Question re: Ghosting and computers to be networked

[MotionMan]

This is a dumbed-down version of the situation and question:

I have five identical computers that I will be setting up. My plan is to set one up and Ghost that setup to the drives of the other four computers.

My question is this:

What are ALL of the settings in Windows XP Pro I need to change/set to make it so that the computers do not look like the same computer a) to each other (network conflicts) and b) to other people using the network (confusion)?

(BTW, I am not worried about IP conflicts as I can get them uniquely assigned once the computers join the network.)

Like I said, this is a dumbed-down version of the situation and question, so I can provide more detailed information if needed.

Thank you very much for your assistance.

MotionMan

 

[BornStar]

It's been a while since I've done this but why not just use Sysprep?

 

[MotionMan]

Originally posted by: BornStar18
It's been a while since I've done this but why not just use Sysprep?

I will look into using Sysprep instead of Ghost, as that seems to create identical computers, but I am not sure that answers my question regarding networking settings.

Thanks.

MotionMan

 

[BornStar]

Sysprep prepares the computer before you use Ghost. You use them together, they aren't competitors. Sysprep works to remove all of the identifying features of the OS (computer name, IP, license key, admin password, so on).

 

[MotionMan]

Originally posted by: BornStar18
Sysprep prepares the computer before you use Ghost. You use them together, they aren't competitors. Sysprep works to remove all of the identifying features of the OS (computer name, IP, license key, admin password, so on).

I did not realize that. Then Sysprep does sound like something I will try prior to Ghosting the original drive.

Thanks!

MotionMan

 

[JDMnAR1]

After loading the image onto your additional machines (but before booting them for the first time) run ghstwalk.exe. It will allow you to rename the machine and generate a new SID (and propagate those changes throughout the registry, etc) to avoid conflicts.

 

[MotionMan]

Originally posted by: JDMnAR1
After loading the image onto your additional machines (but before booting them for the first time) run ghstwalk.exe. It will allow you to rename the machine and generate a new SID (and propagate those changes throughout the registry, etc) to avoid conflicts.

I assume that is a program on the Ghost (or in this case, Norton SystemWorks) disk?

MotionMan

 

[JDMnAR1]

Originally posted by: MotionMan

Originally posted by: JDMnAR1
After loading the image onto your additional machines (but before booting them for the first time) run ghstwalk.exe. It will allow you to rename the machine and generate a new SID (and propagate those changes throughout the registry, etc) to avoid conflicts.

I assume that is a program on the Ghost (or in this case, Norton SystemWorks) disk?

MotionMan

Yes, it ships with Ghost.

 

[MotionMan]

Originally posted by: JDMnAR1

Originally posted by: MotionMan

Originally posted by: JDMnAR1
After loading the image onto your additional machines (but before booting them for the first time) run ghstwalk.exe. It will allow you to rename the machine and generate a new SID (and propagate those changes throughout the registry, etc) to avoid conflicts.

I assume that is a program on the Ghost (or in this case, Norton SystemWorks) disk?

MotionMan

Yes, it ships with Ghost.

Great. I will give it a look.

MotionMan

 

[JackBurton]

Originally posted by: JDMnAR1
After loading the image onto your additional machines (but before booting them for the first time) run ghstwalk.exe. It will allow you to rename the machine and generate a new SID (and propagate those changes throughout the registry, etc) to avoid conflicts.

Um, that's one of the main functions of Sysprep.

 

[JDMnAR1]

Originally posted by: JackBurton

Originally posted by: JDMnAR1
After loading the image onto your additional machines (but before booting them for the first time) run ghstwalk.exe. It will allow you to rename the machine and generate a new SID (and propagate those changes throughout the registry, etc) to avoid conflicts.

Um, that's one of the main functions of Sysprep.

Correct, but if he isn't familiar with Sysprep, it is much easier to use ghstwalk.

 

[MotionMan]

Originally posted by: JDMnAR1

Originally posted by: JackBurton

Originally posted by: JDMnAR1
After loading the image onto your additional machines (but before booting them for the first time) run ghstwalk.exe. It will allow you to rename the machine and generate a new SID (and propagate those changes throughout the registry, etc) to avoid conflicts.

Um, that's one of the main functions of Sysprep.

Correct, but if he isn't familiar with Sysprep, it is much easier to use ghstwalk.

I am not familiar with either, so I will take a look at both.

Thanks for the suggestions. I am glad there are programs out there to do what I need.

MotionMan

 

[JackBurton]

Originally posted by: JDMnAR1

Originally posted by: JackBurton

Originally posted by: JDMnAR1
After loading the image onto your additional machines (but before booting them for the first time) run ghstwalk.exe. It will allow you to rename the machine and generate a new SID (and propagate those changes throughout the registry, etc) to avoid conflicts.

Um, that's one of the main functions of Sysprep.

Correct, but if he isn't familiar with Sysprep, it is much easier to use ghstwalk.

Ah, I see what you were trying to say. Gotcha.

 

[MotionMan]

OK, I have a related problem. I have set up one computer with a login of, say, "Joe". When installing all the programs, they are "registered" to "Joe". If I Ghost the HD and I want the login to be "Jane", how do I get rid of Joe from Windows entirely, including from the program registrations?

(BTW, I got the networking issue licked (I hope)).

MotionMan

 

[MotionMan]

Bump.

MotionMan

 

[nweaver]

do the master as administrator, don't add the user. add users after ghosting

 

[nweaver]

btw, if this is "dumbed down" and we are talking more then 5 machines (i.e. several hundred) you might look at an enterprise imaging product. I'm not to fond of the ghost enterprise stuff, but we use Altiris Deployment solution in house here, and it works great.

 

[MotionMan]

Originally posted by: nweaver
do the master as administrator, don't add the user. add users after ghosting

I thought about that, but since I want all the logins to be identical, I was hoping there was a way to set up one and change the name somehow after ghosting.

(I am talking about 6 machines.)

MotionMan

 

[JackMDS]

I can describe what I do when it involves peer to peer Network.

I have one computer with two Mobile Racks (about $20 each).

This computer can boot from Floppy CD and either of the HD, and has Acronis True image 9 installed.

I put the hard drive to be copied as secondary Drive and make a True Image file of the Drive.

I put the new hard drives (one at the time) and ?Ghost? to True Image to them.

The New hard Drive goes to the New Computer.

Boot, run this free util. http://www.sysinternals.com/utilities/newsid.html it lets you change the name and its create a new Sys ID. Reboot, Done.

No Sysprep or any other special process. Depending on the size of the drive it is a fast clean process.

:sun:

P.S. Depending on your original OS Lic., you might need to take care of WinXP activation.

 

[spikespiegal]

Ghost Walker only helps you if you are in a workgroup.

If you're machines are going to be in a domain/AD, you should Ghost them *before* joining it. Then, once each machine get's joined to the domain after they are ghosted, the Domain prefix that gets generated is unique anways and Ghost Walker is not needed.

Sysprep is highly recommended, especially for XP.