Security Compliance
How to manually install the Patch Manager SolarWinds Client Components with optional agent configuration
This article gives the information needed to install the Patch Manager Solarwinds Client Components on target computers, which is useful in the case of restricted environments where the other methods available do not work due to firewall/network restrictions.
First published date
Last published date
Overview
In order for Patch Manager to communicate with the Windows Clients, it must have Client components installed which is either using WMI protocols or a Patch Manager agent.
WMI protocols use a dynamic port range and the full range must be open, or you run the risk of communication failures. WMI port range is 1024 to 65535.
The other form of communication Patch Manager can use is a Patch Manager agent which needs port 4092 open bidirectional.
Product section
Resolution
Manually install the WMI providers as per steps below:
- Log in to the Patch Manager server (Primary Application Server).
- Navigate to:
<
InstalledDrive>:\Program Files (x86)\SolarWinds\Patch Manager\Server\packages\EminentWare - Copy the
wmiproviders_version_number.exefile to the target computer. - Run the installer using Run as Administrator.
- Accept License Terms
- For Setup Type, select Custom if you need to install the Agent version; otherwise, choose the appropriate installation option
- In Custom Setup, click on Agent and choose Will be installed on local hard drive
- In the next screen, leave the destination folder at the default unless you need to install elsewhere
- For the Primary application server, input the hostname or IP address of the main Patch Manager Application server. IP address is most effective.
- Leave port 4092 unless you need to change. You'll need to ensure this listed port is open between the target computer and the Patch Manager Application Server (bidirectional).
- Leave the Request recreating certificate option unchecked.
- The target computer will restart at the end of the Custom installation.
- Finish the installation steps. Normally, the target server will not require a restart unless doing a custom installation (above).
Related processes/articles: