Is sysprep necessary for Win 7 FOG Image capture & deployment

[jmak]

Hi Everyone

 

I've been using FOG for a couple of years to deploy Win 7 Pro and haven't been sysprepping the source machine before taking the image. This has worked and I haven't needed to run NewSID either.

 

I occasionally get the "the trust relationship between this workstation and the primary domain failed" issue - never when they're first deployed and randomly: sometimes I go months without seeing it. After extensive research (20 minutes on Google ) one of the causes that people mention is failure to sysprep. Could this be my problem? Or would that only cause the problem when I first tried to use the computer? Only asking now as I'm about to order another batch of laptops and am getting ready to prepare a new image.

 

Thanks as ever...

[round2it]

i would say yes it cant hurt.

 

i never used to sysprep and had alsorts of issues now after syspreping the image i have very little in the way of trust/relationship issues just 1 in the past 9 months

[mrstrong]

For what it's worth I'm always seeing "the trust relationship between this workstation and the primary domain failed"

happens on average on 1 pc per 100 pcs every month (rough estimate )

All machines are done via sysprep

I'm getting so quick at running the network ID wizard to join it back to domain I haven't even bothered to try and

find a script to fix.

[gshaw]

You might need to watch out on your KMS server as sysprep resets the client machine ID (CMID) that it uses to check how many unique machines have checked in against the server. If they're all the same they'll never activate. Would always sysprep an image before deploying it, standard MS practice really.

[sted]

For what it's worth I'm always seeing "the trust relationship between this workstation and the primary domain failed"

happens on average on 1 pc per 100 pcs every month (rough estimate )

All machines are done via sysprep

I'm getting so quick at running the network ID wizard to join it back to domain I haven't even bothered to try and

find a script to fix.

run

if exist c:\nsr.txt goto end
bcdedit /set {default} bootstatuspolicy ignoreallfailures
copy "\\server\NETLOGON\distribute\disablestartuprepair.bat" "c:\nsr.txt" /y
:end

as a startup script on your pcs and odds on it wont happen anymore

[RichB]

standard MS practice really.

 

 

Thats why I dont use it and have no issues