Alright I finally got it to work.

I think the trick was to put "Ethernet 2" in quotations. I also perfected the YAML spacing and bracketed the two nameserver addresses.

Thanks for the help gentlemen. Final working network config:

#network:
  version: 2
  ethernets:
    "Ethernet 2":
      dhcp4: false
      addresses:
        - 192.168.1.30/24
      gateway4: 192.168.1.1
      nameservers:
        addresses: [192.168.1.5, 8.8.8.8]

I had the same problem, I had to run the XenClean script and do a fresh install of 9.4.1 which resolved the issue.

https://github.com/xcp-ng/win-pv-drivers/releases

@Cyrille said in Automating VM configurations after mass VMware imports:

Hi,
If you're familiar with Golang, I'm pretty sure the xenorchestra-go-sdk might be able to do what you want (except the network configuration within Windows, but for this you can use Ansible with Xen Orchestra Inventory plugin: read the blogpost.)

The Powershell module is quite new, and we are working on improving it. Please let us know what you are expecting from it

Configuration of pool, host, and VM settings would be the primary things I'm used to accomplishing with PowerShell in VMware.

@dinhngtu said in "Management agent not detected" and "No Xen tools detected":

@MK.ultra Do you have the "Manage Citrix PV drivers via Windows Update" option enabled on these VMs? If so they'll need to be updated via Windows Update. If not, try XenClean to remove all the existing drivers and install clean 9.4.1 ones.

Using XenClean and then reinstalling 9.4.1 directly cleaned up the vulnerability alerts. The VM's had been upgraded from 9.4 to 9.4.1
Thanks!