Microsoft KB Archive/897571

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

Article ID: 897571

Article Last Modified on 12/5/2007

-

APPLIES TO


 * Microsoft COM+ 1.5
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
Consider the following scenario. You use the Microsoft Windows Management Instrumentation (WMI) DCOM application to configure a DCOM static TCP endpoint for WMI on a computer that is running Microsoft Windows Server 2003. When you do this, the static endpoint is ignored. This problem occurs when you connect to the remote computer through a firewall.

Note This problem does not occur on a computer that is running Microsoft Windows 2000.



CAUSE
This problem occurs because the Winmgmt.exe process runs in an Svchost.exe instance.



Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

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:

897667 Availability of Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6

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:  Install Windows Server 2003 Post-Service Pack 1 COM+ 1.5 Hotfix Rollup Package 6 and the hotfix that is mentioned in this article. Click Start, click Run, type Cmd, and then click OK. At a command prompt, type net stop winmgmt, and then press ENTER. Click Start, click Run, type Notepad, and then click OK.</li>  Copy the following code into Notepad. Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SvcHost] &quot;Winmgmt&quot;=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] &quot;CoInitializeSecurityParam&quot;=dword:00000001 &quot;AuthenticationCapabilities&quot;=dword:00003020 &quot;CoInitializeSecurityAppID&quot;=&quot;{D16904E8-7F7D-4821-ACF5-FDE160CBE65E}&quot;

[HKEY_CLASSES_ROOT\AppID\{D16904E8-7F7D-4821-ACF5-FDE160CBE65E}] @=&quot;Svchost_winmgmt&quot; &quot;EndPoints&quot;=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. </li> Save the file that you created in step 5. Name the file Winmgmtsvc.reg.</li> Double-click Winmgmtsvc.reg, click Yes to add the information to the registry, and then click OK.</li> Click Start, click Run, type sc config winmgmt binPath= &quot;%systemroot%\system32\svchost.exe -k winmgmt&quot;, and then click OK.

Notes <ul> This command configures the WMI service to run in a separate process.</li> In this command, the quotation marks are required.</li> In this command, the space after binPath= is required.</li></ul> </li> Click Start, click Run, type %windir%\system32\com\comexp.msc, and then click OK.</li> Under Console Root, expand Component Services, expand Computers, expand My Computer, and then expand DCOM Config.</li> Right-click Svchost_winmgmt, and then click Properties.</li> On the Endpoints tab, click Add.</li> Click Static endpoint, configure the static endpoint that you want, and then click OK two times.</li> Click Start, click Run, type Cmd, and then click OK.</li> At a command prompt, type net start winmgmt, and then press ENTER.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Windows Server 2003 Service Pack 2.

Keywords: kbwinserv2003sp2fix kbfix kbcode kbbug kbhotfixserver kbqfe KB897571

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.