SYSPREP to change SID "after" image restore

Hi all,

I know I can use sysprep to prepare an image so it generates a unique SID. My questions is whether its ok to do this "after" restoring an image to a PC.

I have two Dell machines. One had the factory image which I used to create a restore usb from the factory.wim. If I use that restore USB to reimage the other PC (same exact model and hardware) it works just fine, but the SID is set to the same as the machine where I pulled the factory .wim.

To change the SID I simply open up sysprep on the second PC and ran it to out of box, generalize and reboot. System reboots, I simply have to go through the setup process again and it changes the SID. Are there any problems changing it this way?
binovpdAsked:
Who is Participating?
 
Joshua GrantomConnect With a Mentor Systems AdministratorCommented:
you can do it that way but it isnt the recommended way. If you are only doing it for this pc and they are exactly the same then it is ok. Just don't use this image for any other machine.

If you are planning mass deployment, get an image that is sysprepped before image creation.
0
 
binovpdAuthor Commented:
Hi Joshua,

I am not doing a mass deployment. We have several employees that all use the same Dell model and config. Some of these machines were downgraded to Windows XP and the restore partition removed. I created a boot usb with the factory.wim from one of the machines so I can easily restore these systems (about 9 PC's) to their factory settings with a clean image restore. I know mass deployment would be better to create a gold image restore, but for such a few number of PC's I just restore from the factory.wim and then run sysprep after the fact so each machine is set with a unique SID. I don't believe that should be a problem.
0
All Courses

From novice to tech pro — start learning today.