XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Windows Server 2025 on XCP-ng

    Scheduled Pinned Locked Moved
    Compute
    10
    44
    3.8k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Chemikant784 @archw
      last edited by

      @archw
      Hi, i thought the same today so i gave a try. But unfortunately at my test server fully patched with fresh ADDC on it there are the same issues present. But i have to say that i did not a detailed test at this time.

      1 Reply Last reply Reply Quote 0
      • D
        dinhngtu Vates 🪐 XCP-ng Team
        last edited by

        The latest WS2025 patches fixed the issue for me.

        G 1 Reply Last reply Reply Quote 1
        • G
          Greg_E @dinhngtu
          last edited by

          @dinhngtu

          Thanks, I'll have to give this a try when I get some time, I can set it up on the gigabit network on my lab. Might even do this today because it's a task I can do while getting interrupted.

          G 1 Reply Last reply Reply Quote 0
          • G
            Greg_E @Greg_E
            last edited by Greg_E

            @Greg_E

            Ok, this was again not as straight forward as we might like. System as follows:

            XCP-NG 8.3 (current)
            vTPM, vUEFI, vSecureboot
            NFS share
            Management Agent 9.4
            Server 2025 with November 2024 cumulative update applied (not important)
            AD DS, DNS, DHCP installed and configured

            After several reboots I was still getting the problem:
            server2025-3.png

            Thinking a little more, I decided to switch from Automatic to Automatic (Delayed Start)

            The delayed start seems to have fixed the issue for me:
            server2025-4.png

            I've had this issue before with other services, we handle audio and video devices which have some demanding start routines so I should have thought of this earlier. Simply changing to delayed start lets another necessary service start which then allows the MA to start.

            Also, the horrible lagging I mentioned earlier was from a Truenas issue that I didn't know about until a couple days ago, patch your Electric Eel if you haven't done this yet. It's still a little laggy, but not like it was when I mentioned the problem before. All work so far has been through the XO console which is running on an old HP T630 which is pretty slow.

            Going to monitor this for a while before I dig too deeply into setting this up, it's my second physical network on my lab which is also the second physical network on my VMware system, I'm sure I'll need to do more configuration than just DNS and DHCP down the road. I'll probably form a trust with the first network AD DS, just to give that some practice and see what 2025 might bring. Eventually I'll need to upgrade my production network to 2025, so I'm justifying the time spent in research for the future, I'm already Windows 11 for all my clients, so Server 2025 should play more nicely and might bring some features back that they removed from 2022 (some GPO to start).

            server2025-5.png

            C 1 Reply Last reply Reply Quote 0
            • C
              Chemikant784 @Greg_E
              last edited by

              @Greg_E
              Hi Greg_E

              Thanks for your detailed report and informations 🙂 I will try it with delayed start. It could be a solution indeed. When i have news on this, i will share it here.

              C 1 Reply Last reply Reply Quote 0
              • C
                Chemikant784 @Chemikant784
                last edited by

                My three test systems seems to work properly when the management agent start type is set to delayed. So i think this can be a workaround for the moment.

                G 1 Reply Last reply Reply Quote 1
                • G
                  Greg_E @Chemikant784
                  last edited by

                  @Chemikant784

                  Since it doesn't seem to hurt anything, maybe it should get pushed up the chain to Xenserver and have them just change the MA installer to make this delayed start. But for now maybe this needs to be a note in the documentation that the user may need to change to delayed start for Windows 2025 running any parts of AD. If there are clearer images needed, let us know and one of us will grab some. Fell free to use my images in this thread in the official documentation if desired/needed. Should probably work up a few showing what this looks like from "normal" server view (no GUI), because as we know (people keep telling me) real admins don't use a GUI!
                  (aside, if that's true, why does Xen Orchestra exist??? Why does vCenter??? Why does Prism??? 😉 )

                  Also keep an eye on your server 2022, you never know when Microsoft will push a "fix" for something in AD and break the MA on currently working systems. We all know they have a habit of doing things like this. But I have a feeling it is the functional level of 2025 that is breaking this, something that should probably be tested but I don't have the time right now to delete it and set it back up at functional level 2016 and see what happens.

                  G 1 Reply Last reply Reply Quote 0
                  • G
                    Greg_E @Greg_E
                    last edited by

                    @Greg_E

                    Also I should say that I've rebooted many times and still OK, going to leave it baking while I get on to other things.

                    1 Reply Last reply Reply Quote 0
                    • D
                      dinhngtu Vates 🪐 XCP-ng Team
                      last edited by dinhngtu

                      After some testing, I've found that running any service that creates a form (of which Xen management agent is one) will trigger the issue. This points to an issue in Windows Server itself rather than the Xen guest agent.

                      I've created a thread on Microsoft Community to keep track of the issue: https://answers.microsoft.com/en-us/windowserver/forum/server_performance-servertop_application/creating-an-ui-autostart-service-on-a-server-2025/c2ced91b-21c2-49c1-86a6-24b90dc72c6d. In the meantime, please use @Greg_E's method of setting the Xen management agent service to delayed start to work around this issue.

                      I'm investigating further.

                      G 1 Reply Last reply Reply Quote 1
                      • G
                        Greg_E @dinhngtu
                        last edited by

                        @dinhngtu

                        I haven't had time to install anything else on this VM, I'll have to think about other roles or features that I might want to try to see if additional services will cause additional problems. WDS might be a good one since it opens up a few different services, but really only good for Win10 stuff these days.

                        I could install the Shoutcast server (as a service), but not sure if it plays nice with AD DS, would be simple enough to point a stream at it and play the audio locally once it is set up.

                        Do you think Zabbix agent would trigger it? I could get that going pretty quick and use it to test things with Zabbix while doing it.

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post