Export (0) Print
Expand All
29 out of 39 rated this helpful - Rate this topic

About Windows Remote Management

Windows Remote Management is one component of the Windows Hardware Management features that manage server hardware locally and remotely. These features include a service that implements the WS-Management protocol, hardware diagnosis and control through bmaaseboard management controllers (BMCs), and a COM API and scripting objects that allow you to write applications that communicate remotely through the WS-Management protocol. For more information about the public specification for WS-Management protocol, see Web Services for Management (WS–Management).

Components of WinRM and Hardware Management

The following is a list of components and features that are supplied by WinRM and hardware monitoring:

  • WinRM Scripting API

    This scripting API enables you to obtain data from remote computers using scripts that perform WS-Management protocol operations.

  • Winrm.cmd

    This command–line tool for system management is implemented in a Visual Basic Scripting Edition file (Winrm.vbs) written using the WinRM scripting API. This tool enables an administrator to configure WinRM and to get data or manage resources. For more information, see the online help provided by the command line Winrm /?.

    Windows Server 2003 R2:  For this command to work, the Hardware Management feature must be installed through Add/Remove System Components under Management and Monitoring Tools in Control Panel.

  • Winrs.exe

    This command line tool enables administrators to remotely execute most Cmd.exe commands using the WS-Management protocol. For more information, see the online help provided by the command line Winrs /?.

    Windows Server 2003 R2:  This command is not available.

  • Intelligent Platform Management Interface (IPMI) driver and WMI provider

    Hardware management through the Intelligent Platform Management Interface (IPMI) provider and driver enables you to control and diagnose remote server hardware through BMCs when the operating system is not running or deployed.

    For more information, see the IPMI Provider.

  • WMI service

    The WMI service continues to run side-by-side with WinRM and provides requested data or control through the WMI plug-in. You can continue to obtain data from standard WMI classes, such as Win32_Process, as well as IPMI-supplied data. For more information about configuration and installation required for WinRM, see Hardware Management Introduction.

  • WS-Management protocol

    WS-Management protocol, a SOAP-based, firewall-friendly protocol, was designed for systems to locate and exchange management information. The intent of the WS-Management protocol specification is to provide interoperability and consistency for enterprise systems that have computers running on a variety of operating systems from different vendors.

    WS-Management protocol is based on the following standard web service specifications: HTTPS, SOAP over HTTP (WS-I profile), SOAP 1.2, WS-Addressing, WS-Transfer, WS-Enumeration, and WS-Eventing. For more information about the current draft of the specification, see the Management Specifications Index Page.

Working with WinRM

For more information about writing WinRM scripts, see Using Windows Remote Management.

The following table lists topics that provide information about the WS-Management protocol, WinRM and WMI, how to specify management resources such as disk drives or processes.

TopicDescription
Installation and Configuration for Windows Remote Management The WinRM listener requires configuration on both client and server computers.
Windows Remote Management Architecture Diagram that illustrates the components of WinRM and which components are found on client and server computers.
WS-Management Protocol Description of the public standard WS-Management protocol for remotely sending and receiving management data to any computer device that implements the protocol.
Scripting in Windows Remote Management The WinRM scripting API is similar to the actions of the WS-Management protocol. Data retrieved by scripts is formatted in XML, not objects.
Authentication for Remote Connections WS-Management protocol maintains security for data transfer between computers by supporting several standard methods of authentication and message encryption.
Windows Remote Management and WMI Because WinRM is integrated with Windows Management Instrumentation (WMI), you can obtain WMI data with scripts or applications that use the WinRM Scripting API or through the Winrm command-line tool.
Resource URIs A resource URI is an identifier for a management operation or value. For example, disk drives represent a type of resource.
Remote Hardware Management The IPMI provider supplies classes and data that describe the baseboard management controller (BMC) hardware management domain, the BMC computer systems in the domain, and the BMC sensors. Other objects represent the BMC System Event Log (SEL) and the messages in the log.
Events You cannot obtain events through WinRM scripting, but you can use the Wevtutil.exe command-line tool to view Event Collector events.

 

 

 

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.