Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > Install and configure an Automation Server for WSUS

Install and configure an Automation Server for WSUS


This article describes how to install and configure an Automation Server role on a WSUS server when Patch Manager and WSUS are installed on servers running different Windows Server operating system versions. This situation generates an API mismatch error.


  • All Patch Manager versions
  • All WSUS versions


Install the Automation Server

  1. Download the Patch Manager FULL with SQL installer from the Customer Portal.
  2. Launch the installer on your WSUS server.
    During the installation, the installer extracts the .NET Framework files. 
  3. Select Install the Patch Manager Server Components and Install the Patch Manager Administrations Console, and click Next.
  4. If you accept the License Agreement, click Next.
  5. Select the Destination location and Click Next.
  6. In the Orion Install selection, select Advanced Install.
  7. Select Start Copying Files and click Next. 
    The Wizard installs the Admin Console and closes automatically.
  8. When prompted, click Next to launch the SolarWinds patch Manager Configuration Wizard. 
  9. Select Automation Server and click Next.
  10. Enter the name of the Primary Patch Manager server and test the connection.
    If the test passed, click Next.
    If the test does not pass, troubleshoot the issue, and then click Next to test the connection. 
  11. Configure the Windows Firewall for the server, and click Next.
  12. When prompted, enter the WSUS server information, and click Next.
  13. Enter a local admin account that is in the WSUS Administrators group, and click Next.
  14. Select Install SQL Server Express, and click Next. 
  15. Select the Default service account, and click Next.
  16. Complete the Patch Manager Configuration Wizard and click Next.

Configure the Automation Server Routing Rule

  1. Log in to the WSUS server as an administrator.
  2. Launch the Patch Manager Administration Console.
  3. In the navigation pane, expand Patch Manager System Configuration and select Patch Manager Servers.
  4. In the center pane, select the Automation Server.
  5. In the Actions pane, click Patch Manager Server Wizard.
  6. Select Edit an Existing Patch Manager Server configuration settings, and click Next.
  7. Click the drop-down menu, select the Automation Server, and click Next.
  8. Expand the Management Group dropdown box, select your Managed Enterprise with the Automation Role, and click Next.
  9. Complete the Wizard.
  10. In the navigation pane, expand Patch Manager System Configuration > Management Groups and select Managed Enterprise.
  11. Select the Automation Server Routing Rules tab.
  12. Select Add WSUS Server Rule in the Actions pane.
  13. Click the Server Name drop-down menu, select the WSUS server, and click Save.
  14. Select the Automation Server and Absolute Rule checkboxes, and click OK.
  15. Restart the EminintWareDataGrid server on the Patch Manager Server and the Automation Server.
    If you do not have WSUS servers located at different sites or domains, you are finished.
    If you have WSUS servers located at different sites or domains, configure the Subnet Routing Rules. 

Configure the Subnet Routing Rules

  1. In the navigation pane, expand Patch Manager System Configuration > Management Groups and select Managed Enterprise.
  2. Click the Automation Server Routing Rules tab.
  3. In the Actions pane, click Add Subnet Routing Rule.
  4. In the dialog box, enter the subnet, click Add Subnet, and then click OK.
  5. Select the Automation Server to use for the subnet, and then click Absolute Rule.
  6. Click OK.
  7. Repeat step 3 through step 6 for each additional subnet you want to add to the Automation Server.  



Last modified