Vista SP1, Sysprep & UserLock...

[Gatt]

OK just created a Vista Image.. Sysprep'd it and captured the image to WDS

Then overnight I deployed it to 15 PC's

 

Problem 1

Forgot to create an unattended file... D'Oh!

 

Problem 2

Vista's sysprep strips out all drivers not included within Vista (in my case the Intel Q965/Q963 Express Graphics drivers..

 

Problem 3

Ok this one seriously screwed things up..

When I logged on as any user I was greeted with the users Documents] Folder which i closed.. only for it to appear again, then another, and another and anouther... until my screen ws fileld with them - it took 20 mins for task manager to appear which then told me i had about 700+ "Documents" Processes!!

 

Eventually I managed to get RegEdit open (about 30 mins!)

 

Drilled down a few and eventually came to HKLM\Software\Microsoft\Windows NT\CurrentVersion\WinLogon\ to find that the USERINIT was set to C:\Windows\System32\ULAgent.exe

 

Checked this out and its the UserLock Agent.. Now In XP the USERINIT variable is userinit.exe - set Vista to this and rebooted and all ok - till i sysprep'd again.. problems 2 and 3 came back!!

 

Argh!!

 

So, how do i get Sysprep to not remove the drivers?

And, short of ditching UserLock - how do i get Vista's userinit value to remain as userinit.exe after sysprep?

[PeterW]

Err off the top of my re the drivers are you using the generalize switch?

[Gatt]

yeah - shouldn't i be? (first time using Vista's Sysprep)

 

EDIT

 

Ok fixed the drier issue - injected the drivers via BDD when deploying the install image

What does "generalize" do?

If i dont include it will it strip out the PC name, etc

 

trying to find a workaround for the userinit bug - thinking a regedit patch on first boot up..

Edited March 7, 2008 by Gatt
update