@acebmxer I did install the certs, and everything went fine with that. But I never went back to try and install any uefi VMs through XO-Lite. Something I may or may not get back to, should really wipe the system and start fresh again to see how things have advanced.
Things may be changing, and my lab may not have a physical place in my world. Which troubles me because I'll need to model things if this path turns into reality. Lots of unknowns right now.
It has been suggested to me to run NUT server on something like a raspberry pi. This lets the pi run for a long time on the UPS, and also to auto boot if the UPS runs out. Then it could wake on LAN other devices after power comes back.
I have not implemented this plan yet, but on my to do list.
@JL457 a coworker was telling me about Intune, if you run Config Manager, there are some settings to let them work together. Not sure exactly what needed to be done, but apparently ours is fixed and ready for someone to learn what's what. Our contract allows some stupidly larger number of clients to be using Intune.
I'm not certain on the CPU age here, but maybe. If you set up on a newer host with the same OS and everything works, then yes the CPU could be declared as too old.
I haven't had my E5 v2 system up for several months, but it was working with Win11 24H2 back when it came out. That was on XCP-ng 8.3 before LTS, not sure if there would be a difference in the host OS. It should be working.
Did you use EFI or BIOS mode when you made the VM, all my testing was with EFI mode since win11 really prefers EFI. Shouldn't matter but worth looking at.
Also I was using the evaluation versions, Pro and LTSC, which again shouldn't be an issue but maybe.
https://www.microsoft.com/en-us/evalcenter/
Somewhat concerning since server 2025 uses the same core as Win11, normally what buggers one buggers the other.
Also, I didn't see which set of tools you are running, Xen 9.4.1 or the XCP-ng tools? Could be another variable, if you were using the Xen 9.4.x, it might be interesting to try going back to 9.3.3 if you had them. I know there is a security issue, but worth trying to see if older works.
How old is old? I had some problems with server 2022 a few years ago on old Xeon x5660 processors, wonder if 24h2 is failing on old things like Xeon v2.
I have not had the time to upgrade my servers yet, even in my lab I often fall back on 2022 because it's the old known thing at this point.
I do need to look into this though, I want to raise the domain/forest functional levels up to 2025 to see if that brings me anything when working with Win11. I'm really hoping they build a few more things (or put them back) into the GPO for win11, I'll probably find that they took more stuff out and put it into Intune.
All of mine are 2022, but saw this in previous driver versions with 2025. Low priority on this so I haven't fixed it yet.
The five I updated were all reporting properly as of last week when I looked at it last.
I still haven't fixed the OS drive showing as removable, I'll catch that before the August MS updates and reboot.
I probably would have just bought a cheap mini PC and used Virtual Box for this, which is something I did do in the past for an old XP machine when the hardware started to fail. Grabbed a disk to vhd of it before the final failure and loaded it into Vbox.
Might be able to do this in nested virtualization in XCP-ng.
Yes, master is really the host that controls all of this stuff, so you would need to run the command on a host running as master.
Each host defaults to be its own master, but when you join one to a pool it will "demote" itself from that role.
I'm doing the latest production level updates announced yesterday... My pool has never migrated VMs as fast as it is now.
That was migrating several at a time, moving VMs back to "balanced" at the end is moving them at about half that speed one at a time. This is more than double what I was able to do with the same hardware on 8.2.1. It looks like it is actually capping at the maximum 10gbps speeds that the x710 cards and my switch can handle, that's never happened, not even on my lab which has been on v8.3 for over a year.
(note to self, might be time to upgrade those x520 cards in the lab to x710)
Next month's Windows updates might be interesting, hope this increase holds for that process too.
Uggg... Just after I upgraded 8.2.1 to 8.3.x and did updates. Guess I have more waiting for me for later today or tomorrow.
I went from Citrix 9.3.3 to 9.4.1, and generally they have remained manual when I've upgraded. All these VMs started out with 9.2.x so this is probably the fourth update to them.
And all that said, I know the MAC address did not change, because I had a reservation for one of them and it was found properly before putting it back to manual. I think the XCP-ng side of things worked properly (no MAC change), but the driver side was the issue, and nothing you can fix since you don't write this driver.
I probably should have used the cleaner first, but I went straight to the Citrix installer like I've done in the past. Took about an hour to get the 5 VMs updated, now I can move on to other things that have been lacking. I've mentioned it a few times, but this construction has me way behind for the summer, and only a few weeks of work time left before students come back.
Better late than never I guess 
4 out of 5 of my Server 2022 VMs needed to have the networking set back to manual after the driver update. 5 out of 5 need to have the system drive marked as non-removeable, but I need to move on for a couple other things before swinging back to the system drives.
I let it sit for an hour while I was at lunch, if it didn't pick up by then, it wasn't going to restart. I haven't had time to look through the logs but I'd guess there was a timer that expired since it was taking so long to reboot the Master host.
All three of the hosts took about 30 minutes before reboot.
And then the load balancing was all wrong, when I finished the updates I did a rolling pool reboot. It refused to put any VMs on host 2 during this process, and once the pool reboot finished it spent about 30 minutes migrating VMs for what appeared to be no reason, twice ending up with all VMs on host 1 or host 3. After it finally stopped migrating, I manually migrated a few VMs off to host 2 and left it alone for the night. Just got back in and will be checking things this morning.
I'm doing the latest updates on my production pool, and found something that is really just an annoyance more than a problem.
3 hot pool with Intel Silver v2 and 128GB of ram in each host.
Click on the pool, go to updates, hit the rolling pool update button. VMs migrate out as normal, update get's transferred to Master as normal. Took over 30 minutes after this step to reboot.
Upon reboot, VMs did not migrate back. Task for Rolling pool update did not pick up where it left off. Manually migrated a single VM back to Master to see if things were really still working, seemed OK.
Went to lunch to see if it would sort itself out. Nope.
Came back from lunch, went to the third host and entered maintenance mode to migrate all the VMs, when done told it to install updates, when done told it to reboot. Waiting about 20 minutes so far and guessing it will be a full 30 before it reboots.
Why I say this is an annoyance more than a problem, because we need to be on XCP-ng 8.3 in another two months so I'm not sure this is worth a fix as long as everything functions when I have all three hosts updated.
We have a group of colleges together, and they got the price down to $120 per core for VCF, there are no other levels to buy.
And for the small system that we have, Vates would not be a huge amount less, only a couple thousand a year less which doesn't really push to find a different solution. But again I have not looked into education discounts yet so if that cuts the price in half, then it would be substantial enough that they might think about changing. We also pay for Dell vxrail, not sure how much that costs, but allows us to not employ a person to handle the cluster.
There are scripts to run that will set up the XO-CE, even an image you can download directly and answer a few questions to set the IP, etc. while downloading it. It's not hard and easy to document. If that user goes away, then it might get more complex, but there are a couple people that have made scripts on github to get the XO-CE running on many Debian based and many RHEL based linux, I think there is even a docker image if you are using docker stuff.
But I agree looking out for "the next guy" is something that needs to be done whenever possible.
As far as pricing for non-profit education, I'll have to contact sales again and see what I can do. I checked several years ago when things were kind of separate, now that support is all encompassing I need to check back and see what it will cost. I've just been running the XO-CE version but I like to support projects where I can, and if I can wedge a little money into my budget for support, I certainly will do that. With only 3 hosts and a handful of VMs, it's hard to come up with the money for the lowest tier.
One thing I really want to work with is XOstor, I think in my system this might be a good way to go forward for me. Cheaper than building new NAS (about $5000 each for two of them).
All that said, if it is a simple enough system, you probably aren't going to need much support beyond these forums.
[edit] Are we allowed to attach PDF documents to a post? I have simple instructions from when I set up 8.2 in my lab. I don't have newer documents made for 8.3 using XO-lite yet, but screenshots to put to words. XO-lite is changing the knowledge burden to get up and running by a significant factor, and I like where it is going!
Has anyone tried turning off delta, and turning off compression?
Not ideal, but its how I'm dealing with some different issues (windows with big empty disks).