Central Management

This version of 0patch Agent supports remote management via 0patch Central. You need a 0patch Enterprise subscription for this feature.

Note that some older versions do not support remote management; you may need to update your agents to use this feature.

When the agent is remotely managed, a local admin on the computer can still launch 0patch Console and perform all actions (e.g., for the purpose of quickly disabling a patch to see if it’s causing problems) but all such local changes will be reverted upon agent’s next sync to the server and synchronized with server’s policy. The reasoning behind this automation is that as you manually change agent's configuration in order to troubleshoot some issue, you may forget to revert it back to the original (desired) state. Automatically reverting the configuration ensures that what you see in 0patch Central is actually how the agent is configured. (To make a lasting configuration change when the agent is remotely managed, you have to make that change in 0patch Central.)

To alert the local admin that the agent is remotely managed, 0patch Console’s bottom bar shows the following text in red: “THIS AGENT IS REMOTELY MANAGED. ANY CHANGES YOU MAKE TO THE SETTINGS MAY BE REVERTED UPON THE NEXT SYNC TO THE SERVER” as shown on the image below.

In addition, a remotely managed agent does not show any pop-ups. However, it still logs events to 0patch log files.

0patch Console is warning the user that the agent is remotely managed and that any changes will be reverted upon the next server sync