Windows 2000 Is Unexpectedly Installed On a Newly Created Account During Remote Installation

This article was previously published under Q328725
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to reinstall Windows 2000 through the Remote Installation Service (RIS), you may notice that the operating system is unexpectedly installed to a new account that was created during installation.
This behavior may occur if the RIS server uses Windows 2000 service pack 3 (SP3), and your domain controller uses Windows 2000 service pack 2 (SP2).

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language. The English version of this fix should have the following file attributes or later:
Date         Time    Version         Size     File name     Platform-------------------------------------------------------------------09-Jun-2002  12:39   5.0.2195.6050   93,968   Binlsvc.dll   x86 				
Microsoft has confirmed that this is a problem in Microsoft Windows 2000. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
When you use RIS to install a client, Binlsvc (which is a component of RIS) creates the Machine Account object (MAO). When this occurs, the client Universally Unique Identifier (UUID) (a 32-character number in the Pre-Boot execution [PXE] read-only memory [ROM]) is added to the MAO, identifying it as a managed computer account. This way, if the client is ever reinstalled or re-imaged it will use the same computer account and receive the same computer name.

Identyfikator artykułu: 328725 — ostatni przegląd: 10/26/2013 17:31:46 — zmiana: 2.5

Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Server

  • kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbqfe kbwin2ksp4fix kbsetup kbbug kbfix KB328725
ERROR: at System.Diagnostics.Process.Kill() at Microsoft.Support.SEOInfrastructureService.PhantomJS.PhantomJSRunner.WaitForExit(Process process, Int32 waitTime, StringBuilder dataBuilder, Boolean isTotalProcessTimeout)