In a hybrid environment the on-premises Exchange organization (which can be either Exchange 2010 or Exchange 2013) is integrated with Exchange Online. In a hybrid configuration you basically create one ‘virtual’ Exchange organization with the following features:
- One cross-premises Address Book;
- Secure cross-premises mail flow;
- Cross-premises Free/Busy information, mail tips and out-of-office features;
- Seamless migration to Exchange Online and vice versa;
- No recreation of OST file;
- Automatic reconfiguration of Outlook profile;
- OWA URL Redirect.
To create a Hybrid environment you need at least one Exchange hybrid server on-premises. This can be an Exchange 2010 server but I always recommend using an Exchange 2013 server for this because of the improved hybrid connectivity in Exchange 2013. For redundancy purposes (and performance for larger environments) you better use multiple Exchange 2013 Hybrid servers.
Another prerequisite for creating a Hybrid environment is that you must have Directory Synchronization in place, so DirSync is used for synchronization user accounts, groups and contacts, all other communication is handled by the Exchange 2013 hybrid servers as shown in the following picture:
Continue reading Exchange 2013 Hybrid Prerequisites (Part I)
When you want to change an email address on a Mailbox in Office 365 you get the following error message:
The operation on mailbox “<mailbox>” failed because it’s out of the current user’s write scope. The action ‘Set-Mailbox’, ‘EmailAddresses’, can’t be performed on the object ‘Stacey Brown’ because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.
This issue is caused by the fact you’re synchronizing user objects from a local Active Directory using DirSync or WAADSync, and you want to change properties in Office 365. This is not possible since the Source of Authority is your local Active Directory, and not Windows Azure Active Directory. This means you have to change all the user’s properties in Active Directory, including his email address.
Continue reading The operation on mailbox failed because it’s out of the current user’s write scope
Microsoft has released Exchange 2013 CU9, three months after the release of CU8. Microsoft has made a solid Cumulative Update this time (just like CU8 by the way) and during testing not much issues were found.
There aren’t any new features in this Cumulative Update, and personally I don’t expect any new features anymore in future Cumulative Updates either. All development efforts at Microsoft are currently targeted towards Exchange Server 2016.
The official announcement of CU9 can be found on The Exchange Team Blog, CU9 itself can be downloaded from the Microsoft Download Center, just as the accompanying CU9 UM Language Packs.
Continue reading Install Exchange 2013 Cumulative Update 9
While configuring an Exchange 2013 organization in a hybrid scenario with Office 365 the Exchange Hybrid wizard stopped and showed the following error message:
Subtask CheckPrereqs execution failed: Configure Mail flow The Secure Mail Certificate on server HYBRID01 is not bound to the SMTP Service at Microsoft.Exchange.Management.Hybrid.MailFlowTask.CheckCertPrereqs()…
Continue reading The Secure Mail Certificate on server HYBRID01 is not bound to the SMTP Service
During an upgrade of an Exchange 2013 SP1 multi-role server to Exchange 2013 CU8 the upgrade crashed, apparantly on a strange Receive Connector configuration since the following error message was raised:
The values that you specified for the Bindings and RemoteIPRanges parameters conflict with the settings on Receive connector ” SERVER1\Relay Connector SERVER1″. Receive connectors assigned to different Transport roles on a single server must listen on unique local IP address & port bindings.
Continue reading Upgrade to CU8 Fails on Receive Connector misconfiguration