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

[conradical]

@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

[borzel]

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

[conradical]

@borzel
Got it! Good work by the way!

[borzel]

@conradical

[borzel]

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

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!)

[RKO1337]

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.

I ran

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

this installed the XCP-ng Interface Package.

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

Services after reboot:

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.

Xen Orchestra displays that Xen Tools are not detected, but i can see Memory Usage etc.
XCP-ng Center:

[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)

[RKO1337]

@borzel thanks now all devices correctly recognized

[vmpr]

@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

[olivierlambert]

@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

[vmpr]

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

[olivierlambert]

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

[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 !

[ruskofd]

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

[ruskofd]

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

[ruskofd]

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.

[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).

[olivierlambert]

US language?

[ruskofd]

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

[ruskofd]

And it worked perfectly fine with the XS 8.0 drivers.