Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the hueman domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/CloudIngenium.com/htdocs/wp-includes/functions.php on line 6114
Resolved: Essentials Server Integration must be done on the Domain Controller – Knowledge eXchange

Resolved: Essentials Server Integration must be done on the Domain Controller

Resolved: Essentials Server Integration must be done on the Domain Controller

Recently we performed a migration from our on premise Exchange server to Microsoft’s cloud solution: Exchange Online. Because of that I wanted to perform an integration at the domain controller level using Windows Server Essentials Experience. Unfortunately whether I tried using a member server or a domain controller I came coming across this error message:

Service Integration

This task must be performed on the domain controller

 As I mentioned, I did try this on a domain controller so the error message throws me off big time! It wasn’t until I read several blogs that I found out this error is generated one you have more than one domain controller. It doesn’t matter if they are both running Windows Essentials Server Experience or only one is, the error message is still there.

Obviously at this point there are few things you could do:

  1. Forget about integrating with Microsoft Online.
  2. Demote all but one server in your environment. Remember it is one DC and one Domain… having multiple Domains is a problem too. You can always DCPromo them back up after the fact. Obviously, Essentials would only work on the one that was configured.
  3. Write to Microsoft and hope they allow more than one DC.

It took me a while to figure this out as the message did not indicate the problem correctly but at least the solution was viable in our environment. For those who can’t demote other DCs *including read only ones* sorry but there is no other workaround. Hope this at least helps identify the issue.

Enhanced by Zemanta

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.