Set up an Automation Server

When you install Patch Manager in large or distributed networks, your network environment may require additional Automation Servers to manage your deployment. To address this issue, Patch Manager uses Automation Servers to initiate RPC/WMI connections to remote systems.

When you deploy an Automation Server, Patch Manager can simultaneously target more systems. Additionally, deploying an Automation Server closer to the remote systems they manage allows the RPC/WMI connection to travel a shorter distance.

If an Automation Server is not set up correctly, you can re-provision the server. See Re-provision an Automation Server for details.

You can use Automation Server roles to manage a dedicated target or manage geographically distributed networks.

You can define specific worker process settings to limit the capacity of each Automation Server. See Automation Server Settings for details.

To set up an Automation Server:

1. Download and run the Patch Manager Installer.
2. Configure the Automation Server routing rules.
3. (Optional) Configure the subnet routing rules.

Run the Patch Manager Installer

1. Log in to the Customer Portal.
2. Download the Patch Manager software.
   1. Click Downloads > Download Product.
   2. Click the Products drop-down menu and select Patch Manager.
   3. Click the Licenses drop-down menu and select your license tier.
   4. Download the Patch Manager FULL with SQL installer.
   5. Log out of the Customer Portal.

3. Launch the installer on your WSUS server.

   During the installation, the installer extracts the .NET Framework files.

4. Select the following, and then click Next:
   • Install the Patch Manager Server Components
   • Install the Patch Manager Administrations Console
5. If you accept the License Agreement, click Next.
6. Select the Destination location and Click Next.

7. (Important) In the SolarWinds Platform Install selection, select Advanced Install.

   

8. Select Start Copying Files, and click Next.

   The Wizard installs the Administrator Console and closes automatically.

9. When prompted, click Next to launch the SolarWinds Patch Manager Configuration Wizard.
10. Select Automation Server, and click Next.

11. Enter the name of the Primary Patch Manager server and test the connection.

    If the test passes, click Next.

    If the test does not pass, troubleshoot the issue, and then click Next to test the connection.

12. Configure the Windows Firewall for the server, and click Next.
13. When prompted, enter the WSUS server information, and click Next.
14. Enter a local administrator account that is in the WSUS Administrators group, and click Next.
15. Select Install SQL Server Express, and click Next.
16. Select the Default service account and click Next.
17. Complete the Patch Manager Configuration Wizard and click Next.

Configure the Automation Server routing rules

Patch Manager uses Automation Server routing rules to manage tasks sent to each Automation Server. They define whether or not to assign a task to a default round-robin pool if an assigned server is unavailable.

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. In the Patch Manager Server Configuration Wizard, select Edit an Existing Patch Manager Server configuration settings, and click Next.

   

7. Click the Server Name drop-down menu, select the Automation Server, and click Next.

   If the remaining fields do not populate automatically, click Resolve.

   

8. Associate your Patch Manager Server with a Patch Manager Management Group.

   

   1. Click the Management Group drop-down menu and select Managed Enterprise.
   2. Click Server Role and select Automation.
   3. Review the remaining options, then 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. In the Actions pane under Routing Rules, select Add WSUS Server Rule.

    

13. Click the Server Name drop-down menu, select the WSUS server, and click Save.

    If the remaining fields do not populate automatically, click Resolve.

    

14. Click Test Connection.

    If the connection passes, a dialog box displays. Click OK.

    

    If the connection does not pass, check the configuration settings in the window.

15. Select the Automation Server and Absolute Rule checkboxes and click OK.

16. Restart the EminentWare Data Grid Server Service 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.

(Optional) Configure the Subnet Routing Rules

In the navigation pane, expand Patch Manager System Configuration > Management Groups and select Managed Enterprise.

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 under Routing Rules, click Add Subnet 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.