Having Sysprep Pending on a Shutdown Image

Okay so here is what I am planning for a new deployable image. I would have the computer setup with our general software installed like I always do, with no license keys entered or anything like that.

However now I would finish setting up the pc before creating the master image with a sysprep set to run and tell it to shut down and not restart. Basically where every new system that is imaged would run sysprep from the first boot. This is done to generate new id numbers and to elimate trust relaitonship issues on the network due to all of the pcs imaged having the same id number.

My question is would having sysprep pending on a shut down cause every imaged pc to boot up into sysprep after the image and assign it still the same id since it was a pending sysprep on the image.

I am doing this in an attempt to fix an issue we are having where we get a "trust relationship has failed with the domain" issue that we are seeing now when some user try to login. We can fix this by rejoining the system to the domain through the local administrator account. Would running sysprep and generating a new SID cause this issue to go away on the new machines since they would have different SID numbers?
LVL 6
MISOperationsAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Lee W, MVPConnect With a Mentor Technology and Business Process AdvisorCommented:
Do you think Sysprep ONLY resets SIDs?

Why wouldn't you run SYSPREP as the last step in the image BEFORE shutdown and then image after?

(If you use WDS, you HAVE to run sysprep as the last step or WDS won't detect the partition as ready for imaging)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.