SysPrep 1

[windowsfan]

If I create PC image before joining that PC in the domain and than copy that image on different PC and than join them on the domain.
What is wrong with this? Will it have same SID on pc?
When you join a PC on a domain it gets new SID, right?

 

[SDPT]

no, they should have the same SID.

obtain a new SID:

http://www.microsoft.com/technet/sysinternals/Utilities/NewSid.mspx

_________________________________
IBM CP, MCP 2000, E60 driver ;-)

 

[windowsfan]

does it matter if I use same image on all pc's and dont change SID?
I guess not as all the PC's are part of domain and not workgroup.

What if you change the SID on existing PC on a domain, will it run normal after that?

 

[SDPT]

Well you might have to rejointhe domain.

I always did....just in case.

replying to the question:

"does it matter if I use same image on all pc's and dont change SID?"

http://www.microsoft.com/technet/sysinternals/Utilities/NewSid.mspx

or:

The problem with cloning is that it is only supported by Microsoft in a very limited sense. Microsoft has stated that cloning systems is only supported if it is done before the GUI portion of Windows Setup has been reached. When the install reaches this point the computer is assigned a name and a unique computer SID. If a system is cloned after this step the cloned machines will all have identical computer SIDs. Note that just changing the computer name or adding the computer to a different domain does not change the computer SID. Changing the name or domain only changes the domain SID if the computer was previously associated with a domain.

To understand the problem that cloning can cause, it is first necessary to understand how individual local accounts on a computer are assigned SIDs. The SIDs of local accounts consist of the computer's SID and an appended RID (Relative Identifier). The RID starts at a fixed value, and is increased by one for each account created. This means that the second account on one computer, for example, will be given the same RID as the second account on a clone. The result is that both accounts have the same SID.

Duplicate SIDs aren't an issue in a Domain-based environment since domain accounts have SID's based on the Domain SID. But, according to Microsoft Knowledge Base article Q162001, "Do Not Disk Duplicate Installed Versions of Windows NT", in a Workgroup environment security is based on local account SIDs. Thus, if two computers have users with the same SID, the Workgroup will not be able to distinguish between the users. All resources, including files and Registry keys, that one user has access to, the other will as well.

Another instance where duplicate SIDs can cause problems is where there is removable media formated with NTFS, and local account security attributes are applied to files and directories. If such a media is moved to a different computer that has the same SID, then local accounts that otherwise would not be able to access the files might be able to if their account IDs happened to match those in the security attributes. This is not be possible if computers have different SIDs.

An article Mark has written, entitled "NT Rollout Options", was published in the June issue of Windows NT Magazine. It discusses the duplicate SID issue in more detail, and presents Microsoft's official stance on cloning. To see if you have a duplicate SID issue on your network, use PsGetSid to display machine SIDs.


_________________________________
IBM CP, MCP, (Cientist, partime)

http://good-times.webshots.com/photo/2761403060074648262gLrhkV?vhost=good-times

 

[windowsfan]

Thanks SDPT