FIX: A DCOM static TCP endpoint is ignored when you configure the endpoint for WMI on a Windows Server 2003-based computer (897571)

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

To resolve this problem, you must have Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 installed on the computer in addition to the hotfix that is mentioned in this article. For more information about how to obtain Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix is not replaced by any later hotfix.

Registry information

You must create registry keys to apply the hotfixes that are contained in this package.

File information

This hotfix contains only those files that you must have to correct the issues that this article lists. This hotfix may not contain all the files that you must have to fully update a product to the latest build.

The English version of this hotfix 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 tool in Control Panel.Microsoft Windows Server 2003, Itanium architecture

   Date         Time   Version       Size    File name     Platform
   ---------------------------------------------------------------- 
   21-Apr-2005  08:15  5.2.3790.314  34,304  Svchost.exe   IA-64
   21-Apr-2005  08:15  5.2.3790.314  13,312  Wsvchost.exe  x86

Microsoft Windows Server 2003, x64

   Date         Time   Version        Size    File name 
   ------------------------------------------------------- 
   21-Apr-2005  08:15  5.2.3790.2426  25,600  Svchost.exe      
   21-Apr-2005  08:15  5.2.3790.2426  14,848  Wsvchost.exe

Microsoft Windows Server 2003, x86

   Date         Time   Version       Size    File name 
   ------------------------------------------------------ 
   21-Apr-2005  06:52  5.2.3790.314  13,312  Svchost.exe

Installation information

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, follow these steps:

1. Install Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 and the hotfix that is mentioned in this article.
2. Click Start, click Run, type Cmd, and then click OK.
3. At a command prompt, type net stop winmgmt, and then press ENTER.
4. Click Start, click Run, type Notepad, and then click OK.
5. Copy the following code into Notepad.

   Windows Registry Editor Version 5.00
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost]
   "Winmgmt"=hex(7):77,00,69,00,6e,00,6d,00,67,00,6d,00,74,00,00,00,00,00
   
   [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost\winmgmt]
   "CoInitializeSecurityParam"=dword:00000001
   "AuthenticationCapabilities"=dword:00003020
   "CoInitializeSecurityAppID"="{D16904E8-7F7D-4821-ACF5-FDE160CBE65E}"
   
   [HKEY_CLASSES_ROOT\AppID\{D16904E8-7F7D-4821-ACF5-FDE160CBE65E}]
   @="Svchost_winmgmt"
   "EndPoints"=hex(7):6e,00,63,00,61,00,63,00,6e,00,5f,00,69,00,70,00,5f,00,74,00,\
   63,00,70,00,2c,00,30,00,2c,00,34,00,33,00,32,00,31,00,00,00,00,00
   

   Note Use the Dcomcnfg.exe tool to set the port number. The port number 4321 in this code is an example.
6. Save the file that you created in step 5. Name the file Winmgmtsvc.reg.
7. Double-click Winmgmtsvc.reg, click Yes to add the information to the registry, and then click OK.
8. Click Start, click Run, type sc config winmgmt binPath= "%systemroot%\system32\svchost.exe -k winmgmt", and then click OK.
   
   Notes
   • This command configures the WMI service to run in a separate process.
   • In this command, the quotation marks are required.
   • In this command, the space after binPath= is required.
9. Click Start, click Run, type %windir%\system32\com\comexp.msc, and then click OK.
10. Under Console Root, expand Component Services, expand Computers, expand My Computer, and then expand DCOM Config.
11. Right-click Svchost_winmgmt, and then click Properties.
12. On the Endpoints tab, click Add.
13. Click Static endpoint, configure the static endpoint that you want, and then click OK two times.
14. Click Start, click Run, type Cmd, and then click OK.
15. At a command prompt, type net start winmgmt, and then press ENTER.