Did anyone else have an issue with the agent auto-update where it basically hosed all the agents? I all of a sudden realized yesterday that most of my agent hadnt checked in for about 6 days.... yikes.
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Our update went smoothly. What version were you on before you set up the upgrade?
Answered 03/06/2012 by: nshah
Red Belt

Please log in to comment
When we upgraded from 5.1 to 5.3 there started to be a lot of clients that are not automatically checking in as expected. We applied the latest released version and the problem still exists. They get the green AMP icon and will update if forced manually. I have an open ticket with support (TICK:176016). Most of the machines are connecting, disconnecting and re-connecting quickly after bootup. The details can be seen under Asset History with "Show All History" selected. For example:
2012/03/05 08:40:24 Machine connected with address
2012/03/05 08:40:14 Machine disconnected.
2012/03/05 08:39:46 Machine connected with address

Also, when we upgraded agents from 5.3.47657 to 5.3.53177 we limited the deployment to two labels which contained a total of 332 computers but the agent was pushed to thousands of computers prematurely. After a week of "testing" the new agent it was deployed to all. There was a ticket (TICK:198623 "Agent Updates aren't being limited to labels") on that issue but support couldn't duplicate the issue and it has been closed.
Answered 03/06/2012 by: RichB
Third Degree Green Belt

Please log in to comment
Answer this question or Comment on this question for clarity