An update is available for the Windows Remote Management feature in Windows Server 2003 and in Windows XP

An update is available for the following operating systems:

• Windows Server 2003 with Service Pack 2
• Windows Server 2003 with Service Pack 1
• Windows XP with Service Pack 2

This update adds a new feature to Windows Remote Management (WinRM). This update also updates the version of Windows Remote Management that is included with Windows Server 2003 R2. Windows Remote Management improves hardware management in a network environment in which various devices run various operating systems. Windows Remote Management uses an interoperable standard protocol to help you monitor and manage computers.

The new feature uses the WS-Management industry standard. WS-Management is a Web service-based protocol that uses the HTTP protocol and the HTTPS protocol for transport. Therefore, WS-Management is firewall-friendly.

Windows Remote Management provides a command-line interface that you can use to perform common management tasks. Windows Remote Management also provides a scripting API so that you can write Windows Script Host-based system administration scripts. You can use scripts to monitor the state of server hardware by communicating with a baseboard management controller (BMC). A BMC is a micro-controller that is connected to the processor board of a server. Because the BMC has its own network adapter, the BMC can monitor conditions even when the server is off or when the server is malfunctioning.

Update information

The following file is available for download from the Microsoft Download Center:

Download the WS-Management v1.1 package now. For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base: Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.

Service pack information

A supported feature that modifies the default behavior of the product is now available from Microsoft, but it is only intended to modify the behavior that this article describes. Apply it only to systems that specifically require it. This feature may receive additional testing. Therefore, if you are not severely affected by the lack of this feature, we recommend that you wait for the next service pack that contains this feature.

To obtain this feature immediately, download the feature by following the instructions later in this article or contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

Installation instructions

You must uninstall the beta version of Windows Remote Management before you install this update.

If you want to use Intelligent Platform Management Interface on a computer that is running Windows Server 2003 R2, we recommend that you install the optional Windows Hardware Management component before you install this update.

Be aware that this update will not work if you apply the update in the following sequence:

1. You apply this update on a computer that is running Windows Server 2003 with Service Pack 2.
2. You upgrade the system to Windows Server 2003 R2.
3. You install the Windows Hardware Management optional component on the Windows Server 2003 R2-based computer.

This behavior occurs because this update and the Windows Hardware Management optional component share common files. The files in this update are overwritten even though the "Add or Remove Programs" Control Panel item displays this update in the list of installed programs. To work around this behavior, reinstall this update.

Post-installation instructions

On a Windows Server 2003 R2-based computer that has the Windows Hardware Management optional component installed, the WsmanSelRg collector-initiated subscription collects events form the BMC. This subscription has a URI property that is set to wsman:microsoft/logrecord/sel. After you apply this hotfix, the WsmanSelRg subscription will not work until you set the URI property to the following:To set the URI property, run the following command at a command prompt:

Uninstallation instructions

To uninstall the version of Windows Remote Management that this update provides, follow these steps:

1. Click Start, click Run, type appwiz.cpl, and then click OK.
2. Click to select the Show updates check box.
3. If you are running an x86-based version of Windows XP, select Windows Remote Management (KB936059).
   
   If you are running an x64-based version of Windows XP, select Update for Windows XP (KB936059).
   
   If you are running Windows Server 2003, select Update for Windows Server 2003 (KB936059).
4. Click Remove.

Prerequisites

To apply this update on a Windows XP-based computer, you must have Windows XP Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base: To apply this update on a Windows Server 2003-based computer, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base: For Windows Remote Management to work correctly in the specific scenarios that are described here, we recommend that you apply the hotfixes that are described in the following Microsoft Knowledge Base articles:

• 898708 FIX: IIS 6.0 may send an "HTTP 100 Continue" response in the middle of the response stream when you send a POST request
  Note Hotfix 898708 is required when you use certificates for authentication. If you do not apply hotfix 898708, you may receive the following error message:
  The client cannot connect to the remote host specified in the request. Verify that the service on the remote host is running and is accepting requests.
  You may use the following command to analyze the state of the WinRM service and to configure the service, if necessary: "winrm quickconfig".
• 899900 Windows HTTP Services does not let you append a port number to the service principal name in a program or service when you use Kerberos authentication on a Windows Server 2003 S899900-based computer
  Note Hotfix 899900 is required when you communicate with a WS-Management endpoint that uses Kerberos authentication and that includes the port number in the Kerberos service principal name (SPN).

Another hotfix is required if you want to create an entry in the certificate mapping table for a user account that is a member of the Administrators group. If you do not apply this hotfix, you may receive the following error message:

Restart requirement

If you install this update on a Windows Server 2003 R2-based computer that has the Windows Hardware Management optional component installed, you must restart the computer for Windows Remote Management events to route to the correct System log. Otherwise, you do not have to restart the computer.

Update replacement information

This update does not replace any other updates.

File information

The English version of this update has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with Service Pack 2, x86-based versions

Windows Server 2003 with Service Pack 2, x64-based versions

Windows Server 2003 with Service Pack 1, x86-based versions

Windows Server 2003, x64-based versions

Windows XP with Service Pack 2, x86-based versions

Windows XP with Service Pack 2, x64-based versions

Windows XP, x64-based versions

For more information about the Windows Remote Management Client Shell API, visit the following Microsoft Developer Network Web site:For more information about the Windows Event Collector API, visit the following Microsoft Developer Network Web site: For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: