Server 2012 R2 Hyper-V and Sysprepping a VM
Hello,
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.
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.
Cliff Galiher
Did you remove modern apps on both attempts? Improperly removing a modern app will confuse sysprep in a big way.
ASKER
yes I removed modern apps using
Get-AppxPackage -AllUsers | Remove-AppxPackage
I then verified the apps were gone using Get-AppxPackage -AllUsers
My latest sysprep attempt actually failed with an error message: Driver_power_state_failure
upon reboot the system is saying 'Windows could not complete the installation. To install Windows on this computer, restart the installation.'
Get-AppxPackage -AllUsers | Remove-AppxPackage
I then verified the apps were gone using Get-AppxPackage -AllUsers
My latest sysprep attempt actually failed with an error message: Driver_power_state_failure
upon reboot the system is saying 'Windows could not complete the installation. To install Windows on this computer, restart the installation.'
Try it without removing modern apps. Helps isolate issues.
IIRC, Win10 requires Server 2016 for a proper deployment?
Excellent VDI Step-by-Step.
I have an EE article that may be of help for Hyper-V: Some Hyper-V Hardware and Software Best Practices.
Excellent VDI Step-by-Step.
I have an EE article that may be of help for Hyper-V: Some Hyper-V Hardware and Software Best Practices.
ASKER
Ok will do.
So PXE boot and pull image again.
Run through standard welcome setup, install google earth.
sysprep
or should I pull image, and go into audit mode to make google earth install?
So PXE boot and pull image again.
Run through standard welcome setup, install google earth.
sysprep
or should I pull image, and go into audit mode to make google earth install?
In the very rare instances i embed an application into an inage (which i dont usually recommend), I always install programs in audit mode. That ls personal preference from experience for sure.
ASKER
@Philip Elder...
I researched you comment about Win10 requiring Server 2016... I didn't find any definitive, but I also didn't find anyone detailing a Server 2012 & Win 10 VDI setup either, which leads me to think this may be the case, and the crux of my issue...
I researched you comment about Win10 requiring Server 2016... I didn't find any definitive, but I also didn't find anyone detailing a Server 2012 & Win 10 VDI setup either, which leads me to think this may be the case, and the crux of my issue...
It is not the case at all. MDT 2013 and SCCM both officially support windows 10 using WDS, and 2016 is not yet out. They could not support win10 if that were a requirement.
ASKER
@Cliff Galiher
OK, gotcha. I will proceed with the re-image and test as you stated yesterday, I will let you know shortly my results...
OK, gotcha. I will proceed with the re-image and test as you stated yesterday, I will let you know shortly my results...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
found answer on another site