3 Replies Latest reply on Dec 11, 2009 10:37 AM by SOSITCS

    EPO 4.0 Master Repository and MA Updates


      I checked in the McAfee Agent for Windows 4.0 Patch 2 (1421).  It is listed in the "Current Branch" but under the "Actions" column the "Change Branch | Delete" is greyed out.  I don't know if that is normal.  I should also mention that I have McAfee Agent for Windows 4.5 (1270) checked in and it is currently in the "Evaluation Branch" and under the column "Actions" the "Change Brach" is greyed out but not the "Delete" option.


      I also thought that once patch 2 was checked into the repository it would automatically be pushed out the all the workstations but as of this morning I can see that is not the case.  Do I have to create a client task to push out MA 4.0 Patch 2?





        • 1. Re: EPO 4.0 Master Repository and MA Updates

          By design you cannot delete the agent from the current branch and you cannot move an agent from a different branch. If you wish to place MA 4.5 in the current branch then simply check MA 4.5 into the current branch of the repository and it will overwrite the existing agent in the current branch.


          Updates are not automatically deployed through EPO they require some sort of task (either defined in EPO or on the client machine) to deploy. In this case the agent is not sent out via an update task but rather via a deployment task. This is because all agent installs are (even if you are going from MA 4.0 patch 2 to MA 4.0 patch 3) is actually a complete reinstall of the agent.



          Message was edited by: Jeremy Stanley on 12/11/09 10:33:30 AM CST
          • 2. Re: EPO 4.0 Master Repository and MA Updates

            That is normal- seeing as the agent is a critial component of ePO so it makes sense to not allow deletion- you can upgrade/downgrade per branch but not delete- atleast that is how it has worked for me.


            As for the patch, form what i gather, its not just the patch but the agent install with patch included- so it falls under install and for that you need a client task\product deployment.  If it where a product hotfix and you didn't uncheck that global update setting when you checked it in then it would auto ddeploy.

            1 of 1 people found this helpful
            • 3. Re: EPO 4.0 Master Repository and MA Updates

              Thanks for the replies.  It makes sense now.  Hopefully the day will come when I can answer questions in these groups rather than just ask them.