Error sysprep windows 2008 r2

I did some research on that error, and it is caused by a piece of software not uninstalling cleanly and leaving some registry hooks that is tripping up sysprep. You have to use regedit to delete the entry to that particular piece of software in the cleanup folder, located here:. In that folder, track down the program that is giving you grief. To continue this discussion, please ask a new question.

Which of the following retains the information it's storing when the system power is turned off? Submit ». Get answers from your peers along with millions of IT pros who visit Spiceworks. Bear with me because I'm a complete n00b when it comes to running sysprep. But every time I run sysprep I get a fairly useless 'fatal error' message: "system preparation tool 3. Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group.

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 9 years, 6 months ago. Active 8 years, 7 months ago. Viewed 2k times. Sounds like a good candidate to be posted on ServerFault. Add a comment. Active Oldest Votes. Have you tried to use the UI? Just execute the sysprep. If you have to use the console, maybe try to run the console in evaluated modus. Daniel Manzke Daniel Manzke 2 2 silver badges 8 8 bronze badges.

Kent England Kent England 1. Sign up or log in Sign up using Google. Sign up using Facebook. This started out as an issue trying to deploy out VM's through VMWare vCenter - they previously were working flawlessly and then after I applied a few Windows updates they stopped working so flawlessly I eventually narrowed it down to sysprep, specifically when I tell it to unattend join the domain.

If I remove the Microsoft-Windows-UnattendedJoin section, it seems to work fine kind of defeats the purpose of an unattended join though Below are relevant log and sysprep. I don't know what else to check for : Any ideas?

Online installation cannot complete at this time. Still need to test a bit more, but so far I think I've found a resolution. In our VMWare cluster configuration, we had guest monitoring turned on - this enables a heartbeat between the guest VM tools and the host. If they didn't respond, it would reboot the guest. Since the VM was powered on but not running the vmware tools service during sysprep, it appears that the guest was not alive so it would reboot it.

If I run into this issue again, I'll reopen this question.. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group.