After enabling winrm with the following command I expected that the listed ports are open on the WS2012R2 host. But "nmap -P0 host" shows that nothing listens on this port. Also "/Windows/System32/Configure-SMRemoting.exe -get" shows that Remoting is enabled. The firewall is globally disabled.

winrm.cmd quickconfig -transport:http
winrm.cmd enumerate winrm/config/listener

What else needs to be configured to have something listen on the configured TCP ports? I did not find anything with Google.

Hi,

Below blog has provide detailed steps about how to configure and troubleshooting winrm. You may follow the link below to confirm the configuration steps first, and then narrow down this problem by troubleshooting steps:
WinRM (Windows Remote Management) Troubleshooting
http://blogs.technet.com/b/jonjor/archive/2009/01/09/winrm-windows-remote-management-troubleshooting.aspx

more information you may reference:
Windows Remote Management Command-Line Tool (Winrm.cmd)
https://technet.microsoft.com/en-us/library/cc781778(v=ws.10).aspx
An Introduction to WinRM Basics
http://blogs.technet.com/b/askperf/archive/2010/09/24/an-introduction-to-winrm-basics.aspx

Best Regards,
Eve Wang

Thanks for the reply.

Nothing in these  websites state what causes the ports to become available. Perhaps I miss packages?

My fresh WS2012R2 installation has just the Hyper-V role and everything that comes with that role.

What "process" or thing does actually listen on port 5985/5986? Perhaps there are ways to verify if such process actually runs. 'winrm get winrm/config' shows both ports are set, and 'winrm enumerate winrm/config/listener' shows that it listens on the IP adresses and port 5985. But nmap shows that nothing listens on that port.