On the completion of the Patch Installation Maintenance Window.On the completion of the Patch Detection Maintenance Window.The status of the patch service updates on these triggers in N-able N-central: The types of patches to be reported by the service. Include Patches in the following categories The duration in days that a patch can be approved but not installed before the patch is added to the Missing Patches That Were Approved Over xx Days Ago metric. The default is 4320 minutes 72 hours, or 3 days. If no data is received within the specified time period, the service will transition to a Stale status. The time, in minutes, that N-able N-central waits to receive data about the service. Laptop - Windows, Server - Windows, and Workstation - Windows The data will still be available for reporting.
The service will now only alert you if something has gone wrong with your patch schedule, a patch has failed or a reboot is needed.
On the Thresholds tab, turn off all thresholds except for Patches installed with errors, Missing Patches Older Than (x) Days, and Reboot Required. On the Service Details tab, set Threshold for Monitoring old patches (days) to 31 days. Recommendations for setting up this service: You can use the service and not use Patch Management and visa versa. The Patch Status service is not connected to Patch Management. Devices using older agents will continue to report to the Patch Status service. Agents will go forward using the Patch Status V2 service. You can configure settings through the Status, Service Details, Self-Healing, Reports tabs on this window.Īs of N-able N-central version 12.1, agents that are upgraded to the current version will no longer report into, or have available the Patch Status service. It provides insight into the state of patching on a specific device as well as providing metrics for your reporting. The Patch Status service is automatically added to all Windows devices.
0 kommentar(er)
