@conitrade-as Yes, fixed. Thx! The issue on this VM was we were installing as non-admin. All others were admin by default. Good catch

But thank you for your time all the same.

@kratos no, it's not that rare. I even saw in the wild replication on the same storage (wouldn't recommend it , though ) the cross pool replication is a little harder since the objects are each split on their own xen api, so the calls must be routed to the right one We tested the harder part, not the mono xapi case

I'm getting back to you. I've enabled ‘Nested virtualisation’, and I've also run the following command in PowerShell within the VM: "dism.exe /online /enable-feature /featurename:Microsoft-Hyper-V-All /all /norestart dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart" in a PowerShell session within the VM, but it still isn’t working. Is this normal? Is Docker not working on Windows under XCP-NG?

@rzr Hi. Thank you very much. I will be setting up a new server within the next 2 weeks and will definitely test it. Then I will give you feedback! Thank you again for picking it up!

@Dezerd you just have to start-copy the Replica VM it permits the original job to keep replicating on the VM. there is no failover/failback mecanism AFAIK if you work on replica started VM, you will have to put up in place a replica going to original hosts

@Pilow We tried that as well, same problem Also tried with a VM on the same newtork, just another VLAN, and we're seeing the same thing. At first we figured it was because one of the xcp-ng's was on a remote site which is connected through an IPSEC VPN, but that wasn't the case.