We are facing updating the ZCM agent on 3000+ workstations spread over 26 sites, each with their own ZCM satellite server. They currently run the 11.3.x agent and we recently updated ZCM to 11.4.2.
The administrators want to deploy the updated ZCM agent via a ZCM bundle, to eliminate swamping the network with the agent download at a site, since some sites are on 100M switches and already have a lot of traffic.
The proposed agent update bundle would notify users that they can deploy the update at their convenience (since a reboot is required and the agent update can take quite some time) until a specific date. On that date, the ZCM bundle for the agent update will be set to force run.
This technique (notify, then force) has worked in the past when large applications needed to be deployed to everyone.
Multiple attempts to create a ZCM bundle to do this agent upgrade failed when the agent hit about 94% completion. Having the current ZCM agent running the agent update causes a bit of a dilemma. How does the agent update continue when the update agent shuts down the current ZCM agent and the current agent is running the update? How can the update continue?
While deployment tasks may end up being the way to go, being able to deploy the update via a ZCM bundle would be wonderful.