I'm attempting to create an image for a client using audit mode on Windows 7 Professional. I booted the system and was given the typical OOBE welcome screen. I did the CTRL-Shift-F3 key combination to boot to audit mode. The system booted into audit mode briefly, then restarted. This is pretty typical, so I didn't think much of it. It rebooted into audit mode again. However, before I could make any changes, SysPrep reseal ran and rebooted the system back into OOBE. For some reason, it seems reseal is running on startup. I've attempted to kill the process quickly before it can reseal the system, but it happens too fast. Has anyone encountered this problem? Is there a solution? Thank you for reading – any help would be greatly appreciated.
Windows – HP EliteBook 800 Series immediately exits audit mode
bootsysprepwindows 7
Related Solutions
I think that the problem is that you are choosing Enter System Audit Mode... System audit mode is a special environment that is designed for installing programs and changing settings before an end user receives the system.
Also, by choosing the Generalize option, you are wiping the hardware settings which causes/forces Windows in to scanning for new hardware at each boot.
You only need to choose generalise when you are changing the hardware you are going to be using Windows on.
Lastly, Also, to get out of the audit mode, choose Enter system Out-Of-Box Experience (OOBE). Every time you choose it, the next time you start Windows, you will get the wizard, but it should be quite quick.
So - simply choose Enter system Out-Of-Box Experience (OOBE), and tick Generalize but only when you need to change computers!
It's been a while since I've done this, but from memory the order is:
- Set it up as you want (in Audit mode).
- Generalize it and shut down (still in Audit mode).
- Image/clone it onto new systems' drives.
- Boot each machine, and then finalize each new machine into the OOBE mode.
You can probably get away with imaging it after OOBE if this image is only going to be used on an identical set of computers. You don't want to generalize an OOBE (I don't think you can anyway).
We generalize before duplication because it stops the activation clock and allows up to use the same image on different computers for more than a month (as well as setting it to perform hardware detection on the next boot).
- We setup the base Windows image and generalize it (activation rearm #1 of 3).
- When we get an order for multiple machines that are identical, we use that image on one machine and then set it up the way they all should be (drivers, software, etc.).
- We then generalize it again (rearm #2), and then dupe it for the other machines.
- We then boot each machine, check them over, and then seal it with OOBE (rearm #3).
- It gets boxed and sent to the customer (after 72 hours of burn-in).
You don't want to boot again after OOBE, and you want to avoid sending a customer a new machine with a running activation clock.
PS: We use a duplication machine to dupe our drives; if you're doing a lot of machines, one of these will save you days of time over a year. :)
Best Answer
You can only Sysprep an image 3 times.
HP would have used 2 or 3 of those making the original image put on the notebook, and then to put it into OOBE mode before delivering.
So if you're trying to make an image from the original OEM image that came installed on the notebook, then you may be out of re-arms.
More info from MS' Sysprep, SkipRearm, and Image Build Best Practices:
Additionally, maybe check out this related MS KB article: An error message occurs when you run "Sysprep /generalize" in Windows Vista or Windows 7: "A fatal error occurred while trying to Sysprep the machine"