Hyper-V Server
UPDATED April 2024
Most applications run perfectly fine after being prepared on a Fresh Start machine with DaDesktop (DD). However, a couple of apps might encounter issues due to the cloning process, requiring a few additional steps to get going properly.
System Details
- Hyper-V Server 2019 and later (other versions likely exhibit the same behavior)
- Deployed from a Windows 10 / Windows Server 2019 template
Fresh Start Correction Steps
-
Keep in mind this is a general walkthrough for fixing the application inside Fresh Start. The exact steps may differ based on your specific configuration.
-
Summary – the fix on Fresh Start is as follows: Hyper-V has a problem with duplicate MAC addresses on the External switch when cloned from the Fresh Start machine, so we either select the second pre‑configured Intel network connection or remove the external switch in the Fresh Start machine before cloning (details below).
Fix Procedure
1. Start by opening the Hyper‑V Manager. Right‑click and choose Virtual Switch Manager from the menu.
2. In the Virtual Switch Manager dialog (see below), select the 'External' switch and then pick the Intel Pro/1000 network connection. Note this option is only available with newer Windows 10 templates, specifically v71 and above. Click OK, save the configuration if prompted, and close Hyper‑V Manager.
3. Continue with the Fresh Start machine setup as required. Once finished, shut down the machine from inside the VM and wait until it has completely stopped. Then clone the Fresh Start machine to the trainer and participant machines as needed.
After this adjustment, Hyper‑V Server should function properly on both trainer and participant machines. Without the change, participants may see each other’s systems instead of their own, because the cloning process creates duplicate MAC addresses on the External switch following cloning from the Fresh Start machine.
If you still run into problems, reach out to DaDesktop Support through the chat application—we’re here to assist.