Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Setting a fixed port for WMI

Setting a fixed port for WMI

Overview

This article allows you to see information from Microsoft on setting up a fixed port for WMI.  SolarWinds does not provide support in connection with setting up a WMI.

Environment

  • Server & Application Monitor (SAM) 
  • Windows Management Instr. - WMI (SAM)
  • Monitoring (SAM)

Resolution

Note: The following instructions are based on the Microsoft article located here
SolarWinds does not provide support concerning the following information:

To set up a fixed port for WMI:

  1. At the command prompt, type:  winmgmt -standalonehost
  2. Stop the WMI service by typing the command:  net stop "Windows Management Instrumentation"
  3. Restart the WMI service again in a new service host by typing:  net start "Windows Management Instrumentation"
  4. Establish a new port number for the WMI service by typing:  netsh firewall add portopening TCP 24158 WMIFixedPort
  5. WMI ports are TCP Port 135 and by default, all TCP ports from 1024 to 65534
 

 

Last modified

Tags

Classifications

Public