Submit a ticketCall us

Training ClassThe Orion® Platform Instructor-led Classes

Provided by SolarWinds® Academy, these trainings will introduce users to the Orion Platform and its features, management, and navigation. These courses are suitable for users looking to discover new tips, tricks, and ways to adapt their Orion products to better suit their monitoring needs:
Deploying the Orion Platform
Configuring Orion views, maps, and accounts
Configuring Orion alerts and reports

Reserve your seat.

Home > Success Center > Patch Manager > Patch Manager - Knowledgebase Articles > How to install a Secondary Application Server (SAS) in Patch Manager

How to install a Secondary Application Server (SAS) in Patch Manager

Updated June 27, 2018


This article describes how to install a Secondary Application Server (SAS) in a Patch Manager deployment running supported versions of Microsoft® Windows Server® and Microsoft SQL Server®

When you installed Patch Manager for the first time, you installed the licensed version on the Primary Application Server (PAS). A SAS is a full Patch Manager installation that links back and communicates with the PAS. The SAS is able to independently download third-party packages from the SolarWinds third-party catalog and control separate Windows Server Update Services (WSUS) servers that are not configured to work with the PAS. 

If you want to extend the reach of the PAS to a remote network, install an Automation Server. If you want a completely separate setup that is not controlled by the PAS, follow the steps in this article to install as SAS in your deployment.

See Server Role Definitions for details about Patch Manager server roles. 


  • Windows Server 2008 R2
  • Windows Server 2012 R2
  • Windows Server 2016
  • SQL Server 2008
  • SQL Server 2012
  • SQL Server 2014 and higher


Set up your SAS server

Do not install a SAS on a SolarWinds Orion® server.

Perform the following procedures from the Patch Manager Installation Guide to prepare your server for deployment.

  1. Complete the Pre-flight checklist to verify that system requirements are met, all required software is installed, and required roles and features are enabled.
  2. Review the system requirements for setting up a Patch Manager server.
  3. Prepare the Patch Manager server to verify that the server is set up and configured for a Patch Manager deployment.
  4. Determine and set up the database.

Download the installation file

  1. Log in to the server that will host the SAS.
  2. Go to the SolarWinds Customer Portal.

    See Access the Customer Portal if you need to create a SolarWinds account.

  3. Log in using your SolarWinds ID (SWID) and password.
  4. In the Latest Downloads table, locate Patch Manager and click Choose Download.
  5. Download the following package:
    Patch Manager full package (with SQL)
  6. Follow the prompts on the screen to complete the download.

Run the installation file

  1. Extract the contents of the downloaded ZIP file.
  2. Run SolarWinds-Patch-Manager-2.1.x-Full.exe.

    You may need to verify if the installation file is blocked. To check, right-click the file and select Properties. If required, click Unblock, and then click OK.

  3. If prompted, click Install to install Microsoft .NET Framework.

    Downloading and installing Microsoft .NET Framework can take more than 20 minutes. If your system reboots, run the installation again.

  4. If prompted, enter your email address in the SolarWinds Registration window, and click Continue.

    This registration is for receiving product information from SolarWinds and is required to continue the SolarWinds Patch Manager installation.

    The installer extracts the files and initiates the Patch Manager Setup wizard.

    This process will take some time to complete.

Complete the Patch Manager Setup wizard

  1. In the Installation Type window, select the following, and then click Next:
    • Install the Patch manager server components
    • Install the Patch Manager administration console


  2. Click Next on the Welcome window.


  3. If you accept the terms of the license agreement, click Next.


  4. Accept the default destination (recommended) or select another location, and then click Next.


    The wizard installs the Patch Manager software in the selected location.

    This process may take several minutes to complete.

  5. Select Advanced Install, and click Next.


  6. Click Next to copy the program files to your system.


  7. After the setup completes, the SolarWinds Configuration wizard automatically runs.

Run the Configuration Wizard

The Configuration Wizard is where you select the Advanced option to set up the SAS. When you complete the wizard, perform the following steps.

If you need assistance, contact SolarWinds Technical Support or submit a ticket.

  1. In the Welcome window, click Next.
  2. In the Select a Server Role window, select Application Server and click Next.


  3. In the Select a Provisioning Method window, select Connect this instance to a Patch Manager Primary Application Server.


  4. In the Hostname field, enter the hostname for the PAS, and then click Test to check the connection to the server.

    If the connection is successful, click Next.

    If the connection is not successful, verify that port 4092 is open on the PAS, and then click Test.

  5. Click Next.
  6. In the Select a Server Settings window, no selections are required or available by default for the SAS. Click Next to continue. 
  7. In the WSUS Setup window, select Install the Patch Manager WSUS service (Recommended) if you have a WSUS that needs to be connected immediately to the SAS.

    If you plan to supply a WSUS, select the second option, and then go to Add WSUS to Patch Manager after you complete the installation.


  8. Click Next to continue.
  9. In the Patch Manager Local Credentials Setup window, enter your Domain Admin credentials using the following format in the User Name field: 



    Depending on your environment, you may need to enter a Local Admin user name and password. The user name format would be .\administrator.

    This account will set up the registry keys and complete the installation steps required for the SAS to work properly. These credentials are not used after you complete the installation, but do require Local Administrator rights to the server that is hosting this installation.

  10. Click Next.
  11. In the Patch Manager Database Settings window, select an option and complete the required fields.


    Select Install SQL Server Express instance to install a full Microsoft SQL Server Express Database on the local server.

    Select Use installed SQL Server instance to connect to an existing local or remote SQL database instance and install the EminentWare database. See Configuring Patch Manager for a remote SQL Server for details.  

    Make sure your database instance is not used by another application. Otherwise, you will overwrite the table data.

  12. Click Next.
  13. In the Patch Manager Service Account window, select an option to connect to the EminentWare Datagrid Service.


    Select Use the default service account if you are installing SQL Server Express. This is for a local user.

    Select Use a custom account to connect to a database instance, and then enter a user name and password.

    This account is tied to the EminentWare DataGrid Service that connects to the database and must have sa and dbowner rights. If you are using a Domain Admin account, the account should also be a service account so the password will not change. See error 1064 and error 1069 for examples of errors you may see if you change the password for this account.

  14. Click Next.
  15. In the Proxy Server Settings window, the installer checks your Internet connection.


    When the check is completed, the Completing the Patch Manager Configuration Window displays.


  16. Click Next.

    The Patch Manager Configuration Wizard completes the installation.

    This process requires an extended amount of time to complete. If the Configuration Wizard does not complete successfully and errors display in the wizard, contact SolarWinds Technical Support.

  17. When prompted, click Finish to complete the installation.
  18. If you chose to supply your own WSUS in step 7, see Add WSUS to Patch Manager for details. 



Last modified