@dinhngtu I was just wondering. I would expect the Windows Name (as the property implies). At the moment "OS name" and "OS kernel" are filled with the same information. So in a quick view through the VM-tree one could not define its a server or a client OS. Sure, soon there will be another buildnumber for Windows 11 due to 25h2. But in this way IMHO it's a little bit more tricky to get an overview Overall its not a big thing.

It's great, thank you so far! I've noticed, that the reported OS in XenOrchestra (and XCP-ng Center) is reported differently compared to Citrix Tools. Is this intentional? For example, this is a Windows Server 2025 and not a Windows 11 24h2.

Due to the release of the Xentool 9.4.2, I once again tested whether the tools will start again without Delay. This was now the case with me. My XCP-NG test host now has 8.3 on it. That means: XCP-NG 8.3 with Xentools 9.4.2 and with Windows Server 2025 with AD role installed in this combination lead to me that the tools now can start correctly without the delay setting. But I cannot say whether the problem may have been fixed beforehand or whether XCP-NG 8.3 has an impact. I just wanted to let you know briefly because I didn't have it on my screen at the moment. So the initial reason of this thread seems fixed to me

My three test systems seems to work properly when the management agent start type is set to delayed. So i think this can be a workaround for the moment.