R
rms143
I'm working on a Windows 7 32-bit image of a Dell Optiplex 990. I create a local admin account named thsystem, install all the needed drivers, make the necessary customizations (shortcuts, etc), and install all of the needed software (Adobe Flash/Reader, Quicktime, Citrix, .NET 4.0, etc). I then drop my unattend.xml in the sysprep folder, run sysprep /generalize /oobe /shutdown /unattend:unattend.xml, and then capture the image by booting off a USB drive with WinPE 3.1 and GImageX.
When the test PC that I built the image on reboots, it goes through the setup process, following the unattend.xml settings exactly. It's almost completely unattended except for the PC name (and the forced creation of an account that I delete our users log in via their domain accounts). It works fantastic. But when I install that captured image on another Optiplex 990, even the test 990 I'm using, it gets stuck at the "Windows is starting services" screen and simply will progress past that screen at all, even though the test machine, on first reboot, worked just fine.
What am I doing wrong? What's going on here? I'm dedicating my weekend to this project, because we need to have 30 990s deployed hopefully by this Friday. At this rate we simply won't meet our goal.
Continue reading...
When the test PC that I built the image on reboots, it goes through the setup process, following the unattend.xml settings exactly. It's almost completely unattended except for the PC name (and the forced creation of an account that I delete our users log in via their domain accounts). It works fantastic. But when I install that captured image on another Optiplex 990, even the test 990 I'm using, it gets stuck at the "Windows is starting services" screen and simply will progress past that screen at all, even though the test machine, on first reboot, worked just fine.
What am I doing wrong? What's going on here? I'm dedicating my weekend to this project, because we need to have 30 990s deployed hopefully by this Friday. At this rate we simply won't meet our goal.
Continue reading...
