Changing Win2K Professional Computer Names

\[Editor's Note: Share your Windows 2000 and Windows NT discoveries, comments, problems, solutions, and experiences with products. Email your contributions (400 words or less) to r2r@win2000mag.com. Please include your name and daytime phone number. We edit submissions for style, grammar, and length. If we print your submission, you'll get $100. Submissions and listings are available online at http://www.win2000mag.com. Enter the article ID number in the InstantDoc ID text box.\]

We recently ghosted an image to install Windows 2000 Professional on 25 test workstations. After successfully deploying the image, we immediately faced the problem of how to change each computer's name from the image's original name to a unique name. We attempted to work around this problem by changing each computer's name on the Network Identification Properties dialog box. However, the systems rejected the new names regardless of whether we used Administrator usernames and passwords to make the change.

A few days later, we discovered that we should have selected WORKGROUP instead of DOMAIN during the name-change process. After we changed this selection and entered WORKGROUP in the Member of field, we could use an Administrator account to change each computer's name.

Discuss this Article 6

jim (not verified)
on Jan 17, 2001
I agree with Hans. Using the sysprep utility is the way to go! There is also a -nosidgen swithch that can be used with the utility.
Curtis Westwood (not verified)
on Feb 12, 2001
If you are already familiar with ghost then use the ghstwalk.exe utility from a generic dos boot disk. This allows you to change the computer name and SID.
Hans Van Miert (not verified)
on Jan 11, 2001
This way of working certainly works, but it takes a lot of time to change from workgroup to domain and change the computername. In my opinion it is better to use SysPrep, This program will launch a mini setup after deploying the image and there you can enter the computername, and the system will add it to the domain. With version 1.1 it is also possible to autodetect Mass Storage devices, so this will eliminate multiple ghost images. Version 1.1 with a manual for almost complete unattended installations

Please or Register to post comments.

IT/Dev Connections

Las Vegas
September 30th - October 4th

Paul ThurottYou'll have the opportunity to experience:
• The Microsoft
Technology Roadmap
• Office 365 Implementation
• Hyper-V Optimizing
• Windows 8 Deployment
and much more!

Come See Paul Thurrott & Rod Trent in Person!

Early Registration Now Open

Upcoming Training

Mastering SharePoint 2013: Succeeding, Not Just Surviving

Building on the success of the “Mastering SharePoint 2010” seminars, the presenters have updated the content to cover the latest and greatest SharePoint product: SharePoint 2013. While SharePoint 2013 is relatively new on the marketplace, the presenters have been working with SharePoint 2013 for well over a year, and have implemented it with a number of clients in production environments.

Register Now

Current Issue

May 2013 - The NameTranslate object is useful when you need to translate Active Directory object names between different formats, but it's awkward to use from PowerShell. Here's a PowerShell script that eliminates the awkwardness.

CURRENT ISSUE / ARCHIVE / SUBSCRIBE

Windows Forums

Get answers to questions, share tips, and engage with the Windows Community in our Forums.