the 3.6 agent currently installed on all your workstations and server does not have the ability to install product packages (only dat and engine) from any other than the current branch. You can however push the agent 4.0 out to your environment through ePO, from the eval branch.
See also the readme/release notes for MA 4.0.
Thanks for your answer. Unfortunately, allthough I am responsible for ePO & AntiVirus, I do not have the necessary priviliges on all workstations, nor do I have access to such a user. That is why pushing the agent will not work for me.
What would be the impact if I place the agent 3.6 in the previous branch and the agent 4.0 in the current branch? I would then be able to deploy using a deployment task, but what would be the impact on all systems still having the agent 3.6?
in this case your options are (very) limited. Once the agent 4.0 is in the current branch you can utilise a deployment task to roll it out. All your existing 3.6 agents will be upgraded to the agent 4.0 version you have checked into the master repository. Latest build for agent 4.0 is 220.127.116.114 (Patch 3).
That would be the impact as far as I can see. Bear in mind though that also an update now on a local client or enabled global update can trigger deployment of software in the master repository.
Global Updating is disabled and Deployment tasks are set to diabled. I would of course create a separate group for the upgrade to agent 4.0 and would move systems to that group if I want to upgrade them.
Thanks a lot for your help!
1 of 1 people found this helpful
You can reference this thread for checking in multiple agents into the ePO Master Repository:
Also, that agent is only sent out via a deployment task, not an update, so globacl updating and the "Update Now" option would not trigger an agent upgrade as it is an install package and not an update/upgrade.