Windows Essentails Server 2019, restart every tuesday morning

Question

Windows Essentails Server 2019, restart every tuesday morning,
Only 10 computer's are connected to it. Don't really do need the domain controller.I have disabled the silsvc.exe, by taking the ownership and still my server shutdown, but this i can see any event locgs that my Server Infrastructure Licensing have effect the shutdown.

I really don't want to confirgured it as domain controller.

Please help , as soon as poosible. i am really get upset in fixxing this, please help me

The process C:\Windows\system32\silsvc.exe (TRPSSEAS08) has initiated the shutdown of computer TRPSSEAS08 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Legacy API shutdown
Reason Code: 0x80070000
Shutdown Type: shutdown
Comment: Licensing Compliance Service caused a shutdown. Please look at the events under Microsoft > Windows > Server Infrastructure Licensing > Operational for details.

The User Count Check detected a condition in your environment that is out of compliance with the licensing policy. This server will be automatically shut down if the issue is not corrected in 4 day(s) 13 hour(s) 30 minute(s). Please look for additional events for User Count Check to troubleshoot.
Source link: https://social.technet.microsoft.com/Forums/windowsserver/en-US/99cbb543-7a7e-4b49-acbc-faa517dbe8d2/windows-essentails-server-2019-restart-every-tuesday-morning?forum=WinServerPreview

Answer 1

Welcome to Microsoft Q&A Platform.

Looks like a license cause, we can add a Windows 2019 Standard server to act as another DC.

But we need to buy CALs for our users. Essentials itself doesn't require CALs, however, when we introduce a full server, we will need to get them for all users since services, including DNS and authentication can be handled by either server.

For Windows Server Essentials, because of license limitation, it can only be deployed as Primary DC and holds all FSMO roles. If it do not met, licensing compliance component will force system shutdown.

Answer 2

If anyone ever comes across this issue again, what I found was that my SQL Express instance had created multiple accounts for running "R Scripts," and that's what caused the user account to exceed the 25 user limit and restart every week.