Requirements
These system requirements define the minimum requirements for Patch Manager 2024.4. For additional information about requirements, see the Patch Manager Release Notes.
- Server requirements
- WSUS requirements
- SQL database server requirements
- SCCM requirements
- Firewall requirements
- Managed systems requirements
- SolarWinds Platform (SolarWinds Platform integration only)
- Port requirements
- WMI requirements
Server requirements
Set up your dedicated SolarWinds Patch Manager server using the following requirements.
Hardware or Software | Requirements |
---|---|
CPU |
32- or 64-bit 2.4 GHz Dual Core (minimum) |
RAM |
4 GB (minimum) 10 GB or higher (recommended) |
Hard drive space |
20 GB or higher (without WSUS) 200 GB or higher (with WSUS) SolarWinds recommends 20 GB or higher of hard drive space to accommodate fluctuations in space requirements in a production environment. |
Supported Production Operating System (MMC console only installation) |
Windows Server 2012 Windows Server 2012 R2 Windows Server 2016 Windows Server 2019 Windows Server 2022 |
Supported Production Operating System |
Windows Server 2016 Windows Server 2019 Window Server 2022 |
Supported Evaluation Operating System |
Windows 7 Windows 7 SP1 Windows 8 Windows 8.1 Windows 10 Windows 11 |
Operating system languages | English (UK or US) |
.NET Framework |
Version 4.8 for the Patch Manager server Version 4.8 for the SolarWinds Platform server hosting the Patch Manager Web Console (SolarWinds Platform deployments only) If the server is connected to the Internet, the installer updates Microsoft .NET Framework by default. If the server is not connected to the Internet, download .NET Framework from the Microsoft Support website and manually install the software on the server. |
Visual C++ Runtime |
Visual C++ Secure Runtime 9.0 SP1 Visual C++ 2008 Redistributable (32- and 64-bit) Visual C++ 2010 Redistributable (32- and 64-bit) Visual C++ 2012 Redistributable (32- and 64-bit) Visual C++ 2013 Redistributable (32- and 64-bit) SolarWinds Patch Manager installs this software, if required. |
Internet access |
Ensure that the Patch Manager server can access the following websites:
|
WSUS requirements
You can configure Patch Manager with Windows Server Update Services (WSUS)—a free plug-in for your Windows Server operating system. This plug-in downloads software updates from the Microsoft Updates website. Patch Manager allows you to distribute these updates to your managed computers.
See the Microsoft Docs website for details about activating WSUS on your Patch Manager server.
Operating System | Supported Versions |
---|---|
Windows Server 2012 |
WSUS 3.0 SP2 with Microsoft KB2734608 WSUS 6.0 WSUS 6.2 |
Windows Server 2012 R2 | WSUS 6.3 |
Windows Server 2016 Windows Server 2019 Windows Server 2022 |
WSUS 10 |
SQL database server requirements
If you are using a remote SQL database server for the Patch Manager database, ensure that the server meets the following requirements.
See Patch Manager SQL account permissions for details about the SQL Server accounts and account permissions used in Patch Manager.
Hardware or Software | Requirements |
---|---|
CPU |
Dual processor, 3 GHz Quad-processor, 3 GHz, 64-bit (for large networks) |
RAM |
8 GB (minimum) 16 GB (recommended) |
Hard drive space | 20 GB (minimum) |
Database |
Compatible with Microsoft SQL Server instances running the following versions: SQL Server 2012, 2012 SP1, 2012, SP2, or 2012 SP3 SQL Server 2014 or 2014 SP1 SQL Server 2016 SQL Server 2016 Express SP1 SQL Server 2016 SP2 SQL Server 2017 SQL Server 2019 SQL Server 2016 or later is required for a SolarWinds Platform installation. SQL Server 2012 or later is required for a standalone installation.
|
SCCM requirements
Optionally, you can configure Patch Manager with Microsoft System Center Configuration Manager (SCCM)—a systems management application sold separately that manages computers in a corporate enterprise.
See Set up Patch Manager with SCCM in the Patch Manager Administrator Guide for details.
Software | Requirements |
---|---|
SCCM |
SCCM 2007 SP2 or later SCCM 2012 SCCM 2012 R2 SCCM 1511 SCCM 1606 SCCM 1610 SCCM 1702 SCCM 1706 SCCM 1710 SCCM 1801 SCCM 1802 SCCM 1806 SCCM 1810 SCCM 1902 SCCM 1906 SCCM 1910 SCCM 2002 SCCM 2006 SCCM 2010 SCCM 2103 SCCM 2107 SCCM 2111 SCCM 2203 |
Add support for SCCM 2111
If you are running SCCM 2111 in your deployment, perform the following steps to enable third party patches to display in the Configuration Manager:
-
Log in to the Configuration Manager.
-
In the left menu, click Administration > Site Configuration > Sites.
-
Select the site and choose Hierarchy settings.
-
Uncheck the following option:
-
Click OK.
-
Restart the Configuration Manager.
Firewall requirements
Ensure that the Patch Manager server can access the following websites across your corporate firewall.
Website | Description |
---|---|
https://www.microsoft.com | Provides access to the WSUS installer |
https://3pupcontent.solarwinds.com | Provides access to third-party updates from SolarWinds |
https://catalog.update.microsoft.com | Provides access to Windows updates, patches, and hotfixes from Microsoft |
https://downloads.solarwinds.com | Provides access to Patch Manager application updates in the Patch Manager MMC Console |
Managed systems requirements
Ensure that all client systems managed by Patch Manager meets the following minimum requirements.
Hardware or Software | Supported Versions |
---|---|
CPU |
1.5 GHz (minimum) Dual or Quad Core (recommended) |
RAM | 1 GB (minimum) |
Operating system |
Windows 7 Windows 8 Windows 8.1 Windows 10 Windows 11 Windows Server 2008 R2 or 2008 SP2 Windows Server 2012 or 2012 R2 Windows Server 2016 Windows Server 2019 Windows Server 2022 |
SolarWinds Platform (SolarWinds Platform integration only)
When you integrate Patch Manager with the SolarWinds Platform , do not install Patch Manager, WSUS, and the Patch Manager Web Console on the SolarWinds Platform server. This configuration will impact the performance of your SolarWinds Platform-based applications.
SolarWinds Platform server requirements
See the SolarWinds Platform documentation for the latest SolarWinds Platform server requirements.
Additional Web Server requirements
Software | Supported Versions |
---|---|
SolarWinds Platformweb user interface |
Latest version Beginning in Patch Manager 2.1.7, the SolarWinds Platform web user interface no longer supports a SolarWinds Platform server running Windows Server 2012 or Windows Server 2012 R2. Ensure that the SolarWinds Platform server is running Windows Server 2016 or later. See the SolarWinds Platform documentation for the latest SolarWinds Platform server requirements. |
Web console browser
See the SolarWinds platform requirements for details about the SolarWinds Platform Web Console browser requirements.
Port requirements
The following table lists the port requirements for the Patch Manager server and Application Server.
Patch Manager server
Port | Protocol | Service/Process | Direction | Description |
---|---|---|---|---|
135 | TCP | RPC Endpoint Mapper | Bidirectional | The Patch Manager server uses this port to establish Windows Management Instrumentation (WMI) connections to remote computers. The server also uses this port to connect to the Service Control Manager (SCM) when it provisions the WMI providers dynamically on the remote computer. |
389 | TCP | LDAP | Bidirectional | Patch Manager servers use this port for Active Directory authentication. |
445 | TCP | SMB over TCP | Bidirectional | The Patch Manager server uses this port when it provisions the WMI providers to a remote computer. |
4092 | TCP | Console to Server Communication | Bidirectional |
The Patch Manager Web Console uses this port to communicate to an independent Application Server role. This is a one-way communication channel that only requires inbound TCP traffic on the application server. In a distributed environment, Patch Manager servers use this port in the same manner for downstream server communications. For example, the Patch Manager Primary Application Server (PAS) uses port 4092 to communicate with remote Patch Manager servers in secondary server roles. This port is required to manage systems running the Patch Manager Agent. |
8787 | TCP | Web Console connections | Bidirectional | By default, users connect to the Patch Manager Web Console server on port 8787. |
17777 | TCP | SolarWinds Information Service (SWIS) | Bidirectional |
The SWIS facilities data exchange for the SolarWinds Patch Manager Web Console, along with the web console API. Ensure this port is not blocked on servers running the Patch Manager Web Console server. |
1024-65536 | Dynamic Ports | DCOM or RPC | Bidirectional |
WMI technology is based on Distributed Component Object Model (DCOM)/RPC communication. DCOM/RPC allocates the ports used by the server within a dynamic port range. This range is typically between 1024 and 65536. To configure these ports using Windows Firewall on your managed computers, enable the Inbound Rules in the WMI group. |
Application Server
Port | Protocol | Service/Process | Direction | Description |
---|---|---|---|---|
1433 | TCP | Web-based reports | Bidirectional |
In an integrated configuration with the SolarWinds Platform , the SolarWinds Platform server uses this port to establish a connection to the EminentWare database using TCP/IP. This is also the default port that connects the SQL server with the Patch Manager database. Use SQL Server Configuration Manager to enable the Named Pipes and TCP/IP protocols for the SQL Server Network Configuration. Web Reports requires these protocols enabled on the SQL Server instance where the EminentWare database is located. Additionally, configure a Windows firewall for this port. |
54092 | HTTP | Web API | Bidirectional | Provides unencrypted communications from the SolarWinds Platform Web Module to the Patch Manager Service |
54093 | HTTPS | Web API | Bidirectional | Provides encrypted communications from the SolarWinds Platform Web Module to the Patch Manager Service |
WMI requirements
The following table lists the WMI requirements required by systems running Windows operating systems to establish a successful WMI connection with a remote system.
Requirement | Systems |
---|---|
Distributed Component Object Model (DCOM) File and Print Sharing RPC Service WMI Firewall Exception |
Remote systems |
Credentials with Local Administrator rights | Remote systems in the credential ring |
DCOM | Local systems |
WMI technology is based on DCOM / Remote Procedure Call (DCOM/RPC) communication. DCOM/RPC allocates the ports used by the server within a dynamic port range—typically between ports 1024 and 65536. To configure these ports using Windows Firewall on your managed computers, enable the Inbound Rules in the WMI group. See the Microsoft operating system documentation for details.
Ports 135, 445, and dynamic ports 1024 to 65536 must be open between Patch Manager and the remote system. See Port requirements for all SolarWinds products to review all Patch Manager ports.