Hoping somebody can help me with a ePo question. I'm preparing to deploy VSE 8.7.0i Patch 4 to our users but i'd like to know how you can do this to small numbers of users at a time, to make sure I don't have any compatibility issues. As far as I can see once you upload the patch in to ePo, it's ready for everybody to receive. Surely ePo offers a way of deploying patches in a granular fashion ??
The way i do it is:-
1 - Disable Global updating in EPO ( Menu -> Configuration -> Server Settings )
2 - Create a new group in the system tree with a task that installs VSE 8.7 P4 (or what ever software you want) with immediate start schedule.
3 - Move selected computers into that group and send an agent wake up.
4 - Once done move the computers back to their original group
If you have multiple repositories you could create multiple 'install' groups and specify different repositories by creating a new agent policy for the group.
Note: I don't use directory sorting so couldn't comment on how this method could/would/should work under those circumstances.Message was edited by: Tristan
I was thinking of doing this also but in my configuration global updating is already disable. The thing is that as soon as I put the package (VSE patch4) in the current branch, all the PCs are downloading it....
I got several repositories but I guess that as they didn't download the latest version yet, when the PCs check they found the master server is the one having the latest VSE version and all are downloading on it...
do you think I can log on the repositories and manually copy the VSEpatch4 into the current_branch folder?
Do you have an update client task running against your groups?
Make sure you only have the 'Signatures and engines:' options ticked and everything under 'Patches and service packs: ' unticked within the configuration tab of the client task.
thanks Tristan !
yes I had this ticked !
so I will untick it and then put back VSEpatch4 in the current branch ! if my understanding is right, the repositories will then download the patch in their current branch folder, but no PCs will install it !
Take a look at KB57905 which you can search from the McAfee Knowledgebase https://mysupport.mcafee.com/Eservice/templatepage.aspx?sURL=3 .
It will show you the various means that Patches can be prematurely deployed throughout your organization. We had global updating disabled, but it still went out to systems that were not part of our test group.
It is a pain to deploy patches as it leaked out to over 1400 of my systems. The only issues we had was with Thunderbird not working. This is due to a problem with exclusions longer than 15 characters, this is addresses byhotfix 613356 which you can get from support after running the MER tool.
Thank you for using McAfee software. This document contains important information about this release. McAfee strongly recommends that you read the entire document.
For a list of supported environments for VirusScan Enterprise 8.7i on Microsoft Windows, see McAfee Support KnowledgeBase article KB51111.
This release was developed for use with:
Resolved issues in this release of the software are described below:
Message was edited by: twenden on 1/18/11 9:27:05 AM CSTMessage was edited by: twenden on 1/18/11 9:29:10 AM CST