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?