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

    Windows Server 2025 on XCP-ng

    Scheduled Pinned Locked Moved
    Compute
    10
    40
    1.1k
    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 @flakpyro
      last edited by

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • C
        Chemikant784 @archw
        last edited by

        @archw

        You should also notice that you cannot run any task scheduler tasks any longer. The task starts, but the action is not taken and after the timeout it end. Also any .msi package cannot be installed due to the Windows Installer Service is not able to start.

        G A 2 Replies Last reply Reply Quote 0
        • G
          Greg_E @Chemikant784
          last edited by

          @Chemikant784

          I noticed the installer when I was trying to update from the 9.3.3 to 9.4 agent, didn't know about schedulers being locked up.

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

            @Chemikant784
            So with this being patch Tuesday, two updates got installed:

            2024-11 Cumulative Update for Microsoft server operating system version 24H2 for x64-based Systems (KB5046617)
            2024-11 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Microsoft server operating system version 24H2 for x64 (KB5045934)

            For whatever reason, those processes are no longer showing up and I can run things from the scheduler??

            If you updated tonight, did yours go away?

            C 1 Reply Last reply Reply Quote 1
            • 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.

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