Server 2012 R2 Hyper-V and Sysprepping a VM
Posted on 2016-09-13
I have a Hyper-V host setup and am trying to setup a VDI for DELL WYSE clients. This is my first attempt at such a setup.
I am trying to create a set of pooled desktops. I created a VM, PXE booted to WDS, pulled down my current Win10 Enterprise image.
The first VM I created I pushed through MS Welcom setup, installed Google Earth, tested Google Earth with Remote FX. Removed all modern apps, and kicked off sysprep. Sysprep runs for a while visually (maybe 3-5 min) then seems to freeze, yet Hyper-V manager still shows minimal CPU usage 5%-6%. I let this run for 10-12 hours, and then forefully turned off the machine. Upon reboot, the computer was not sysprepped and took me to a normal login screen.
On my second attempt, I created the VM, PXE booted, pulled down the same image, except this time I went into audit mode, installed Google Earth, ran sysprep with option to shutdown the machine. So far I have the same results.
I read the heartbeat may be confusing the Hyper-V host, so I disabled Heartbeat on the guest VM integration services.
Any insight on sysprepping Win 10 Enterprise VM on Hyper-V 2012 R2 Host? Experience similar issues?
At a loss at the moment, wondering if I need to rebuild my Hyper-V host.