System Preparation Tool - Use to Customize Windows

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.

Thanks again for the quick reply.

I get that about bypassing the Windows Welcome/Setup is used to put me back in Audit Mode, but I don't want that Windows Setup in the first place because I don't want it to create a named account (i.e. Eric-PC) in place of the Administrator account (which is the problem I ran into the first time I tried Sysprep).

I have this section near the very end of my unattend.xml:

<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
</OOBE>

Shouldn't that "SkipUserOOBE" eliminate my seeing the Windows Welcome?

I've installed Windows 7 Pro x64 to a virtual machine. Booted into audit mode from the OOBE welcome screen with ctrl+shift+F3 and installed service pack 1 and all windows updates. I then use the system preparation GUI to Boot to OOBE, generalize and shutdown. Reboot into generic WinPE for Windows 7 AIK and capture the drive image with imagex. All seems to go without a hitch and I'm able to restore the system from the created wim file but I cannot create an image catalog of the captured wim with System Image Manager in order to create an answer file for reinstallation. Is this normal for a captured image or am i doing something wrong. My technician and install machines are both x64 so shouldn't be a different architecture problem.

Here is a screen shot of the error


I'm attaching the WSIM log as well... tho not much info in it

Kari said:

Hi Diatomacious, welcome to the Seven Forums.

I am not sure I understand you correctly. Why would you need to create another answer file for further installs? The captured image when used on another machine will install Windows exactly as it was prepared by you, with your original answer file. When installation is finalized (OOBE) on your technician machine after you have captured the image you can find your original answer file (unattend.xml) in C:\Windows\Panther folder.

The subsequent installs do not need to be sysprepped.

Sorry for the misunderstanding... I should have noted that I did not originally use an answer file for installation. So if I'm to understand correctly I should just use an answer file created from the catalog off the installation disc for installation of the sysprepped image.

Hello Kari and thank YOU very much for taking the time and sharing your knowledge.

In the section 2.4. Create an Answer File
when it says:

"Browse to your Windows install media (DVD or USB), open the folder Source and select the file install.wim."

I only have an install.esd file...

Seeing the txt that came in the w7 i got i see:

* Windows 7 Ultimate SP1 X64 Multi-8 ESD April 2015

[ RELEASE INFO ]
* File: Win7.X64.MULTi8.Apr2015.iso
* Source: X17-59465
* Size: 3,55GB
* Format: Bootable ISO

[ CONTENTS ]

* Integrated / Pre-installed in Audit Mode:

* .NET Framework 4.5.2
* Internet Explorer 11
* Hotfixes - 2015-04-14

* Setupcomplete / Post-install:

* NDP45-KB3037581
* KB890930
* Defender Updates

* install.wim compressed to recovery format (install.esd)

My goal was to do your tutorial but with the most update version of w7 i found to avoid as much as possible to mess with updates before sysprepping but im really far cause im stuck at the begining of the creation of my answer file !

Thank YOU for YOUR Time !