In my previous blog post I explained how to manage your Email attributes in Office 365 by directly editing the Exchange attributes in your on-premises Active Directory. This works fine, but it is not recommended nor is it supported by Microsoft.
In this blogpost I’ll discuss how to add an Exchange server on-premises (or keep the last Exchange server when you’ve moved all Mailboxes to Office 365 for that matter) and manage your Exchange Online environment properly.
Exchange Server on-premises
So, what options do you have? Add an Exchange server on-premises, or keep one of the existing (hybrid) Exchange servers for management purposes. Since this is a green field Active Directory, and there’s no Exchange server on-premises you can use the free Microsoft Hybrid License to for this management server. For additional details on this free Exchange license you can check the Microsoft knowledgebase article KB2939261: https://support.microsoft.com/en-us/kb/2939261.
Continue reading Office 365 Directory Synchronization without Exchange server Part III
The Microsoft Directory Synchronization has been available in a variety of versions and names:
- DirSync (the original).
- Azure Active Directory Sync (AADSync).
- Azure Active Directory Connect (AADConnect).
Each version of the tool had a number of releases, for the original DirSync for example there were 14 different releases as can be seen here. Similar information for AADSync (5 releases) can be found here, and for AADConnect (12 releases) you can find it here.
In my test environment (Exchange hybrid) I’m currently running AADSync 1.0.491.413. Since the current (as of March 2016) version is AADConnect 188.8.131.52 it’s time to upgrade J
When upgrading from a previous version there are two options:
- In-place upgrade – this is the recommended way if the upgrade time takes less than three hours.
- Parallel upgrade – This is the recommended way if the upgrade time takes more than three hours.
Why three hours? The Directory Synchronization runs every three hours. It is also estimated that if you have more than 50,000 objects to synchronize, the upgrade will take more than 3 hours.
Continue reading Upgrade Azure Active Directory Synchronization to AADConnect
I used to run Skype for Business on-premises (ever since Lync Server 2010) and every year I was struggling with SSL Certificate renewal. Last time (few weeks ago) it didn’t work as expected (every now and then I could not respond to message) I decided to move to Skype for Business Online.
Since not too much SfB enabled users were involved I decided to decommission SfB on-premises first and then enable SfB in Office 365 (user accounts were synchronized from on-premises Active Directory to Azure Active Directory).
After fully decommissioning all Skype for Business servers on-premises I enabled the SfB licenses in the Microsoft Online Portal, but unfortunately I was not able to logon to SfB Online:
Continue reading Users do not show up in Lync Online
When you have implemented Directory Synchronization between your on-premises Active Directory and Office 365, and you move a user in Active Directory out of the DirSync scope (for example to an Organizational Unit that’s not synchronized) the user is removed from Office 365.
However, when you move the user back to an Organizational Unit that’s synchronized (i.e. in-scope) the password is no longer synchronized. So, when this user tries to logon to Office 365 services, the logon attempt fails. Only when you change the password in Active Directory, the new password is synchronized to Office 365, and the user is able to logon again to the service.
Very similar to this, when a disabled user in the on-premises Active Directory is enabled, the password is not synchronized to Office 365.
This is a known issue with DirSync or Azure AD Connect (up to November 2015). On November 4, 2015 Microsoft released a new version of Azure AD Connect that fixes this particular issue (together with a number of other fixes of course).
You can find more information regarding the updated version of Azure AD Connect on Sander Berkouwer’s blog A new version of Azure AD Connect was released today. You can download the new version of Azure AD Connect on the Microsoft Download Site.
In three earlier blog posts I explained how to implement directory synchronization and how to create an Exchange hybrid configuration:
These steps will create a hybrid configuration between your on-premises Exchange 2013 environment an Exchange Online, but to move mailboxes from Exchange on-premises to Exchange online (or vice versa) you need to create an endpoint. This an on-premises Exchange 2013 server (but it can be more) where the Mailbox Replication Service (MRS) is running, used to move mailbox data from one server to another. The process is similar to an on-premises mailbox move where the MRS is responsible.
Create a migration endpoint
To create an endpoint you have to go to the Exchange Admin Center in Office 365 and login as an Office 365 tenant administrator. You can get there via the Microsoft Online Portal, select Admin | Exchange, or navigate directory to the Exchange Admin Center, and login as an Office 365 tenant administrator.
In the Exchange Admin Center dashboard, under Recipients select migration. At this point an empty screen will be shown:
Continue reading Moving Mailboxes in a Hybrid Configuration – Part I