New
#60
Kari - Finally got sysprep to work, but running into a couple of problems. Here's what I did to make it work - first, I took out the AutoLogon of the unattend.xml file. Burned a PC back to its original image (just the Windows 7 Pro OS with an Administrator account) and ran Sysprep with "Audit Mode", Generalize un-checked, and "Quit".
When it was done, I ran my Powershell Build which added the accounts, apps, printers, all that we need. When it was done, I ran Sysprep with "OOBE", Generalize checked, and "Shutdown". Booted that image up with an ISO key to save it via Clonezilla to a server. When it was done, I booted it back up and it went through all the "Sysprep is starting services..." et al. It then finally came up to the Windows Set-up page. I hit Ctrl+Shift+F3 so it would let me login as Administrator - which worked, except it tried to auto-logon Administrator and failed. Was able to login properly after that. When I logged in the Sysprep GUI was there, which I expected. Hit Cancel on that, then changed the computer name (Sysprep seems to give it some long name with "WIN-" followed by letters/numbers?) back to our needed computer name, which requires a reboot. Did the reboot and goes all the way back through the "Sysprep is starting services..." screens again, which I did not expect. It again tried to Autologin "Administrator", but is either sending the password blank or putting in the wrong password. I press Enter and login again as Administrator. And again the Sysprep GUI is there.
Logged off and it gave me "Administrator" and "Other User" rather than "Administrator" and our two other accounts names, which I'll call "User1" and "User2". I logged in as "User1" under "Other User" and it went through our Setup scripts to create the desktop for the user and configure the system to work for our needs, but when it was done - there was the Sysprep GUI again on the Desktop! And every time I reboot it, it goes through "Sysprep is starting services" as if it's booting up again for the first time.
So my issues are -
- It tries to Autologin the "Administrator" account.
- Acts like it's booting up for the first time during every reboot.
- The Sysprep GUI is on the Desktop every time you try to login to any account.
Aggravating to come this close, but not figure out how to correct these three things. I did burn the image I'd saved onto another computer and was able to activate both with OEM (slmgr.vbs) and it gives them separate Activation IDs and CMIDs, but I noticed that with Group Policy the SIDs were identical on each PC. I thought Sysprep is supposed to remove that information as well, so that when I run Group Policy on each PC, new SIDs are given?
Thank you.