According to winrm SDK (msdn2.microsoft.com/aa384426), Windows Remote Management is the Microsoft implementation of the WS management protocol, which is based on standard soap and is not affected by the firewall, allows hardware and operating systems of different vendors to operate on each other." Java specification request 262 (Web Services connector for JMX agent) promises to directly interact with Windows-based, WS-management services.
Winrm can be used for Windows Server 2003 R2, Windows Vista, and Windows Server 2008, and winrm allows you to manage computers over the Internet. Winrm uses port 80 to complete this operation. Port 80 is a standard Internet service port. Most firewalls open this port (however, you can change the port used by winrm and the default transmission mechanism HTTP as needed ).
This technology makes it easier to manage computers over the Internet or even through firewalls. Of course, Windows Management specifications (Wmi) can always remotely manage computers; however, WMI relies on Distributed COM (DCOM) as its remote management technology. This is no problem, but by default, many firewalls will block DCOM communication. Indeed, you can open the corresponding port and allow DCOM to communicate, but many network administrators are not willing to do so, they are worried that the release of DCOM will also bring various types of malicious damage.
Therefore, winrm is a Microsoft implementation of the WS-management protocol, which is a standard soap-based protocol that is not affected by the firewall and allows hardware and operating systems of different vendors to operate on each other." This is just another way of saying that standard Internet protocols (such as HTTP and https) can be used for remote management.
Powershell uses winrm as the remote transmission protocol. The latest powershell 2.0 ctp3 version can be downloaded: http://go.microsoft.com/fwlink? Linkid = 131969. However, to use winrm on powershell 2.0 ctp3, you can only use Vista and Windows 2008 server.