Changing ComputerName in Win2K (TRICKY..read -- UPDATE--)

[MrSharky]

Ok here's the current situtation...


At work I made an image of a laptop with the ComputerName = "changeme" and I added that computer to our domain (lets call the Domain = "work"). Now I have to send that image to our computer manufacturer and have them install it on all the new laptops that we buy from them. So when the computer arrives to our employees that are going to be using it, it would have all our software and settings already configured, except for 2 things:

1) The computer name has to be changed
2) the ip has to be "hard-coded"

My question is this, is there anyway that I have change the computername (without being on your network) thru the administrator account wether is be a program or a "safe" registry hack. I'll looking to incorporate this method into a "first-time" run only batch file. Let me know if there are any tips/tricks/programs that I could use to get this task done.

Thanks
Please email here or just PM me.

---UPDATE--- 2/26/2002 6:00pm

Okay, thanks for everyone input. I guess I need to be a little more specific. Here's how I see it all going down step by step:

1) I create an image of a laptop (by means of any imaging program, perferably norton ghost)
2) I send that image to computer manufacturer, and they load image onto laptop and send it to Site XYZ
3) When user Joe Blow starts up the machine, it does several things (in no particular order)

3a) it has to have the computer name changed (Admin will provide, in an email)

3b) it has to be added to our domain = "work" *see above (if not already done so in the orginal image)

3bi) in order for this computer to be added to our "work" domain, only certain users (admins) have rights to this new computer to our domain (with a unique name of course), the end user will not have access to change computer name

3c) restart


So here are some things I've tried:

-I've restore an image to the new laptop (the image is already part of the "work" domain). I then go to the Server domain consel and add a computer called PC123. Then I used ghostwalker to change orginal name (say PC000) on the laptop to PC123, but this error message comes up after I reboot and try to log in

"The sustem could not log you on. Make sure your Username and domain are correct, then type your password again. Letters in passwords must be typed using the correct case. Make sure that caps lock is not accidentally on."

-We can't let the end user have permission to add computers to our "work" domain. I'm looking for something so that when the new computer gets to the new location, the end user types in the new computer name (that we've given them in an email) and "BOOM"... away they go onto our domain and everything is peachy.!?!??!


Any more suggestions?? Please feel free to comment or ask anything about this complicated operation. I like how ghostwalk did everything but not sure why it won't sign onto the network. Does it have something to do with the SIDs, if so how do I tell the server to reconize a SID that I hardcode into a computer? Thanks again

 

[DAM]

See I have never been able to change the computer name once the computer has been added to the domain, what you can do is maybe not add them to a domain, then just change the name and add the domain at the same time, that way you avoid this.




dam()

 

[mmcwiz]

Best practice would be to run sysprep before taking the image. First use Setup Manager to create sysprep.inf which is basically an unatend.txt used to automatically answer setup questions. The questions that you want to answer manually when you pull down the image are left blank (ie IP address and PC name). Final step is to run sysprep.exe on the machine that you want to take the image of right before you take the image. When you pull that image down to a new machine a mini setup will run which will prompt for those things not answered by sysprep.inf (ie IP Address and PC name). I know that this explanation is a little hard to follow so I'll include a link will complete directions. The document covers a lot more than what you are trying to do here but if you skip to the section "Deploying the Desktop Using the Sysprep Utility " near the end it should answer all of your questions. If not just ask me about anything specific that you are having trouble with. It may be hard to tell by my crappy explanation but I've actually done this for thousands of machines.

Sysprep stuff

 

[Saltin]

You should never create an image of a computer that has been added to a Domain already.
You should leave the image in a workgroup.
Trust me on this one.

Sysprep is indeed a useful tool for scenarios such as this, but you must first wiegh the cost/benifits of doing it manually vs having sysprep automate the process.
If you are doing this for less than 30 machines, think about doing it manually. Sysprep is a bear to get working, and short of large scale roll-outs it is prohibitively time consuming to get working correctly.

 

[mmcwiz]

Saltin,
I can tell that you have tried to use sysprep before in the NT4 world and I feel your pain (he he). For W2K syprep could not be easier. A wizard will help you create the files you need and it takes about 5 minutes. Also for W2K in an Active Directory there are none of the problems with SID's that you?re familiar with in NT4. You can sysprep a member of the domain and then use that image with absolutely none of the ill affects that plagued NT4. Believe me I've done this many times with several configurations on thousands of PCs and its really very easy and straight forward.

 

[fastcobra]

don't add the "image" to the domain.....or more work for you.
Just make an image, use the image on all the laptops,
image laptops
change computername
run "ghostwalker" (to change the sid)
reboot,
add to domain,
reboot,
change ip (does not require reboot in win2k)
log on to network and add users,
you are done.

 

[SaigonK]

Sysprep will not change the hostname for you.
If you make your images using Sysprep BEFORE you Ghost them then you dont need to use Ghostwalker either....so do what fastcobra said but use sysprep to create your images so you can at least take out a few steps.

 

[Saltin]

<< Saltin,can tell that you have tried to use sysprep before in the NT4 world and I feel your pain (he he). For W2K syprep could not be easier. >>



To be honest with you, I have never Admin'd an NT4.0 network. I wouldnt want to. All of my paying jobs have been 2k/Xp related, thats what I know best.
I did not state that Sysprep was a bad tool. I stated that the cost of properly setting it up is something to keep in mind.
Often it is easier to simply re-name the desktops.
I understand how sysprep works. The amount of time and trouble it takes to properly implement it is prohibitive in CERTAIN cases.
I use a standard image, and define the software packages and desktop via GPO. That's my take.

Im not saying sysprep is an improper method to achieve the poster's goals. It just seems to me that his implementation is not anywhere near large enough to make it worth while.

My experience with images, tells me to
1) create image
2) install image
3) reaname box and reboot
4) add to domain.

Done.

 

[Santa]

Perhaps what Saltin is talking about is the answer file..

Sysprep in of itself is only a reversion tool. It reverts the system back to a state before a SID is issued and certain key information is entered. The reason you may want to use this utility is more or less to make the image.

The answer file is up to the administrator and situation whether there are certain information all stations have or not.

Oh and btw: if your computer vendor has a system where they can drop your image onto the desktops before shipping it to you I would check with them to see if they have a setup specialist to guide you through what is best practice for images.

I wouldn't just go off of the expereince you see here on the boards since how do you explain to your upper bosses that you understood so and so because you read a BBS?

Talk to someone there unless you fully firmly understand ghosting.. sysprepping, and the whole entire process from sent image.. restored image.. all the way down to what needs done when the preinstalled PC arrives.

 

[Santa]

Something to explain what Saltin is talking about and to back his methology of creating an image in workgroup first.


It is also recommended to clone workstations while they are members of a workgroup rather than a domain. The reason for this has to do with machine account names. If a Sysprep source computer is created with a computer name, that same computer name will be duplicated when the computer is cloned. Windows NT domains use the machine account name to establish trust relationships between the domain controllers and the workstations. If computers are added to the domain prior to being cloned, the computer name will need to be changed after the clone procedure is complete for this workstation to be able to participate in the domain. For this reason, it is best to prepare the computer as a workgroup member and then perform the clone procedure. After the installation is verified as successful and Sysprep has been run, the workstation can be added to the domain with a unique machine name.

Straight from Microsoft's web site.

 

[SaigonK]

Exactly!

NEither sysprep nor the Setup Manager or any answer file allow you to change the hostname, once it is set...thats it.
You HSOULD use sysprep for and Win2k/NT images you create and Microsoft will tell you so.
If you plan to get support for these images, they will tell you unless it was made with Sysprep then you are on your own.

They played that wonderful card with us when the good ol Citrix Farm crapped the bed!

 

[MrSharky]

Do you know where I might be able to get ghstwalk.exe.?? I have systemworks 2002, but can't seem to find it. Thanks

 

[mmcwiz]

Sysprep will allow you to change the hostname. It will also allow you to update drivers, change IP configuration, change Domain or even automatically join a specified Domain. For simple instructions on how to set all of this up in 30 minutes or less read This Link

 

[SaigonK]

It doesnt owrk though...it tells you it can change all that but i have yet to see it work.
i.e. the doc tells you that you are able to enter in DNS servers to be used by each new PC, but they dont populate because it sees the new nic as a different piece of hardware and wont apply thise settings to it.

The computer name does the same thing, I have done this hundreds of times and have yet to see a successful converion of the host name.
Setup manager wont do the tirck either, if need be call Microsoft, they will give you the same answer.

 

[Saltin]

It's exactly the answer file I am speaking of when I talk about the issues with sysprep. MMCwiz, the other poster's are correct when they mention that all the functionality you are promised with sysprep is not exactly delivered.

 

[mmcwiz]

I can only speak from my own experience. I have been able to use sysprep and driveimage pro to successfully do what MrSharky wants to do. I cannot speak to your environment or any issues you may have run into. I think that the best-case scenario (if time permits) would be for MrSharky to experiment with all of our suggested solutions and decide what works best for him in his situation. I respect your opinions and experience and believe that we share the common goal of trying to help each other.

 

[MrSharky]

.

 

[Woodie]

Here's my $.02

Assumption: You're building W2K clients for a W2K domain

Build your image (whatever way, I don't know what's best for you.), but make the images non-Domain members.
When you send a new workstation to a user, one of the admins (doesn't need to be a Domain Admin) creates a computer account for that user in the AD, under whatever OU is appropriate. On the computer object, he gives the USER the right to join that computer to the domain...(NB: just for that single computer). The admin then emails the computer name to the user, along with a short procedure.
The user fires up the workstation, logs in as some "local admin", and follows the procedure to change the computername, and add it to the domain. It will prompt him for a Domain ID/pword, and he can put in his own ID/pword.
Since you're not using DHCP, it sounds as if the user will have to modify that as well, potentially BEFORE the hostname change.
<reboot>
User can now login as themselves, and the computer is in the domain.

Pros:
User doesn't get any special rights to the Domain.
IT support doesn't have to go out and touch the machine.
User procedure is pretty simple GUI.

Cons:
IT has to create all the computer accounts.
User has to know the initial local Administrator password.
User has to do the initial setup procedure (which will generate calls to the helpdesk).

 

[MrSharky]

Thanks woodie for the breakdown. That helps!