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

    [Beta Release] XCP-ng Windows Client tools 8.2.1-beta1

    Scheduled Pinned Locked Moved Development
    53 Posts 11 Posters 26.5k Views 7 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.
    • borzelB Offline
      borzel XCP-ng Center Team @conradical
      last edited by

      @conradical we don't have xcp-ng drivers on Windows Update. Maybe later....

      C 1 Reply Last reply Reply Quote 0
      • C Offline
        conradical @borzel
        last edited by

        @borzel
        I thought I read where you were working on that process and got it done and were registering the device IDs. I guess i read wrong 🙂

        borzelB 1 Reply Last reply Reply Quote 0
        • borzelB Offline
          borzel XCP-ng Center Team @conradical
          last edited by borzel

          @conradical device id's are "registered" in the xen project and in "the pci database" ™ ... but they are for future use

          C 1 Reply Last reply Reply Quote 0
          • C Offline
            conradical @borzel
            last edited by

            @borzel
            Got it! Good work by the way!

            borzelB 1 Reply Last reply Reply Quote 0
            • borzelB Offline
              borzel XCP-ng Center Team @conradical
              last edited by

              @conradical 🏆

              1 Reply Last reply Reply Quote 0
              • borzelB Offline
                borzel XCP-ng Center Team
                last edited by borzel

                Status update: I'm currently working on avoiding these WMI errors. Here is my current progress:

                0_1543695450544_c08507e5-eba8-45e6-94e8-2ba601777c01-grafik.png

                https://github.com/xcp-ng/win-xenguestagent/commit/280847a38a0687a3c06608b51f9cc0cb9b4d9f9b

                0 borzel committed to xcp-ng/win-xenguestagent
                current progress to avoid WMI errors
                - tidy up most of the unnecessary untry()-catch() blocks
                - switched to .Net 4.7.1
                - fix IntPtr.Int32 errors (use IntPtr.Int64!)
                1 Reply Last reply Reply Quote 1
                • R Offline
                  RKO1337
                  last edited by

                  Thanks for the XCP-ng tools.

                  I tried to install the XCP-ng Tools on a new Windows Server 2019 vm (german locale), XCP-ng 7.5.
                  I used the Windows Server 2016 default Template.

                  Installed Net Framework 3.5 beforehand, launched the setup.exe as administrator.
                  The installation finishes with the management agenet could not be started message.

                  I restarted the vm, no new Xen Devices are shown in device management.
                  Only both of these services were installed.
                  892c2ea7-6c57-415c-abe2-b1785cd0142d-image.png

                  I ran

                  C:\Program Files\XCP-ng\XenTools\InstallAgent.exe DEFAULT
                  

                  this installed the XCP-ng Interface Package.

                  af6c61f8-f38e-48be-a422-47aced5a5dad-image.png

                  I got no popup that asked to reboot the vm, but restarted anyways.

                  Services after reboot:
                  d6a7e406-8686-423b-99b7-ed983b609971-image.png

                  Device manager shows two new unknown XENBUS devices. Under system devices XCP-ng Interface and XCP-ng PV Bus (0002) are now listed.
                  Network adapter, drives etc. are same as before the driver installation.
                  515e2f4b-99b8-417d-ae8e-2e241a869f76-image.png
                  e548cbee-1488-4a39-b881-04d1c1439629-image.png

                  Xen Orchestra displays that Xen Tools are not detected, but i can see Memory Usage etc.
                  XCP-ng Center:
                  e94af70e-5391-4e15-b0b4-802a8db2dd28-image.png

                  borzelB 1 Reply Last reply Reply Quote 0
                  • borzelB Offline
                    borzel XCP-ng Center Team @RKO1337
                    last edited by borzel

                    @RKO1337 you have to install the drivers then manually ... point the driver install dialog from windows to c:\programe files\xcp-ng\drivers (don't forget to tell him to search also in subfolders)

                    R V 2 Replies Last reply Reply Quote 1
                    • R Offline
                      RKO1337 @borzel
                      last edited by

                      @borzel thanks now all devices correctly recognized

                      1 Reply Last reply Reply Quote 0
                      • V Offline
                        vmpr @borzel
                        last edited by

                        @borzel thanks for the hint, now it works also fine for me, in xcp-ng center it says:

                        IO optimized
                        Management Agent installed

                        but in XenOrchestra it still says: "Xen tools version Not installed"

                        what should we do to get this fixed?

                        cheers, Ringo

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

                          @borzel is the XCP-ng Center guy, @julien-f or myself are more on the XO side.

                          1. Let's see if it's not a refresh issue, can you refresh your browser page and see if the result is still the same?
                          2. If it doesn't solve it, try to disconnect and reconnect your pool master in Settings/server, refresh and let us know
                          V 1 Reply Last reply Reply Quote 0
                          • V Offline
                            vmpr @olivierlambert
                            last edited by

                            @olivierlambert thanks for your reply, but after refresh and disconnect/connect its still the same 😞

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

                              Then feel free to open an issue here: http://github.com/vatesfr/xen-orchestra/issues/new

                              1 Reply Last reply Reply Quote 0
                              • ruskofdR Offline
                                ruskofd
                                last edited by ruskofd

                                I did a new test on my new fresh install of XCP-ng in my lab. So, to begin, the installation of PV Drivers + Management seems working on Windows Server 2019 with French locale with the version indicated in the title of the topic.

                                How I proceed ?

                                1. Launch the Setup.exe provided in the archive. The installation continue until "Management Agent failed to install"
                                2. I reboot my virtual machine
                                3. Launch the following command in the C:\Program Files\XCP-ng\XenTools folder with an Administrative prompt : InstallAgent.exe DEFAULT
                                4. Launch again the Setup.exe and select the Repair Menu. The Management Agent seems installed in the end of installation, he asks me to reboot to install the network driver. And I had to reboot again to install the storage driver.

                                And now everyone seems happy !

                                xoa.PNG

                                srvc.PNG

                                periphs1.PNG

                                periphs2.PNG

                                1 Reply Last reply Reply Quote 0
                                • ruskofdR Offline
                                  ruskofd
                                  last edited by

                                  I can provide additionnal tests, I will post my results after these during the following week ☺

                                  1 Reply Last reply Reply Quote 1
                                  • ruskofdR Offline
                                    ruskofd
                                    last edited by

                                    New test on Windows Server 2019 Core (French locale as well) : same procedure, same results 👌

                                    xoa.PNG

                                    mgmtagent.PNG

                                    taskmgr.PNG

                                    1 Reply Last reply Reply Quote 0
                                    • ruskofdR Offline
                                      ruskofd
                                      last edited by

                                      Here are my results on different versions of Windows Server (using Standard Edition). I used the same procedure indicated above.

                                      For each system, I update all the operating system to last version possible before installing PV drivers (thanks optic fiber 😂).

                                      • Windows Server 2012 R2 Core : successful install, VSS seems good (stable state and no error), soft shutdown and reboot OK.
                                      • Windows Server 2012 R2 Desktop Experience : successful install, VSS seems good (stable state and no error), soft shutdown and reboot OK.

                                      For both Windows Server 2012R2, they require more reboot, especially one more for the storage PV drivers after the installation of network PV drivers, but it works.

                                      • Windows Server 2016 Core : successful install, VSS seems good (stable state and no error), soft shutdown and reboot OK.
                                      • Windows Server 2016 Desktop Experience : successful install, VSS seems good (stable state and no error), soft shutdown and reboot OK.

                                      I don't know if it's very useful to test on Windows Server 2008/2008 R2 since the extended support will reach his end of life in the next January. But I can provide tests if required.

                                      1 Reply Last reply Reply Quote 1
                                      • ruskofdR Offline
                                        ruskofd
                                        last edited by ruskofd

                                        I tested to install a Windows 10 1903 client for doing some Remote Desktop, the Management is installed perfectly by doing the procedure above. But the disk and network drivers are not installed and they don't want to be installed. Usually you have a popup window on login to install these drivers, but in this case, it won't show.

                                        I guess it's a compatibility issue, I will try with XS 8.0 drivers (version 8.2.1).

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

                                          US language?

                                          1 Reply Last reply Reply Quote 0
                                          • ruskofdR Offline
                                            ruskofd
                                            last edited by

                                            French as usual, it worked with Windows Server (2012R2, 2016 and 2019)

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