Answering myself:

@dinhngtu downloaded on a windows server 2022, extracted and did the inf install. No visual feedback.
How do I know it was installed?

@Greg_E You've got a point, actually several.

The scripts exist for a reason because the official way is way to complicated. I still use them, having converted to xcpng @home (scripts) and @business 3 yrs ago.

There should be an official script, definitely. So all are on the same page. They have nothing to loose, everything to gain! The more people use it the better and having a simple way to officially install XO would help that.

Regarding XO6, I don't personally like it at all, mainly because I have to hunt around to find stuff, where in XO5 it's already automatic (not talking about missing features which revert us to XO5).
I actually don't like the UI, it is cramped especially on smaller laptop screens... But this is a personal preference.....

@gduperrey updated 2 hosts @home. 5 @office.
Had to run yum clean metadata ; yum update on cli (cancelling to run RPU in XO) for updates to appear.

Also here the task progression can't be followed (stays at 0% until completed):

instead of

As shown above the evacuation tasks are not shown.
The last steps migrating thre VM's to the original place are shown:

Just did my RPU and checked on the new v6 interface.
The old one has task details that are missing on the new one (or I didn't find them:

I like to see the evacuation tasks happening (in the past I could identify hangs etc)

Here instead of the ID of the VM host the real names should be shown:

@McHenry This should not happen. If thr VM runs on the slave and the master is rebooted or shut down it still should continue to run. Done this many times. The only thing happening is that XO can't access the VM's any longer as it needs the master.

That being said: running the firewall/router on a VM opens you to a lot of future pain (as you just have experienced). Don't do that unless you absolutely must and can work around down-times caused by VM/host issues.

Install it on a dedicated machine!

@dinhngtu Updated from previous version running on 8 Windows Server 2022 VM's across HomeLab & Office.

No issues.

@acebmxer Fixed. Worked here now. Had the same error before

@stormi Downgraded all hosts @home and @office. I have not done anything to running Windows Server VM's or touch anything regarding certs. So I guess I'm all good.

@gduperrey Updated 2 pools/2 servers @home, updated 3 pools/5 servers @ office with RPU.
All fine.

@dinhngtu

@dinhngtu Hopefully before the next updates to xcpng. Rolling pool update moves all VM's....

Does this bug clear itself after a VM reboot? Or has the tools to be reinstalled? Is it only cosmetic or does it affect the running VM?

Havne't tried this myself and as we have moved all VM's to these new tools I'd like to be aware of what I can expect.

@dinhngtu Is it impossible to report the correct Windows version? Seems to be the "correct" solution....

@dinhngtu Better to report it Windows11/Windows Server 202x

@dinhngtu One would suppose for it to report the correct Windows version.... Or at least a common "general one", e.g. "Windows 10 or newer". As it is it doesn't feel right.

@olivierlambert Moved all my homelab and business vm's to this, from Citrix-tools (latest version).
Apart from loosing all IP info in the network (as it's always a new network adapter) all went without any issues.
All Vates now

@olivierlambert Working again, using both build scripts.

As always

@olivierlambert Created issue on both githubs.