Hyper-V Server
Last updated April 2024
Most applications function perfectly when set up on a Fresh Start machine within DaDesktop (DD). However, a handful of apps behave differently after cloning and require additional steps to run properly.
System Details
- Hyper-V Server 2019 and later (older editions likely exhibit the same behavior)
- Deployed with the Windows 10 / Windows Server 2019 template
Fresh Start Fix Notes
-
Keep in mind this is a general guide for fixing this app when using Fresh Start. Steps may vary depending on your specific setup.
-
Here's a summary – apply these steps on the Fresh Start machine as described. Hyper-V encounters duplicate MAC address issues with the External switch when cloned from the FreshStart machine; to resolve it, either select the second pre-configured Intel network connection or remove the external switch in the FreshStart machine before cloning (I'll detail this below).
Fix process
Start by opening Hyper-V Manager, then right-click and choose Virtual Switch Manager.
In the Virtual Switch Manager window, pick the 'External' switch, then choose the Intel Pro/1000 network adapter (this option appears only with newer Windows 10 templates, v71 and above). Click OK, save the config if prompted, and close Hyper-V Manager.
Proceed with the FreshStart machine setup as needed. Once everything is configured, shut down the VM from inside the guest operating system and wait for it to stop completely. Then clone the FreshStart machine to the Trainer and Participant machines as required.
After this fix, Hyper-V should work properly on both Trainer and Participant machines. Without it, the cloning process creates duplicate MAC addresses on the External switch when the FreshStart machine is cloned.
If issues persist, reach out to DaDesktop Support through the chat app – we're ready to assist.