@hoh This is SOOO long in the tooth........... Always was annoying. Thx for findinf a fix, looking forward to it.

@stormi didn't see that (my old eyes)... guessed so anyway

@gduperrey reboot necessary?

@conitrade-as Yes, fixed. Thx!

The issue on this VM was we were installing as non-admin. All others were admin by default.

Good catch

@dinhngtu

@dinhngtu

@dinhngtu Noting there:

@dinhngtu We have one Win11 in production, which dodn't install the new tools, running the previous ones.

We always get:

We have rebooted before installing the tools: same issue
We have run Xenclean before installing: same
We have run Xenbootfix: same

Basically we'tried everything. I haven't opened an official ticket yet because the answer here might help others.

@dinhngtu Upgraded from previous tools (big jump from citrix was already done ) @home and @office a dozen Windows11 and Windows Server 2022.
No issues.

@dom0 As said numerous times by the developers: XCPNG Center is not supported. You have to use XO/XOA.

@ph7 This I can confirm, with XO VM.
But discussion was about the host....

@robertblissitt Press ESC and you'll see what's happening

@gduperrey Updated 2 pools/2 hosts @home (via cli). 3 pools/5 hosts @office (via RPU).
No issue.

Confirmed. Backups run successfully again.

@simonp NFS and S3

Updated XO to Master, commit a3139 and now the backups are failing.
Log sample:

  "tasks": [
    {
      "data": {
        "type": "VM",
        "id": "11393959-0b52-7c05-7b02-3fe6d645256d",
        "name_label": "XO"
      },
      "id": "1771281894926",
      "message": "backup VM",
      "start": 1771281894926,
      "status": "failure",
      "tasks": [
        {
          "id": "1771281894938:0",
          "message": "clean-vm",
          "start": 1771281894938,
          "status": "success",
          "end": 1771281895646,
          "result": {
            "merge": false
          }
        },
        {
          "id": "1771281897732:0",
          "message": "snapshot",
          "start": 1771281897732,
          "status": "success",
          "end": 1771281912046,
          "result": "6ab9cc35-95c2-0139-d996-7beafced8d6b"
        },
        {
          "data": {
            "id": "5f5c2608-bd80-4682-addc-dab062e9962c",
            "isFull": false,
            "type": "remote"
          },
          "id": "1771281912060",
          "message": "export",
          "start": 1771281912060,
          "status": "failure",
          "tasks": [
            {
              "id": "1771281916065",
              "message": "transfer",
              "start": 1771281916065,
              "status": "success",
              "end": 1771282018684,
              "result": {
                "size": 6650068992
              }
            },
            {
              "id": "1771282024895",
              "message": "clean-vm",
              "start": 1771282024895,
              "status": "failure",
              "tasks": [
                {
                  "id": "1771282027367",
                  "message": "merge",
                  "start": 1771282027367,
                  "status": "failure",
                  "end": 1771282031803,
                  "result": {
                    "code": "NOT_SUPPORTED",
                    "message": "Can't init vhd directory without using alias",
                    "name": "Error",
                    "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/_cleanVm.mjs:75:5)"
                  }
                }
              ],
              "end": 1771282031803,
              "result": {
                "code": "NOT_SUPPORTED",
                "message": "Can't init vhd directory without using alias",
                "name": "Error",
                "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/_cleanVm.mjs:75:5)"
              }
            }
          ],
          "end": 1771282031850
        }
      ],
      "infos": [
        {
          "message": "Transfer data using NBD"
        }
      ],
      "end": 1771282031856
    },
    {
      "data": {
        "type": "VM",
        "id": "fb7c36ab-2f26-b049-6fcd-2dfcabd37361",
        "name_label": "Windows 11"
      },
      "id": "1771281894928",
      "message": "backup VM",
      "start": 1771281894928,
      "status": "failure",
      "tasks": [
        {
          "id": "1771281894938",
          "message": "clean-vm",
          "start": 1771281894938,
          "status": "success",
          "end": 1771281895970,
          "result": {
            "merge": false
          }
        },
        {
          "id": "1771281897733",
          "message": "snapshot",
          "start": 1771281897733,
          "status": "success",
          "end": 1771281898773,
          "result": "3ce54f0c-8fa4-d71f-7693-8cf0c5c5a004"
        },
        {
          "data": {
            "id": "5f5c2608-bd80-4682-addc-dab062e9962c",
            "isFull": true,
            "type": "remote"
          },
          "id": "1771281898774",
          "message": "export",
          "start": 1771281898774,
          "status": "failure",
          "tasks": [
            {
              "id": "1771281900165",
              "message": "transfer",
              "start": 1771281900165,
              "status": "success",
              "end": 1771282339491,
              "result": {
                "size": 68675436544
              }
            },
            {
              "id": "1771282341068",
              "message": "clean-vm",
              "start": 1771282341068,
              "status": "failure",
              "tasks": [
                {
                  "id": "1771282341203",
                  "message": "merge",
                  "start": 1771282341203,
                  "status": "failure",
                  "end": 1771282345026,
                  "result": {
                    "code": "NOT_SUPPORTED",
                    "message": "Can't init vhd directory without using alias",
                    "name": "Error",
                    "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/_cleanVm.mjs:75:5)"
                  }
                }
              ],
              "end": 1771282345026,
              "result": {
                "code": "NOT_SUPPORTED",
                "message": "Can't init vhd directory without using alias",
                "name": "Error",
                "stack": "Error: Can't init vhd directory without using alias\n    at RemoteVhdDisk.init (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/disks/RemoteVhdDisk.mjs:78:31)\n    at async _mergeVhdChain (file:///opt/xo/xo-builds/xen-orchestra-202602162239/@xen-orchestra/backups/_cleanVm.mjs:75:5)"
              }
            }
          ],
          "end": 1771282345027
        }
      ],
      "infos": [
        {
          "message": "Transfer data using NBD"
        }
      ],

reverting back to commit a3139 and all is well again

Answering myself:

@dinhngtu downloaded on a windows server 2022, extracted and did the inf install. No visual feedback.
How do I know it was installed?

@Greg_E You've got a point, actually several.

The scripts exist for a reason because the official way is way to complicated. I still use them, having converted to xcpng @home (scripts) and @business 3 yrs ago.

There should be an official script, definitely. So all are on the same page. They have nothing to loose, everything to gain! The more people use it the better and having a simple way to officially install XO would help that.

Regarding XO6, I don't personally like it at all, mainly because I have to hunt around to find stuff, where in XO5 it's already automatic (not talking about missing features which revert us to XO5).
I actually don't like the UI, it is cramped especially on smaller laptop screens... But this is a personal preference.....

@gduperrey updated 2 hosts @home. 5 @office.
Had to run yum clean metadata ; yum update on cli (cancelling to run RPU in XO) for updates to appear.