@olivierlambert Sorry. I was working some other stuff, so I haven't had a chance to look. And I don't know if I will have time until next weekend. Thank you for checking up, though. I will post when I have an update on the situation.

@kevdog You can force a host to be ejected even if the host is not reachable any longer from the pool master using: xe host-forget uuid=UUID If there is any issue because VMs are thought to be running still on that host, you may need to do a power state reset on such before you can get rid of that host. See if that works for you.

@olivierlambert Thank you! I read the blog post you linked and it sounds perfect for me. It looks like it will come in handy as I work to get my VMs migrated off older versions of Citrix and XCP to modern, cohesive hosts.

@Danp Thank you. I hadn't noticed this configuration menu.

@olivierlambert Thanks for the clarification, it is definitely from sources. Apologies I will try to remember! I'll patch my system a little later today. Edit: Patched to Xen Orchestra, commit 6953e - All good. Thanks, really appreciate the prompt fix!

@olivierlambert Thanks I see that clarifies things. Took me a while to realize that this is to change the management xcp-ng connection to the network and not the VMs.

@olivierlambert Gotcha, that's what I thought. Thanks! So yeah @rauly94 either use XO Proxy or setup a VPN, those are the 2 best options for this.

Yes it will

@creoleMalady one more suggestion for the sake of an alternative solution. If you insist on managing multiple servers not in host (even though running them in a pool would equalize the CPU features to the oldest CPU available) you can use Cloudstack as a management platform to do the templates and networking for you. It dynamically transfers templates and assigns networks on demand on the hosts as you provision vms on them. The disadvantage is that you need to learn Cloudstack which can be much of an overhead by its own if you dont want to go too deep.

Before the end of the year