Sysprep and new sid

[98616722]

Hi all.
I am setting up an image for dell laptops (winxp), and am not sure whether i need to run something like newsid to blank the sid of the laptop.
when i am running the sysprep tool, i choose no sidgen and reseal, and it informs me that if i am using it for an image that i will need to unchoose this. does thesysprep remove the sid or what should i do,

thanks!!

 

[bcastner]

Sysprep is being run after the installation has entered the GUI portion of the setup.

You need to seal prior to this point for the image to be SID-less.

If you are using these computers in a Domain, the SID issue is not relevant. If using them in a workgroup, follow the image install (prior to joing the network) by running Newsid.

 

[98616722]

cheers Bcastner.

am setting the machine up and copyin the profile into the default profile and then running the sysprep, when off the domain. then i am taking the image,they will be running on a domain environment, i thought that because they would be goin on a domain that it would need a new sid, surely pcs cant all have the same sid.

 

[bcastner]

When the machine join is done a new Domain SID is written that overwrites the SID and RID values of the local install.

 

[bcastner]

Which, by the way, should tell you that a Sysprep step is not required.

You may find some things of interest here:

http://unattended.msfn.org/index.htm

 

[98616722]

let me get this, u say that when i carry out the install,in which i add the machine to the domain,setup and remove it before i carry out the sysprep, that the imaged machines will all receive a new sid when they are being put out to the end user on the domain.

thanks

 

[bcastner]

If you chose to:
You could fully setup the machine without the machine join to the domain. Set the Workgroup name = Domain name. Install any and all applications desired Image that. Roll it out.

Then, for each machine, prior to the Domain machine entry being made for the machine, set the computer name and Domain settings as needed and do the machine join.

Duplicate SIDs aren't an issue in a Domain-based environment since domain accounts have SID's based on the Domain SID and not the SID created at installation.