Install Patch Manager in an Orion deployment
These instructions provide stand-alone installation steps for installing Patch Manager on a dedicated server with Microsoft Windows Server Update Services (WSUS) enabled in the operating system.
See the Patch Manager Administrator Guide for advanced deployment scenarios and instructions for integrating Patch Manager with System Center Configuration Manager (SCCM).
Patch Manager must be installed on a separate server.
Before you install the Patch Manager Web Console, update the Orion Platform modules (such as NPM and SAM) on your Orion server to the same version (for example, 2020.2.5. Running a previous version will impact the stability of your Orion deployment. See your Orion product documentation for instructions.
To complete the installation:
- Use the Local Administrator account to install the software. The domain account is subject to your domain group policies, which can block the installation tasks.
- If you are installing Patch Manager using a remote SQL Server instance, run the installation file as an existing, fully-qualified domain account with sysadmin rights on the SQL database server.
Before you begin
Review the pre-flight checklist. This checklist helps you:
- Verify that system requirements are met, all required software is installed, and required roles and features are enabled.
- Gather the information required to complete the installation.
- Prepare the Patch Manager server to ensure it is set up and configured for a Patch Manager deployment with the Orion platform.
- Select and configure the SQL database that meets your deployment requirements.
- Set up and configure the managed systems to receive updates from the WSUS server.
Locate the database information.
If you installed a full version of Microsoft SQL Server on another system, locate the following:
- Network path to the database instance
- SQL Server computer name hosting the Orion database
- Record the IP address, port, and location of the Orion website.
- Go to customerportal.solarwinds.com.
- Log in using your SolarWinds customer ID (SWID) and password.
- Click Downloads > Download Product.
- On the Products Downloads page, click the drop-down menus and select Patch Manager and the corresponding license.
- Under All Release Downloads, locate and download:
- Patch Manager full package (with SQL)
- Patch Manager Integration Module
- Follow the prompts on the screen to complete the download.
Run the installation file
- Double-click the installation package.
- Extract the contents of the downloaded installation ZIP file to the Patch Manager server.
Double-click the installer.
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.
If prompted, click Install to install the .NET Framework.
Downloading and installing .NET Framework can take more than 20 minutes. If your system reboots, run the installer again.
Select the following options, and click Next:
- Install the Patch Manager server components
- Install the Patch Manager administration console
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
In the Welcome window, click Next.
The installer checks your environment to verify the system requirements.
- If you accept the terms of the license agreement, click Next.
Accept the default destination (recommended) or click Browse and select a directory, and then click Next.
The wizard installs the Patch Manager software.
This process may take several minutes to complete.
Select Advanced Install, and click Next.
The program files are copied to the system.
After the setup completes, the SolarWinds Configuration Wizard automatically runs.
- In the Welcome window, click Next.
Enter the SQL Server database settings, and then click Next.
- Click the SQL Server drop-down menu and select the SQL database server hosting the Patch Manager database instance.
Select an authentication method and complete the fields (if required).
- Enter the SQL Server database settings, and click Next.
- Select Use an existing database.
Click the drop-down arrow and select the external database.
Select the SQL Server database account, and click Next.
If you are creating a new account, select Create a new account and enter your password.
If you are using an existing account, verify that Use an existing account is selected and accept the default information.
Verify the settings for the Orion website, and click Next.
- If the SolarWinds directory does not exist, you are prompted to create the directory. Click Yes to continue.
- If prompted, select the services to install, and click Next.
Select Primary Application Server, and click Next.
Accept the default server settings, and click Next.
Select I'll supply my own WSUS server, and click Next.
Select the WSUS setup options, and click Next.
Enter a user account and password with local admin rights to the SolarWinds Patch Manager server, and click Next.
If the SQL server is remote, the user account should be a domain account.
Select the location of the SolarWinds Patch Manager database, and click Next.
Select the service account to run the SolarWinds Patch Manager Service, and click Next.
The installer checks the proxy server settings, and verifies the Internet connection.
Run the Completing Orion Installation Wizard
The wizard configures the Orion installation.
This process may take several minutes to complete.
In the Product Features Select window, select WSUS Extension Pack, and click Continue.
The Patch Manager Administrator Console appears.
Locate the Patch Manager database
In the navigation menu, select Patch Manager System Configuration.
In the Patch Manager System Tasks pane, click Database Information.
The Database Information dialog box displays with the machine, database, and database instance names.