Hyper-V Server
UPDATED April 2024
When you spin up applications on a Fresh Start machine via DaDesktop (DD), the vast majority behave exactly as expected. A handful of apps, however, don't survive the cloning process gracefully and require a couple of additional tweaks to get them running properly.
System Details
- Hyper-V Server 2019 and later (older versions will probably show the same behavior)
- Deployed from a Windows 10 or Windows Server 2019 template
Fresh Start Fix Notes
-
This is a general guide for making this application work inside Fresh Start. Depending on your exact setup, the steps may vary slightly.
-
In a nutshell, the Fresh Start fix works like this: Hyper-V can encounter duplicate MAC address issues with the External switch after cloning from a FreshStart machine, so we pick the second pre-configured Intel network connection or remove the external switch from the FreshStart machine before cloning — the detailed steps follow below.)
Fix process
1. To begin, open Hyper-V Manager. Right-click and select Virtual Switch Manager from the menu.
2. In the Virtual Switch Manager window pictured below, pick the 'External' switch, then choose the Intel Pro/1000 network connection (this option only appears with Windows 10 templates version 71 or later). Click OK, save the configuration if prompted, and close Hyper-V Manager.
3. Proceed with the rest of your FreshStart machine setup as needed. When you're done, shut down the virtual machine from inside the VM itself — wait until it stops completely. Then clone the FreshStart machine to the Trainer and Participant machines as required.
After this adjustment, Hyper-V Server should work properly on both Trainer and Participant machines. Without it, participants may see each other's VMs instead of their own because cloning creates duplicate MAC addresses on the External switch from the FreshStart machine.
If you still run into trouble, reach out to DaDesktop Support through the chat app — we’re happy to help.