Multiple issues with MA 5.2.333 & VSE8.8P7 & Windows 10
1. Extreme slow installation of VSE8.8 Patch 7 (also Counts for Patch 6) especially in combination with windows 10.
For new installations it takes between 23 up to 30 minutes to install Patch 7 (For Patch 6 allready took between 15 - 25 minutes), this was timed on computers where nothing else was running atm of the deployment (imagine how much longer it could take elseway)
(the duration info comes from the "C:\windows\temp\mcafeelogs\vse8.8.0.core_install_<timestamp>.log" logfiles.)
2.Sometimes when the user restarts the computer during the LOOOOONG installation process the AV gets totaly corrupted (AV & computer), without any option to remove the AV (VSE8.8 disappears from the Add-Remove program listing but some of the services & processes are running like mcshield for instance)
(We already had about a dozen newly deployed Windows 10 clients victims ) in a few cases it could be fixed by running setupVSE.exe (the one with the embedded Patch 7 'VSE880LMLRP7') which is also a LOT faster? in others we had to remove everything manually by disabling all mcafee services & processes deleting all the folders and a few hundred regkeys and start all over again.
That claims that VSE 126.96.36.1998 has to be installed prior to MA 188.8.131.523 ???
How can you properly manage that especially for new computers (via ePO)???
We did some tests with brand new deployed windows 10 laptops, deployed MA 184.108.40.2063 and guess what VSE 220.127.116.118 does NOT get installed, while the same article says:
The VSE 18.104.22.1688 installer checks to ensure that MA 22.214.171.124 or MA 126.96.36.1993 is installed first.
If you attempt to install VSE 188.8.131.528 after MA 184.108.40.2063, the install will fail. Instead, install VSE 220.127.116.118 directly.
If we remove MA 18.104.22.1683 and install MA 22.214.171.124 then the AV VSE 126.96.36.1998 does eventualy gets installed but it takes ages (almost an hour from the moment the setut starts).
It seems that the installation of VSE88P7 happens in 2 twice or in 2 steps (which tooks in total about 50 minutes to finish, the first one about 29 min and the second 23min (according to the start & end time inside 2 "vse8.8.0.core_install_<timestamp>.log" files))
Why SOOOOOO LOOOOOONG when we deploy it via the epo software deployment task using the VSE with imbedded P7 (VSE 188.8.131.528)? While when we run it manually the setupVSE.exe (the one with the embedded Patch 7 'VSE880LMLRP7', which is the exact same one we imported into our repository) the installation process only takes a few minutes including updating the DAT files???)
Again how the F. can we properly deploy (without implementing all kind of additional checks and using different repository branches for the different MA versions) MA 184.108.40.2063 into our epo environment as we can't deploy it to our new windows 10 clients (I don't even know if the same counts for Win 7 or 8.x)
And once we've deployed VSE 220.127.116.118 we have to install MA 18.104.22.1683 or you can run into many issues according the same SB10151 article (it sounds a bit like the 'chicken or the egg' story?)
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.