XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    XCP-ng Windows PV tools announcements

    Scheduled Pinned Locked Moved News
    22 Posts 6 Posters 1.2k Views 8 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      abudef @dinhngtu
      last edited by abudef

      @dinhngtu said in XCP-ng Windows PV tools announcements:

      @abudef Got it, the agent was not changed since the last version so the build number was not bumped. I'll keep that in mind for the next release.

      👌
      e9ef55bc-1a55-4dd6-9576-d20e105472e3-image.png

      1 Reply Last reply Reply Quote 2
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Thanks @abudef !

        1 Reply Last reply Reply Quote 0
        • A Online
          acebmxer
          last edited by

          Installed tools on a two windows 11 and windows server 2022. No issues detected so far. One vm did have drivers managed by windows update enabled others did not. Ran Xenclean on all system and then installed the new drivers/tools? 👍 👍 👍

          Will these tools be included next xcp-ng release or update like the Linux drivers/tools are?

          1 Reply Last reply Reply Quote 0
          • M Offline
            manilx @olivierlambert
            last edited by

            @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 😊

            1 Reply Last reply Reply Quote 0
            • C Offline
              Chemikant784
              last edited by

              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.

              37736f8f-199d-48a9-a6da-18ae49cb667c-grafik.png

              D 1 Reply Last reply Reply Quote 1
              • D Offline
                dinhngtu Vates 🪐 XCP-ng Team @Chemikant784
                last edited by

                @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?

                M C 2 Replies Last reply Reply Quote 0
                • M Offline
                  manilx @dinhngtu
                  last edited by

                  @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.

                  1 Reply Last reply Reply Quote 1
                  • C Offline
                    Chemikant784 @dinhngtu
                    last edited by Chemikant784

                    @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.

                    1 Reply Last reply Reply Quote 1
                    • D Offline
                      dinhngtu Vates 🪐 XCP-ng Team
                      last edited by

                      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?

                      M A 3 Replies Last reply Reply Quote 0
                      • M Offline
                        manilx @dinhngtu
                        last edited by

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

                        1 Reply Last reply Reply Quote 0
                        • A Offline
                          abudef @dinhngtu
                          last edited by

                          @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
                          
                          1 Reply Last reply Reply Quote 0
                          • M Offline
                            manilx @dinhngtu
                            last edited by

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

                            D 1 Reply Last reply Reply Quote 0
                            • D Offline
                              dinhngtu Vates 🪐 XCP-ng Team @manilx
                              last edited by dinhngtu

                              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.

                              C 1 Reply Last reply Reply Quote 1
                              • C Offline
                                Chemikant784 @dinhngtu
                                last edited by

                                @dinhngtu From my point of view this would be fine 🙂 So the systems can be distinguished even when the buildnumber is the same.

                                1 Reply Last reply Reply Quote 0
                                • First post
                                  Last post