Windows Forum

Ask something
Discussion Locked

SIDs and imaged XP computers

0 helpful
9 replies

by sue t

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I will be using an image on computers and need to know if I need to do anything about the SID on each computer after it has been imaged or not. We use workgroups on our network and we are not using Active Directory but we may in the near future. Is there anything else other than changing the computer name on each PC that I need to do?

9 replies

by sue t

Poster rated this answer. Thank you. I figured I would have to do it and you confirmed it. I downloaded the program and it works great.

by sue t

Poster rated this answer. Thank you. I used sysprep before but I did find out that the utility Darts32 pointed me to is faster to do than sysprep.

by mrjay67

Well technicly you should use "sysprep" or similar program for changing the sid and such. However we have a Netware network and dont use domains(ust workgroups) and have not had any known problems from imaging without sysprep. I know this is not the "correct" way but it works for us. We do use Symantec Ghost for imaging(but that shouldnt really matter). I think you might see more problems in a true domain enviroment. Im out of practice with domains though.

hth

Jason

by sue t

Poster rated this answer. Thank you for replying but it looks like we will be moving to active directory in the very near future and I would like to not have to revisit every computer in the event identical SIDs turns out to be a problem.

by d_v ant

Check the documentation of the imaging software you are using to see if it reets the SID. Symantec's Ghost version 7.5 and later do. Earlier versions may as well, but 7.5 and above definitely do. The same may be true for what you are using. If not, sysrep will do the job.

by sue t

Poster rated this answer. I use Ghost and didn't realize it did that. Thank you.

This discussion is closed to new replies.