WS-Management (Web Services-Management) is a DMTFopen standard defining a SOAP-based protocol for the management of servers, devices, applications and various Web services. WS-Management provides a common way for systems to access and exchange management information across the IT infrastructure.
The specification is quite rich, supporting much more than get/set of simple variables, and in that it is closer to WBEM or Netconf than to SNMP. A mapping of the DMTF-originated Common Information Model into WS-Management was also defined.
WS-Management was originally developed by a coalition of vendors. The coalition started with AMD, Dell, Intel, Microsoft, Sun Microsystems and expanded to a total of 13 members before being subsumed by the DMTF in 2005.
The DMTF has published the standards document DSP0226 with version 1.2 of September 30, 2014.[1]
Using WS-Management (WinRM 2.0), Windows PowerShell 2.0 allows scripts and cmdlets to be invoked on a remote machine or a large set of remote machines.
WinRM 2.0 for Windows XP and Windows Server 2003 was released on Oct 26, 2009.[3]
WinRM 3.0 for Windows 7 and Windows Server 2008 R2 was released on Sept 4 2012 and shipped in Windows 8 and Windows Server 2012.[4]
A European research project (ITEA 2 programme, a strategic pan-European programme for advanced pre-competitive R&D in Software-intensive Systems and Services), named SODA (Service Oriented Device and Delivery Architecture) developed several implementations of WS-Management in ANSI C, Java, and for OSGi. These implementations are specifically targeted to be used with an open SOAP web serviceprotocol stack named DPWS (Devices Profile for Web Services), and were optimized to be integrated in micro-devices with only 100kB of memory. These implementations are free software, licensed under the GNU Lesser General Public License (LGPL), and their source code is freely available for download.
OpenNMS, an open-source network management platform, includes a pure-Java WS-Management client library.[6] This library enables WS-Management as a management protocol in OpenNMS.[7]
By default WinRM HTTP uses port 80 and HTTPS uses port 443. On Windows 7 and higher the default ports are 5985 and 5986, respectively.[8]