[There's a reason that Yoda is the unofficial mascot of SBS.  Size indeed matters not.] You should be aware of the following before you deploy Services Integration features: - THE OFFICIAL BLOG OF THE SBS DIVA
Wed, Dec 4 2013 21:49 bradley

You should be aware of the following before you deploy Services Integration features:

So everyone is aware:

http://blogs.technet.com/b/sbs/archive/2013/11/04/services-integration-overview-for-windows-server-2012-r2-essentials-part-1.aspx

"You should be aware of the following before you deploy Services Integration features:

  1. Windows Azure Active Directory integration will be turned on automatically when you turn on either Office 365 or Windows Intune. This is because they both leverage Windows Azure Active Directory as a common identity platform.
  2. Currently, the Services Integration features, including Windows Azure Active Directory integration, Office 365 integration, Windows Intune integration, and on-premises Exchange integration, are only supported in a single domain controller environment. In addition, the integration wizard must be run on a domain controller."

If you were planning to have two DCS in your Essentials role network, this can't be done at this time.  I, along with other partners that have opened support cases are asking this to be changed.  There's no eta of when a fix will be done.

So for now, be aware of this limitation.

Filed under:

# re: You should be aware of the following before you deploy Services Integration features:

Thursday, December 05, 2013 2:52 AM by Paul Crosbie

It can be done. I have done it. You just have to deploy the services integration features prior to adding the second domain controller. Also make sure you use an account with a non-expiring password because you can't update it without demoting the second controller.

It might not be pretty or hassle free but it can be done.

# re: You should be aware of the following before you deploy Services Integration features:

Thursday, December 05, 2013 5:53 PM by bradley

That's not a good solution and a lousy workaround.