[Beta Release] XCP-ng Windows Client tools 8.2.1-beta1
-
On a host running XCP-ng 7.6 I tested the tools on 2 VMs:
-
On new install of Server 2016: Ran XCP-ng tools' setup.exe as administrator which gave a "Windows Management Agent failed to install" error message. Then remembered I needed .net framework 3.5 and installed it then tried again. Installed successfully and was prompted to reboot. It appears to be working correctly. Both XO and XCP Center tell me the management agent is not installed on the VM (though I believe it is). You might consider adding a reminder about the .net 3.5 requirement in the setup.exe prompts.
-
On existing install of Server 2016 with .net 3.5 installed: Uninstalled Citrix guest tools then rebooted. Server came back up with full capabilities of guest tools and correctly recognized NIC. From what I can tell, Citrix's tools didn't actually uninstall. I then installed Citrix's guest-tool-leftovers uninstaller (xluninstallerfix.exe), ran it, and rebooted to a blue screen. Restored to snapshot. Attempted same process (xluninstallerfix.exe) then installed XCP-ng guest tools before reboot but still blue screen. Attempted to remove Citrix's guest tools in safe mode using the process described here: https://antisp.in/recovering-windows-server-2012-on-xen-server/ (author fails to mention you need to manually start the two services). Restarted several times but Citrix's tools are still active. Did the same thing with xluninstallfix.exe in safe mode and then attempted to install XCP tools while still in safe mode. XCP tools failed to install as it was unable to start a service (error 1603, related to task scheduler I believe). After several failed install attempts rebooted to another blue screen. I could have booted to safe mode again but I'd still be unable to install tools in safe mode so out of luck.
As far as I can tell it works great on new VMs but there seems to be no way to safely replace Citrix tools with XCP-ng tools at the moment.
-
-
@harrise I have the same experience.
-
@dbeato said in [Beta Release] XCP-ng Windows Client tools 8.2.1-beta1:
@harrise I have the same experience.
Actually mine said Management Agent installed, then I also needed to do Cause A( steps on the troubleshooting guide here
https://github.com/xcp-ng/xcp/wiki/Troubleshooting#windows-management-agent--windows-pv-tools -
See below my results
-
@dbeato glad that it works now... I actually don't know an automated way to find all the little things that can cause the drivers to fail. It's mostly detective work
-
@borzel said in [Beta Release] XCP-ng Windows Client tools 8.2.1-beta1:
@dbeato glad that it works now... I actually don't know an automated way to find all the little things that can cause the drivers to fail. It's mostly detective work
Yeah, that is why I am reporting here
One thing I would say though, it doesn't seem to do the paste from the host as XenServer used to. Not sure if it is supposed to be that way. -
@dbeato hmm.. never saw this feature ... I'll try with some test VMs
-
@dbeato it just works!
-
@borzel said in [Beta Release] XCP-ng Windows Client tools 8.2.1-beta1:
@dbeato it just works!
Good, that's what I need to review again as this morning did not want to work.
-
I've installed this on Win server 2019, PV Drivers install, but XCP-ng center reports the management agent is not installed AND under the performance it says to install XCP-ng tools to view memory data.
-
@conradical Did you reboot? Do you see the XCP-ng devices in Device Manager?
-
@borzel
Yes, I did reboot. I don't see XCP-ng, but see
XenServer PV Netowrk Device
XenSRC PV scsi disk device
and XenServer PV Bus'sHow that I look closer i see Xenserver Agent and XenServer PV Driver monitor. -- I'm wondering if these grabbed from windows update automatically post XCP-ng tools install.
-
Screenshots..
-
so I did a fresh 2019 install, using the server 2016 template since 2019 template isn't available yet, post install i was prompted with this screenshot:
This is also the recently re-released Win Server 2019 disk.
-
Apparently be default the template has "Windows Update tools" enabled. Should this not pull the drivers for XCP-ng?
-
@conradical we don't have xcp-ng drivers on Windows Update. Maybe later....
-
@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 -
@conradical device id's are "registered" in the xen project and in "the pci database"
... but they are for future use -
@borzel
Got it! Good work by the way! -
