[RESOLVED] Win2k Cloning

[SpongeHead]

I am cloning 20 pc's using Ghost2001, win2k SR2. The 1st pc cloned ok but the next two won't logon as admin or user, I can change the IP address but not the pc name. Do I need a CID patch?

[Ya_know]

Ghost Walker. It is used to apply a new SID (Security IDentifier) when cloning NT or 2K. I only have a brief experience using it, and am not sure where you could get it. Check the same source you got that version of Ghost...or i am sure someone will post...

[Ya_know]

Something is going on with
this thread. we bot got double posts...

[MacGyver]

Well this thread is about Cloning, isn't it? <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0">

[Ya_know]

That was probably one of the better laughs I have had in a while. Thanks, I needed that!

[Sowulo]

Originally posted by MacGyver:
<STRONG>Well this thread is about Cloning, isn't it? <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0"></STRONG>

ROFLMAO! <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0"> <IMG SRC="smilies/biggrin.gif" border="0">

[DigUm]

Let me think this thru:

1.Since all your computers had the name at one time, the sys is confus-ed, let's try and fix it.
2.Make sure your ip's are proper, then make them join a workgroup. Now reboot, oh by the way make sure your admin account is proper.
3.After the reboot, log in as admin, make the computers join the domain, then reboot.
4.Should work now.

-DigIt!!

[Ya_know]

Originally posted by DigUm:
<STRONG>1.Since all your computers had the name at one time, the sys is confus-ed, let's try and fix it.
2.Make sure your ip's are proper, then make them join a workgroup. Now reboot, oh by the way make sure your admin account is proper.
3.After the reboot, log in as admin, make the computers join the domain, then reboot.
-DigIt!!</STRONG>

Your advise will not work with NT on a Domain. NT4 and 2k(NT5) will uniquely identify the PC with a SID (Security IDentifier). Only one of these SID's can be added to a Domain. Significant problems will be presented when you try to add cloned systems to the same Server Manager for Domains. (I know, in 2k there is active directory…If anyone has insight there, please fill in the blanks)

Ghost Walker will provide the opportunity to change the Network name (Netbios name); during that process it will also change the SID for you automaticly. Thus giving you the chance to be unique from the clone or ghost image. At that point odds are slim that the SID will match anything else on the network, even if you have over 5000 nodes. You have a better chance of hitting the lottery in three states on the same week. (Of course this is an undocumented statistic)

Scroll to SID: S-1-5-18 in this link, you will see where I get some of this...
Well Known Security Identifiers in Windows 2000

I believe Sysprep will provide some assistance as well, unfortunately I've never used it. Check this link for a start:
System Preparation Tool (Sysprep) Script File Keys

[DigUm]

I have had this experience with Cloning.

We cloned over 12 machines that were separate from the main domain. They all had NT4 cloned on them. What I fear, since I didn't use the Symantec Console to clone these, is that if these computers ever were to join the main domain there would problems due to the SID hasn't been changed on these comps.

Symantec emailed me about a problem I was having in Win2000 when I was trying to clone other comps from an original and I was trying to use the scripting tool in the Symantec Ghost Console to change the computer names with each clone. They say keep the same # of characters when assigning names to the clones (as well as check the SID change box).

By the way if you ever have funny errors pop up when logging onto a domain that you have always been able to log into, log into the local machine, then rejoin the domain thru the Network Wizard. You will probably get log in errors after cloning a comp. <IMG SRC="smilies/eek.gif" border="0">

[Penman]

You can change the SID once your computer is up and running using this little program:

newSID

works fine on NT, never tried it on 2000 though!

[SpongeHead]

I am using sysprep & it all seems to be working fine now.

Thanks 4 the help