Vista Sysprep/imagex pain and suffering
Hi all.
I’ve been trying to create a deployable Vista image for our corporate environment, and I’m finding it quite painful to do the Microsoft-approved method of sysprep/imagex.
Here’s the procedure I’m following:
Start up new Dell notebook - latest company model is the Latitude E6500
Join the domain, log in as test user, install corporate apps, and tweak settings.
Create an unattend.xml using Windows AIK 1.1 and system image manager.
In this xml I have it join the domain, copy my test user profile to the default user, enable local admin, hide EULA and a few other common settings.
Also I specifically tell it <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
I copy the unattend.xml to c:\windows\sysprep then run
Sysprep /generalize /oobe /shutdown /unattend:unattend.xml
Then I boot PE2 do a net use g: to a network share and run imagex /capture /compress fast /check c: g:\E6500.wim “E6500 corporate imageâ€Â
This takes a long time, but I can live with it, even though I really miss the speed of using Ghost.
Next, I unbox another E6500 same hardware config, boot PE2, format c: , net use g: to my share and run imagex /apply g:\E6500.wim 1 c:
This runs for a while (much faster than the capture thankfully)
Once done, I reboot.
Vista does the OOBE thing (annoyingly slow) and once it’s done, I log in.
Looking around I see that almost everything is there, and most of my unattend settings worked BUT, it’s deleted the video card and NIC drivers, even though I thought that the PersistAllDeviceInstalls would prevent this.
One workaround is to add the driver path to the offline servicing pass. This gets the drivers re-installed but adds to the already too long OOBE process.
Is there any way I can prevent the drivers from being deleted by sysprep?
I know that the Vista .wim install makes life easier for different hardware platforms, but I’m fine with having 2 or 3 images for our different models.
And are there any other things I can do to speed up any of this?
Thanks,
Steve
I’ve been trying to create a deployable Vista image for our corporate environment, and I’m finding it quite painful to do the Microsoft-approved method of sysprep/imagex.
Here’s the procedure I’m following:
Start up new Dell notebook - latest company model is the Latitude E6500
Join the domain, log in as test user, install corporate apps, and tweak settings.
Create an unattend.xml using Windows AIK 1.1 and system image manager.
In this xml I have it join the domain, copy my test user profile to the default user, enable local admin, hide EULA and a few other common settings.
Also I specifically tell it <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
I copy the unattend.xml to c:\windows\sysprep then run
Sysprep /generalize /oobe /shutdown /unattend:unattend.xml
Then I boot PE2 do a net use g: to a network share and run imagex /capture /compress fast /check c: g:\E6500.wim “E6500 corporate imageâ€Â
This takes a long time, but I can live with it, even though I really miss the speed of using Ghost.
Next, I unbox another E6500 same hardware config, boot PE2, format c: , net use g: to my share and run imagex /apply g:\E6500.wim 1 c:
This runs for a while (much faster than the capture thankfully)
Once done, I reboot.
Vista does the OOBE thing (annoyingly slow) and once it’s done, I log in.
Looking around I see that almost everything is there, and most of my unattend settings worked BUT, it’s deleted the video card and NIC drivers, even though I thought that the PersistAllDeviceInstalls would prevent this.
One workaround is to add the driver path to the offline servicing pass. This gets the drivers re-installed but adds to the already too long OOBE process.
Is there any way I can prevent the drivers from being deleted by sysprep?
I know that the Vista .wim install makes life easier for different hardware platforms, but I’m fine with having 2 or 3 images for our different models.
And are there any other things I can do to speed up any of this?
Thanks,
Steve
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
smason
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.