Homelab environment; just set up a virtual Windows server 2025 instance using AD. The server service seems to refuse to launch automatically and requires a manual start each time. I’ve increased the verbosity to ‘debug’.
I did a gpresult and shows the nx_user policy is active. It’s been linked to the correct group policy OU for the local domain. At least from what I can tell. And then ran secedit to dump user rights. The nx user shows up in the following: SeTcbPrivilege, SeIncreaseQuotaPrivilege, SeServiceLogonRight, SeAssignPrimaryTokenPrivilege, and SeDenyInteractiveLogonRight.
I am using the latest version, 8.16.1