-1

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:

enter image description here

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?

TheCleaner
  • 32,627
  • 26
  • 132
  • 191
LonnieBest
  • 1,510
  • 4
  • 22
  • 39
  • 3
    This question appears to be off-topic because it is about how to use a product for purposes not allowed its licensing restrictions. – Jacob Apr 03 '14 at 15:18
  • 1
    This question appears to be off-topic because the OP completely failed to understand what the product he has purchased should be used for. – Dan Apr 03 '14 at 15:20
  • This is not off-topic. I understand perfectly. Dan only thinks inside the box. The topic is about disabling a policy enforcement. Dan don't like that topic, but since it IS the topic, it is not "off topic" – LonnieBest Apr 03 '14 at 15:31
  • Better said: Restricted Topic. That's fine. – LonnieBest Apr 03 '14 at 15:33

2 Answers2

11

2012 Essentials has to be a domain controller. Install a different version of Windows Server.

TheCleaner
  • 32,627
  • 26
  • 132
  • 191
  • If there were a way to disable or fool the service that is checking for this requirement, it would prevent me from having to deploy a different server version. I need this server to do so little, and it is a shame that an arbitrary policy it preventing it from doing something it would be otherwise be quite capable of. – LonnieBest Apr 03 '14 at 14:58
  • 7
    @LonnieBest And if there were a way to disable threads on my screws, I could use them as nails. But, such is life. The better approach, however, is that if you want a screw, use a screw and if you want a nail, use a nail. – HopelessN00b Apr 03 '14 at 15:00
  • 1
    This also has licensing implications, I think. – MichelZ Apr 03 '14 at 15:02
  • 3
    @HopelessN00b really drove that point home. – MDMoore313 Apr 03 '14 at 15:03
  • 1
    When the screw has been intentionally dipped in Gorilla Glue, preventing it from functioning as it could (without the glue), I like the idea, also, of removing the unnecessary glue. This why I use Linux for everything I can; you don't encounter these intentional sabotages of things not working decidedly. – LonnieBest Apr 03 '14 at 15:04
  • 3
    @LonnieBest You're not grasping it - Essentials is there to fill a small market gap and fulfil a specific role. You are not that market and this product does not work for you. Use the correct tool for the job. – Dan Apr 03 '14 at 15:06
  • @LonnieBest - I don't know what "custom service" required you to pick Essentials to begin with other than maybe price. But regardless, there isn't a workaround to this...MS is pretty clear here. – TheCleaner Apr 03 '14 at 15:07
  • @TheCleaner It was picked because it was the only spare license the company had. It does indeed work, it just shuts down do to this policy. – LonnieBest Apr 03 '14 at 15:11
  • @Dan I grasp it just fine, Dan. I just don't give up so easily. I've found workarounds for stuff like this in the past. I'm just checking here to see if anyone else has discovered a way disable the enforcement of this shutdown ramification. – LonnieBest Apr 03 '14 at 15:14
  • @LonnieBest It doesn't work, though does it? The fact it shutdowns and isn't licensed means it's *broken*. Any workarounds would be a breach of licensing, you realise that? – Dan Apr 03 '14 at 15:14
  • 2
    If price is an issue, stick it on a Win7/8 box if it can be done. Otherwise, this is really just "chat" at this point. The best option is to get Windows Server Standard if it requires a WinServer OS. – TheCleaner Apr 03 '14 at 15:15
  • 5
    @LonnieBest Please don't ask us how to defeat software licensing restrictions. That's not what we're here for. – Michael Hampton Apr 03 '14 at 15:17
8

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.

Community
  • 1
HopelessN00b
  • 53,795
  • 33
  • 135
  • 209
  • I using it, because the company has a license for installing it. I installed this a few months ago, using the migration mode you speak of, right off the bat. I didn't know that there was a time limit on it at that time. Now I know this due to it shutting down automatically every few days. – LonnieBest Apr 03 '14 at 15:10
  • @LonnieBest At the risk of getting an answer, let me ask... why do you care? So what, if it has to be the FSMO role holder and be on a domain? Put it on its own domain and don't use that functionality. Just run the service. What's wrong with that option? – HopelessN00b Apr 03 '14 at 15:12
  • Because on this domain, all windows servers and workstations are joined to a Zentyal domain provided by 2 Zentyal Domain Controllers. This service that is running must authenticate users with that domain. I was not aware that 2012 essentials had to be FSMO when I initially set up this service on this server. Everything worked great for a long while, then this policy enforcement finally got me after an expired time of working as intended. – LonnieBest Apr 03 '14 at 15:25