Skip to main content

WindowsRM

What is WindowsRM

WindowsRM (Windows Remote Management), is a built in Microsoft system management component which allows configuration data as well as monitoring events to be to be exchanged with the Memset backend systems.

WindowsRM is a web service which listens on a dedicated port for authenticated, encrypted HTTPS communications to and from a dedicated end point.

More information can be found on the relevant section of the Microsoft site. here

Why is it installed?

Memset utilises WindowsRM to send new system configuration to your server when it is needed. This can be new networking information, when a Miniserver is migrated to a new host or it can be security updates using Windows Updates.

How do I know if my Windows Server has WindowsRM enabled?

You can check to see if WindowsRM is running on your server by running WindowsRM directly or reviewing all the listening ports on your server and checking to see if TCP port 5986 is listening for connections.

WindowsRM configuration can be retrieved by doing the following:

  1. Open powershell
  2. Run the following command:
    winrm enumerate winrm/config/listener
    

You can generate a list of open ports via powershell by doing the following:

  1. Open powershell
  2. Run the following command:
    netstat -ano
    

This command will output all the open ports on your server and show which ones are listening for incoming internet connections. The WindowsRM component listens on TCP port 5986 so if you see a line like the one highlighted in the following screenshot you will know that WindowsRM is installed and running.

Is it secure?

When Memset puts a Windows Server live the Windows Firewall Service is enabled by default and is configured to allow encrypted traffic on port 5986 only to Memset IP addresses. If you decide to disable Windows Firewall please ensure any other security application you decide to use is configured to prevent access to TCP port 5986 from the Internet.

If you have any questions please do not hesitate to contact the support team via this link.

Last updated 11 June 2015, 12:17 GMT