We're presently using Agent 3.6 for all our "clients" (BTW thanks for the info on end-of-life).
If I do as you say, won't the agent 3.6 package be moved to "previous branch"? The doc mentions :
(...) only agent version 4.0 and later can use the Previous and Evaluation branches for deployable files. Agent version 3.6.0 and earlier can only use the Current branch's deployable packages, regardless of this setting.
So won't I automatically install agent 3.6 to all my clients ? There's a deployment task that executes once a day... Since I only want to test MA 4 on a few systems before deployment this would defeat my purpose... or not ?
You can change setting by clicking Edit on bottom right.
There no option to have 2 different versions of agent in Current Branch. I did follow: Disabled overall agent deployment task Checked in new agent, marked move 3.6 to prevous branch Deployed new agent for few systems manually, test it for limited period of time, during this time you will not be able to deploy automatically agents, if you need - only manually for new systems Deployed new agent to all.
You will still be able to push 3.6 agent manually --> when you choosing system --> deploy agent --> you will have option to choose what agent to push.
bottom line - agent 4 is more than 7-8 months as released, have patch 1, stable. no reason to postpone this upgrade.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.