Windows NT 3.51 Computer Object Is Not Created in the Computers Container (243550)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
This article was previously published under Q243550 SYMPTOMS
When a computer running Microsoft Windows NT 3.51 Workstation/Server joins a Windows 2000 domain, a computer object is not created in the Computers container. Instead, an account is created in the Users container. The account is named computer$ (where computer is the name of the workstation or server). The computer successfully participates as a domain member.
CAUSE
When a computer running Windows NT 3.51 joins a domain, a user account is created, which is then changed to a computer account. As a result, the machine account is listed as computer$ in the Users container.
RESOLUTION
To resolve this problem, you must first create the computer object prior to joining the Windows NT 3.51-based computer to the domain. To do this, use the appropriate method.
NOTE: If the computer is already a domain member, you must first delete the computer$ user object with Active Directory Users and Computers or Server Manager before following these steps from a Windows 2000 domain controller. Using Server Manager- Click Start, click Run, type srvmgr.exe, and then click OK.
- On the File menu, click Computer, and then click Add to Domain.
- Click Windows NT Workstation or Server, type the computer name, click Add, and then click Close.
- Configure the Windows NT 3.51-based computer to join the domain.
Using Active Directory Users and Computers- Click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers.
- Right-click the Computers container, click New, and then click Computer.
- Type the name of the Windows NT 3.51-based computer you want to add.
- Click to select the Allow pre-Windows 2000 computers to use this account check box, and then click OK.
- Configure the Windows NT 3.51-based computer to join the domain.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows 2000.
MORE INFORMATION
Modification Type: | Major | Last Reviewed: | 9/24/2003 |
---|
Keywords: | kbbug kbenv kbpending KB243550 |
---|
|