Yes, you are doing right.Test agent 4.6 on your test machines and if everything goes fine move it to current baranch.But if after installing agent 4.6 still you can redeploy agent 4.5.T do this first you will creat a client task to remove agent 4.6.after it recheck in agent 4.5 into current branch and deploy it.
If I don't delete 4.5, I always can switch between the versions? So why use evaluation branch?
All versions of the agent have the same product code, so you can't have more than one agent package in a particular branch.
Yes, I know, but I can always switch between the branches.. So why evaluation branch?
1 of 1 people found this helpful
Switching between branches is fine, but just to test a specific product if we checkin it in evaluate branch it is good, because the code of the both versions is same so you cant put both agents in same branch.
Thank you very much!
I have another 2 little questions, I would be happy for an answer
1 - When I upgrade my agents to 4.6 patch 2, I have to upgrade the agent key updater? And if I upgrade the two of them, I have to upgrade the agent key updater first?
2 - What will change if I upgrade the agent key updater? Anything at the Security Keys?
Why it's important to upgrade the agent key updater?
Have a nice day everyone!
As long as your ePO public key has not changed (for any reason), then you do not need the agent key updater.
So till I want to change my public key it's not relevant?
Thank you and a wonderful day