Monitor & Agent Management Affected by Microsoft Update
A recent Microsoft update may affect our ability to manage and deploy agents and monitors from the Real-Time Console.
You may encounter issues only if not all your machines running the ControlUp Real-Time Console, Agents and Monitors have the latest Windows updates deployed.
Microsoft included KB5004442 in their latest cumulative update that was released the week of 13 June 2022. This KB by default hardens the DCOM communication which we use for the Real-Time Console to manage agent and monitor machines (along with the WMI). Hardening DCOM causes the Real-Time Console to not be able to perform management tasks on the agent and monitor machines.
If all your ControlUp machines include all the latest Windows updates, there is no need for action and you will not experience this issue.
Real-Time Console Management Tasks
The Real-Time Console is not able to perform management tasks such as start/stop/deploy on agent and monitor machines that ran this latest Windows update.
Agent Deployment from the Real-Time Console
This issue also may affect the ability to deploy new agents and monitors directly from the Real-Time Console onto Windows machines that have run this Windows update. This issue affects environments that have selected the Deploy Agents Automatically option in the Agent Settings page. For deployment, you can use an MSI. For details, see How to Deploy the Agent on Your Master Image for PVS/MCS/Linked/Instant Clones.
Because this issue may affect the ability of the Real-Time Console to perform other management tasks such as start/stop on the machines as well as monitor deployment, we strongly recommend the solution below on all your ControlUp machines.
Make sure you always have the latest Windows updates installed on all ControlUp machines (monitor, console and agent machines).
If for some reason, you cannot run all the latest Windows updates on all your machines, you have to disable the hardening changes on those machines as described in this Microsoft article. Be sure that you assign a value of 0 to the new registry key to disable the change.