Clone a XenMobile node over Hyper - V 2016

Instructions

1. Turn off both nodes In Hyper-V Manager
2. Select the virtual machine that you want to clone (can be in running or off state).
3. Right click on the virtual machine, and select Export.
4. Specify the location where you want to save the exported VM.
5. You can click on Browse button to select a folder. Export Virtual Machine Hit Export when done.
6. The selected virtual machine will be saved in the location you specified.
7. In Hyper-V Manager, select Import Virtual Machine in the Actions pane. Click Next button.
8. Import Virtual Machine Select the folder which the source virtual machine is exported to, then hit Next button.
9. Import Virtual Machine in Hyper-V Select virtual machine to import, then hit Next button.
10. Import Virtual Machine in Hyper-V Select the radio button of Copy the virtual machine (create a new unique ID) and hit Next button.
11. Import Virtual Machine in Hyper-V Specify a folder location to store the virtual machines configuration files. You can leave it as default as Hyper-V will create a unique ID for the cloned VM. Hit Next button.
12. Import Virtual Machine in Hyper-V Specify a folder location to store the virtual hard disks for the cloned virtual machine. You must specify a folder location which is different from virtual hard disks of source virtual machine if you’re cloning the VM on the same host, otherwise you will encounter Hyper-V error while copying virtual hard disks to destination folder due to files already existed. Click on Next button when done.
13. Import Virtual Machine in Hyper-V Click on Finish button on the summary page to start the import. Import Virtual Machine to Clone in Hyper-V Once import operation completed, a clone virtual machine that is identical to the original virtual machine is created and listed in Hyper-V Manager.
14. Now change the name on the hyper-v manager by right clicking the VM.
15. Then log in to the new XenMobile node, and change the ip address to the non-working node.
16. Restart the server.
17. Then bring all nodes up again.