Hyper-V Server

UPDATED April 2024

Most applications run perfectly when set up on a Fresh Start machine within DaDesktop (DD). A small number, however, don't behave as expected after cloning and need a few extra steps to work correctly.

System Details

Hyper-V Server 2019 and newer (older versions likely show the same behavior)
Deployed using a Windows 10 / Win 2019 Server template

Fresh Start Fix Notes

This is a general guide for resolving the issue inside Fresh Start. The exact steps may differ depending on your specific configuration.
Summary – Apply the following fix on the Fresh Start machine. Hyper‑V generates duplicate MAC addresses on the External switch when cloned from a Fresh Start machine. To avoid this, either select the second pre‑configured Intel network connection or remove the External switch before cloning (detailed below).

Fix Process

1. Open Hyper‑V Manager, as shown. Right‑click and choose Virtual Switch Manager.

Hyper-V Manager

2. In the Virtual Switch Manager window, select the 'External' switch, then choose the Intel Pro/1000 network connection. Note: This option is only available with Windows 10 templates version 71 and higher. Click OK and save the configuration if prompted, then close Hyper‑V Manager.

Hyper-V Virtual Switch Manager

3. Continue with any remaining Fresh Start machine configuration. When finished, shut down the machine from inside the VM and wait until it is fully stopped. Then clone the Fresh Start machine to the Trainer and Participants’ machines as needed.

After this change, Hyper‑V will work properly on both Trainer and Participant machines. Without it, participants may see each other’s machines instead of their own because cloning the external network card creates duplicate MAC addresses on the External switch when the Fresh Start machine is cloned.

If you still run into problems, reach out to DaDesktop Support via the chat app – we’re happy to help.