-
@Chemikant784 Yes, it does not replicate the version reporting from Citrix, but rather to be consistent across guest OSes. What would you like to see reported here?
-
@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.
-
@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. -
I'll change it to report something like "Windows 11 Professional 64-bit" instead. Any other guest information you'd like to see reported here?
-
@dinhngtu Better to report it Windows11/Windows Server 202x
-
@dinhngtu I would prefer some standardized OS information for Windows systems, similar to this info:
Get-ComputerInfo | Select-Object OsName, OsVersion, OsBuildNumber, OsArchitecture OsName OsVersion OsBuildNumber OsArchitecture ------ --------- ------------- -------------- Microsoft Windows Server 2025 Standard Evaluation 10.0.26100 26100 64-bit -
@dinhngtu Is it impossible to report the correct Windows version? Seems to be the "correct" solution....
-
Sorry for the confusion, I was posting the output from my Windows 11 computer...
On Server 2022 for example, it will report "Windows Server 2022 Datacenter 64-bit" instead. So the OS name should be correct wrt. client/server editions, i.e. it will not report as Windows 11 on Server 2025.
-
@dinhngtu From my point of view this would be fine
So the systems can be distinguished even when the buildnumber is the same. -
Got a weird bug on these.
Used xenclean to remove Citrix 9.4.1 drivers, installed the 9.0.9137-2 . Now if I live migrate a VDI, the agent gives up on that VM. Drivers are all working, just the agent needs reinstalling. Only got one pool to test it on, but its the same on all four hosts.
Three VMS I migrated disks on;
From Management Agent Detected before VDI migrated to agent missing after migration completion;
All three are Server 2019 VMs.
Any similar known issues?
-
@spelon Yes, it's known. I'll try to fix that in the next release.
-
@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.
-
@manilx It's purely cosmetic and will clear on reboot.
-
