Using Windows Remote Management

Windows Remote Management is intended to improve hardware management in a network environment with various devices running a variety of operating systems. The entire design of the service is focused on monitoring and managing remote computers by implementing an interoperable standard protocol.

Because the WinRM Scripting API and the WinRM C++ API implement and closely model the operations defined for the WS-Management protocol, scripts and applications receive streams of XML in response to requests. Input parameters to method calls must be constructed in XML. You can use the methods of the MSXML API to display or construct XML strings. For an example, see Displaying XML Output from WinRM Scripts.

The following list includes topics that describe how to use WinRM scripting:

Tracing WinRM Activity

Because WinRM obtains data through Windows Management Instrumentation (WMI), you can trace WMI activity that results from WinRM messages. Starting with Windows Vista, the WMI service does not use the WMI Log Files. Instead it uses Event Tracing (ETW) and events are available through the Event Viewer UI or the Evtutil command-line tool.

See Also

Windows Remote Management
About Windows Remote Management
Windows Remote Management Reference
Scripting in Windows Remote Management

Send comments about this topic to Microsoft

Build date: 11/2/2009

Tags :


Community Content

DSC_KE_MSFT
WinRM audit messages not always generated in security event log on Windows XP

The configuration for WinRM contains security descriptor string that is used to control access to resources using WinRM and the WS-Management protocol (run 'winrm configsddl -?' for details on how to modify this property). When this SDDL is changed so that audit messages should be logged when a user accesses a resource, those messages are not generated in the event log when running on Windows XP.


There is no known workaround for this issue on Windows XP.

Tags : winrm

Page view tracker