This content has been marked as final. Show 3 replies
I think you'd be heading the right direction with removing 7.1 first. I don't have them anymore, but a cleaning of the registry keys is a good idea as well, since some of the older applications weren't as thorough in removing those. It shouldnt be to difficult to create a small script that will run the 7.1 uninstaller, then clean the registries, then you can either push a new install or run your mid package. Keep in mind that a mid package install means you lose all your settings specific to that system until the next asci.
I always do a direct upgrade of VSE without removing any older version before. The reason is that this will minimize the time no VS is on the client and also, in case the VSE85 install will fail, it will rollback to the VSE7.1 installation. If you remove VSE7.1 explicitly before you are left with no AV protection. My experiences are very good with the direct upgrade mehtod through ePO (VSE7.1 to "Ignore", and VSE8.5 to "install"). You can always use the "Deinstall" option for VSE7.1 in case of troubleshooting.
For your outlook problem. Througout the migration just execute a script which deletes the EXTEND.DAT files at every logon. This will resolve the error automatically.
Thanks, i'm trying to upgrade using the installation designer and in several instances i've noticed that after removing VSE 7.1 epolicy orchestrator has then installed 8.5 so that about 2% of PC ended up unprotected. In 2 instances PCs appeared to have both 7.1 and 8.5 (which i guess is the lesser of two evils!).
I guess i'll trial and upgrade without removing 7.1 on a number of Virtual PCs, however my concern is that the outlook error will then remain unresolved. I guess that will show itself in a trial. I'll get back with trial results.