@planedrop Ah... well, that solves that. We've got secure boot required per compliance.

@planedrop Thank you, this is exactly what I'm looking for.

Are the citrix tools available somewhere, or is it only behind a subscription? We're open to subscriptions if needed.

@Darkbeldin

Thank you for that clarification.

Am I correct in assuming the Windows Agent for the Citrix Tools is also not available as open source?

Is there an official recommendation on which one performs better/less issues/etc, or is this up to each induvial user?

What is the current recommended best practice for modern Window's OS and the XCP/Xen tools?

I've tried by checking the Windows Update option and pulling down the Xen versions, which works fine for the drivers, but my XCP-NG instances never pick up the agent. This leads to bad commmunication via the reboot button, no RAM reporting, and no little windows logo for OS identification in the gui.

I then spun up a brand new vm and installed the XCP-NG drivers/agent as found in git. However, development on those appears to have stalled out in 2019, so I'm concerned about security, reliability, and moving forward.

Any suggestions?

@olivierlambert

I blew away the docker container and did a fresh build of XO from source on a *buntu box. Issue resolved itself with that. Must be a bad build in the docker.

Fresh install of XO, spun up a testing Windows VM, used the Windows Update tools/drivers. Sees the drivers, agent is installed, reports an IP, all works well. Except XO can't see the ram usage. It just reports as 0.

I've tried this with two different installs now, same thing. Tried with Win 2016 and 2019, no difference.

This is the from source build of XO, running in docker from the image ronivay/xen-orchestra due to how quickly I could add it ot my existing pool.