Sysprep 2 0 error updating registry
An update to WSUS 3.0 SP2 on Windows Server 2008 R2 and Windows Server 2008 (both x64 and x86) seems to break Windows Server Update Services (WSUS) and/or Internet Information Services (IIS) making clients unable to update via WSUS showing error 0x80072EE2.To me, the subversive update number is not clear yet.If you want to create a reference OS image, you have to run the sysprep Windows tool to prepare the image for OS deployment.If the tool fails with the error message “Sysprep was not able to validate your Windows installation” on a Windows 10 computer, you most likely have a problem with Windows apps.This shows that IIS and its pipings are broken and client computers cannot communicate with the server.Another symptom and a confirmation of the broken IIS hypothesis is a selection of the following warning and error events listed for Windows Server Update Services: service prior to manipulation.So, if you know for sure the exact update that does this, please comment.
I tried to sysprep a Windows 10 installation that was not activated, and sysprep ran through without complaints.
With the build SFC command it will stop doing that.
If you need to disable System Update scheduled updates on a single machine, you can easily do this manually.
The v Sphere Web Client is packaged with the v Center Server.
You can install the v Sphere Client from the VMware v Center autorun menu that is part of the modules ISO file.