Odd as I’m not seeing any issue with connecting Windows 11 client computers up to (a straight out-of-the-box install of) Windows Server 2019, 2022, or 2025. Did you follow the tips I’ve given for doing that over in the “Suggestions, Limitations, and Known Issues” section of my main WSEE on 2019/2022/2025 article?

Also, if your Windows 11 client computers were recently upgraded to version 24H2, then they most likely became disconnected from the server during the upgrade process (and would show as being “offline” within the DEVICES page of the server Dashboard). If so, then you will need to completely uninstall the “Client Connector for Windows server Essentials” program from the client computer, restart it, and then reinstall the client connector software on it once again (by going to https://YourServerName/connect).

Additionally, if the client computer was previously joined to the domain, then you’ll most likely want to temporarily add Microsoft’s SkipDomainJoin setting to the registry of the client computer BEFORE running the client connector software on it, and then delete it afterwards. Doing that will prevent the client connector software from trashing the user profile that’s currently in use on the client computer (i.e. it’ll prevent it from trying to completely rejoin the domain again when reinstalling the client connector).

As for forcing the client computer to connect to the server via Kerberos… I know of no way to do that, and I imagine that doing so is not possible (i.e. something like that would most likely take a complete rewrite from Microsoft, and at this point, I seriously doubt that’s something Microsoft would be willing to do seeing as they’ve pretty much given up on Essentials now).