I did it that way so as to get the old Citrix driver first, and then let it update and watch it reboot. That was my logic anyway.
@dinhngtu said in Migrating from XCP-ng Windows guest tools to Citrix:
@bberndt Okay, I managed to reproduce your situation. I think it's because the "driver via Windows Update" option was enabled after installing the XS drivers, which caused the drivers to lock onto the non-C000 device and prevent updates from coming in.
Normally, XenClean should be able to fix the situation. But if you want to fix things manually, or if things still don't work (C000 is still not active), here's a procedure that should fix the problem:
Take a snapshot/backup/etc.
Keep a note of static IP addresses (if you have any; there's a chance those will be lost). You can also use our script here: https://github.com/xcp-ng/win-pv-drivers/blob/xcp-ng-9.1/XenDriverUtils/Copy-XenVifSettings.ps1
Reboot in safe mode and disable the non-C000 device.
Reboot back to normal mode; it'll ask you to reboot a few more times.
The C000 device should now be active and you should be able to get driver updates again.
(Optional) You can now enable and manually update the non-C000 device (Browse my computer - Let me pick).