1 of 1 people found this helpful
Does it have anything to do with EEPC? I think you should post it in ePO forum. This one is for "EEPC v6.x in ePO", just not very fortunate wording.
My bad, i'll move it
As long as you do not have "Global Updating" enabled, what you described doing in 3.6 is still possible in 4.5. If you do not have any Client Tasks enabled to deploy the McAfee Agent 4.5 to the machines it should not install. You could check in the 4.5 Agent to the repository, create a Tag called something like "Ready for 4.5" and then create a "Client task" to install MA 4.5 only to machines tagged "Ready for 4.5". Alternatively you could also use the "Evaluation Branch" to test out the new agent.
Thanks for that, but pardon me for maybe being a bit thick.....in the old 3.6 console you could do what you suggested in point 1, disable client task for Mcafee Agent, but in 4.5 the Deployment Client task for this particular OU has both the Mcafee Agent and Virusscan product, and in 4.5 I only get the drop-down choice of Install, whereas the old 3.6 version I got Install, remove, not install etc.. The 4.5 (schedule) bit I can enable/disable, but won't this disable both (Agent & Virusscan deployment
Do I just (on the Mcafee Agent just Choose 'Select' so the Mcafee Agent is not listed?
Sorry if I have confused you.
If you disable a task that is setup to install both the Agent and VSE it will not install either one. One way to get only the Agent to stop installing would be to just choose "Select" from the drop down where the Agent is listed or you could just press the "-" sign next to that entry and the Agent installation will be removed from the task. I don't know how controlled you want your roll out to be. Are you looking to do a whole group, EPO tree section, or OU at a time? If you want to do a whole EPO tree section at a time you could just have the Deployment task for the Agent in the "My Organization" level and then set it to Disabled. Then you could "Enable" that task in the particular EPO tree section you want to deploy the agent to. In order to do it this way you would have to make sure there are no other McAfee Agent 4.5 deployment tasks setup to install form the "Current" branch otherwise the agents will be deployed throughout your tree.
Thanks, I think I may have done it like that on 3.6 console. As long as the top-level is set to disabled, when I put the mcafee agent 4.5 into the repository it won't go and deploy to everything, that's right isn't it?
Then I can go to each OU and install it at my leisure.
That should be right as long as the top level is set to disbaled the child levels will also be disabled until you set them otherwise.