Hide this message
Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.
The following sections describe the ports used in the Patch Manager environment.
The Patch Manager server uses this port to establish WMI connections to remote computers. It also uses this port to connect to the Service Control Manager (SCM) when it provisions the WMI providers dynamically on the remote computer.
Create a firewall exception to allow traffic from the Patch Manager server to your managed computers over this port. To do this if you are using Windows Firewall on your managed computers, enable the Inbound Rules in the Windows Management Instrumentation (WMI) group.
The Patch Manager server uses this port when it provisions the WMI providers to a remote computer.
Enable File and Print Sharing on the client systems using the applicable network management tools.
The Patch Manager console uses this port to communicate to an independent Patch Manager application server. This is a one-way communication channel, so it only requires inbound TCP traffic on the application server.
Patch Manager servers in a distributed environment also use this port in the same manner for "downstream" communication. For example, the Patch Manager Primary Application Server (PAS) uses port 4092 to communicate with remote Patch Manager servers in secondary server roles.
Patch Manager servers use this port for Active Directory authentication.
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 Windows Management Instrumentation (WMI) group.