Microsoft KB Archive/229798

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 17:05, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Knowledge Base


Article ID: 229798

Article Last Modified on 2/27/2007



APPLIES TO

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional Edition
  • Microsoft Windows 2000 Datacenter Server



This article was previously published under Q229798

SYMPTOMS

When you try to use the Winmsd command, the Microsoft System Information console (Msinfo32.exe) may start instead.

CAUSE

This issue occurs because the Winmsd tool is not included with Windows 2000. This tool has been replaced with Msinfo32.exe in Windows 2000.

RESOLUTION

To work around this issue if you want to use Msinfo32.exe to connect to Microsoft Windows NT 4.0-based computers, please see the following article in the Microsoft Knowledge Base:

229796 Cannot Use MMC to Connect to a Remote Windows NT 4.0-Based Computer


NOTE: If network connectivity is required without the full feature set of Msinfo32.exe and the use of Windows Based Enterprise Management (WBEM), copy the Winmsd utility into the %Systemroot%\System32 folder to replace the Winmsd stub that refers to Msinfo32.exe.

STATUS

This behavior is by design.

MORE INFORMATION

The following article in the Microsoft Knowledge Base details the process of installing WBEM on a Windows NT 4.0-based computer to enable Msinfo32.exe connectivity:

229796 Cannot Use MMC to Connect to a Remote Windows NT 4.0-Based Computer



Additional query words: 2000

Keywords: kbprb kbui KB229798