@probain Well I’ve been running commit 035ee for a few days now and haven't had any problems. But haven't done a lot of work with it. When I update, I always run some kind of full/complicated update since I've had some problems before and with this type of update I've never had any issues. sudo su nvm install 22 && npm install --global yarn && cd ~/xen-orchestra/ && git checkout . && git pull --ff-only && yarn && yarn build --force && yarn run turbo run build --filter @xen-orchestra/web && systemctl restart xo-server.service && cd && systemctl daemon-reload Or maybe just a simple CTRL F5 in Your browser will work

@paco On the stuck server, could you warm migrate the vms to one of the other hosts? Or could you shut down a VM at a time and cold migrate them? The second option is certainly not ideal, but maybe?

@Greg_E said in XCP-ng Windows PV tools announcements: @john.c I'll have to update group policy and check that out, would be a time saver. Everything I use is an Enterprise level of some kind, using EDU in production right now, and Pro/Enterprise evaluation in the lab. I was looking at running a post imaging script to prevent some of the bloat, but a GPO might be easier. You can use Windows ADK to customise the installation media and build a custom ISO. That file can then be placed on your ISO SR. The GPO is especially effective when combined with a custom ISO built using Windows ADK. I have tried this myself and it’s very effective doing it this way, the Windows ADK tool is very powerful but will require time to learn. Will save time with all of the extra installations, if you use a custom ISO.