This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
We're currently experiencing a problem with a on-prem DC running windows server 2019 essentials and it's connected to a AZ AD in the cloud. The server has been shutting down once a week because of an executable "silsvc.exe"
error:
“This process C:\Windows\system32\silsvc.exe (REDACTED) has initiated the power off of computer REDACTED on behalf of user NT AUTHORITY\SYSTEM for the following reason: No title for this reason could be found
Reason Code: 0x2000c
Shutdown Type: power off
Comment: Licensing Compliance Service caused a shutdown. Please look at the events under Microsoft >Windows> Server Infrastructure Licensing > Operational for details.”
If anyone has any solutions to fix this problem, I would greatly appreciate it, I already know that the FSMOs all need to be on the 2019 essentials DC, but I need some further instructions (e.g. how to do that) to fix this problem.
Thank you.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
look at the events under Microsoft\Windows\Server Infrastructure Licensing\Operational for details
What was found?
Just checking if there's any progress or updates?
--please don't forget to upvote and Accept as answer if the reply is helpful--
"The FSMO Role Check detected a condition in your environment that is out of compliance with the licensing policy. The Management Server must hold the primary domain controller and domain naming master Active Directory Roles. Please move the Active Directory Roles to the Management Server now." Event ID 21
There are also Event IDs 38 which do describe when the Server will be shut down again because it's out of compliance with the abilities of a Windows Server 2019 Essentials Server.
Is this a new problem? or has it been working for a while now? Are there other domain controllers present?
So we have a Active Directory local Domain Controller set up with AZ AD, basically it pulls user accounts from Azure AD and then authenticates locally using those accounts. This shutdown occurs every week or so. We thought it was a power issue and replaced some hardware and updated completely, but my colleague correlated the shutdowns with this executable. I think what's happening is Windows 2019 Essentials needs all the FSMO roles under its control, not under the AZ AD. There's only one domain controller on prem.
So azure joined? or only using azure ad connect?