Hyper-V Server

UPDATED April 2024

Most applications run without any issues on a Fresh Start machine with DaDesktop (DD). However, a handful of apps don’t behave correctly after cloning and need a little extra attention to get them back to normal.

System Information

 

Fresh Start Fix Notes
  1. Bear in mind, this is a general guide for getting this application to work inside Fresh Start. Depending on your specific configuration, the steps might vary slightly.

  2. Here’s a quick summary: Hyper-V runs into trouble with duplicate MAC addresses on the External switch when you clone from the FreshStart machine. So the fix is to either pick the second pre-configured Intel network connection or remove the external switch from the FreshStart machine before cloning—I’ll walk you through the details below).

     

How to Fix It

1. You’ll see the Hyper-V Manager below. Right-click to bring up the Virtual Switch Manager.

Hyper-V Manager

 

2. In the Virtual Switch Manager (shown next), pick the 'External' switch and then choose the Intel Pro/1000 network connection. Note that this option is only present with newer Windows 10 templates (v71 and above). Click OK, save your configuration if prompted, then close Hyper-V Manager.

Hyper-V Virtual Switch Manager

3. Finish any remaining configuration on the FreshStart machine. When you’re done, shut down the VM from inside it and wait until the machine comes to a complete stop. After that, clone the FreshStart machine to the Trainer and Participant machines as needed.

Once you’ve done this, Hyper-V should work fine on both the Trainer and Participant machines. If you skip the fix, participants might end up seeing everyone else’s VMs instead of their own because the external network card gets cloned and causes duplicate MAC addresses with the External switch when cloned from the FreshStart machine.

If you’re still running into trouble, just reach out to DaDesktop Support through the chat app and we’ll be glad to assist.