This content has been marked as final. Show 6 replies
When you pushed 8.7 to the computers, did your task include a removal step for 8.0?
When I pushed 8.7 & 8.5, I configured a removal task for the previous and then an install task for the current. The one time I forgot to do this on a branch, I edited the deployment task to add the removal step and set the schedule for immediate to get it out ASAP.
Thanks for your comment.
No, I did not include the removal task!
I have tested without removal task and it worked in the lab, so didn't bother. :(
Is it too late to add removal task??
I've been able to add it successfully after initial deployment on a small scale with test branches...if not, you could always config a separate task for just removing the old version.
Thanks, I have set the removal task.
See how it goes.
I had this issue when I deployed 8.5i to our environment (approx. 50,000 workstations) last year.
It seems that in some cases (<2% of environment) 8.0i just didn't want to let go of the system. I found no difference statistically whether the deployment task was set to remove 8.0 or not. Unfortunately, on those machines who failed to remove 8.0i when installing 8.5i, there was no easy solution. In fact, it took multiple methods. On some, I could set the deployment task to remove after the fact and it worked, on others I had to log on remotely and remove using ARP applet. On others, those methods would not work either and I had to perform a manual wipe from the machine using a doc given to me by platinum support for manually removing 8.0i and all other McAfee products.
That's a ******.
Did your users experinced slow responce whilst havining 2 version of VSE?