|
Home > Archive > Windows 2000 track general > September 2001 > Imaging and sid?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| HOOLIGAN 2001-09-02, 2:44 pm |
| Hypothetical question here.
On my one domain network, we install by imaging from the server(with a sid changer), as all machines are identical. If I were to disconnect one computer and once i put a new computer in its place with Identical Netbios,ip etc it works fine, but If i were
to put the original machine back it can no longer log on the the network .I assume its to do with the SID, but which SID? or SIDs?
Cheers in advance
Hooligan | |
| dentonb2000 2001-09-06, 11:13 am |
| When you say put the original machine back on the network, do you mean something low-level like pinging or something higher as in Domain logon? | |
| relder 2001-09-08, 7:12 am |
| When you join the domain, the dc adds the computer account to active directory. Although it appears as a NetBIOS or FQDN under Active Directory Users and Computers, AD is actually using the SID. Thus--it doesn't more than one machine with the same number.
Why not use the SYSPREP tool. This will remove all references to the SID. Then image the drive. Roll out the image to your clients. At first boot a mini setup screen appears requesting machine specific information and a new SID is created. You can write an unattended setup file for this portion if you want.
Rob Elder |
|
|
|
|