Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Patch Manager > Servers not rebooting after updates applied and does not complete the reboot cycle

Servers not rebooting after updates applied and does not complete the reboot cycle

Created by Brandon Painter, last modified by Cory Farr on May 31, 2017

Views: 42 Votes: 0 Revisions: 6

Overview

The machines are not rebooting properly when assigning a task targeted at multiple systems. This could be related to WMI connectivity issues. Installing the Patch Manager Agent to your systems allows you to connect to your systems using port 4092 instead of WMI.

Environment

Patch Manager 2.1 and later​

Cause 

This is due to time out or connectivity issues with WMI.

Resolution

  1. Find the system you are having issues with and select it in the Patch Manager console.
  2. Right-click the system and select Deploy Client Components.
  3. Follow the wizard to either use the Remote installer services or Create a WSUS Package.
  4. If you create a WSUS Package, it will create one located in:  Administration and Reporting > Software Publishing > Solarwinds.
  5. Publish the package and approve it to your computer groups that you desire to send it to. Refer to Approving Updates.
Last modified
08:01, 31 May 2017

Tags

Classifications

Public