Apparently, Server 2012 Essentials doesn’t like the fact that I have joined it to a domain where I do not want it to be a domain controller, and due to this fact it is shutting down automatically every few days
Here’s the alert specifying why it is shutting itself down:
I have no intentions of allowing this server to be a domain controller. If I cannot find a work around that will allow me to continue running it as “a server that is simply joined to the existing domain” (and not experience it shutting down automatically every few days), I will be installing a different version of Windows Server.
I’m using this server to run one specific custom service (exclusively), and it does this just fine except for the fact that it shuts down automatically every few days (due to the enforcement of this FSMO policy).
Given that I’m not willing to allow this server to be FSMO (or even allow it to be an additional domain controller), is there any way that I can possibly prevent the enforcement of this restrictive policy?
Answer
Well, why on Earth are you using Server Essentials for that? Server Essentials is designed to be an all-in-one server solution for small businesses, not a dumb server running a simple service.
What you want is not possible with Server Essentials. The closest you can come is to install it in migration mode and join it to an existing domain, but there’s a time limit on that.
You can have only one server on your network that is running Windows Server 2012 Essentials, and that server must be a domain controller for the network.
You will need to install a different version of Windows Server, as suggested in TheCleaner’s answer.
Attribution
Source : Link , Question Author : LonnieBest , Answer Author : Community
