![]() This then left me with plenty of ghost devices to deal with. ![]() To resolve, I had to reinstall the latest management agent, and then uninstall. I came across some odd behaviours where even when removing the agent from add/remove programs, the driver sets would stay in play (confirmed under device management). I needed to remove these on the source VM to start with which is a commonly known requirement in the XenServer world. Uninstall XenServer Tools/Management Agent The VM’s in question are Windows Server 2016 Step 1. Below is what (after many attempts and head meets wall moments) I found to be the best way of consistently moving the workload from XenServer 7.6 to Hyper-V 2016. The tools are limited, and whilst there are some freebie options around to help, it’s the process rather than the tooling that is the challenge. Not the simplest of all tasks and disturbingly complex compared to the simplicity of moving VM’s in and out of vSphere. I recently had the unenviable task of moving a few XenServer based Virtual machines across to Hyper-V.
0 Comments
Leave a Reply. |