For a couple of week one of my customer was complaining about little hickups in their Lync 2013 environment. It was working, but every now and then they had these strange little issues. When I moved my own accounts to Lync Online I was not able to federate with this customer anymore so it was time to start investigating.
In Exchange Server 2010 SP1 is was possible to create a hosting specific implementation by using the /hosting switch during setup. The /hosting implementation is discontinued by Microsoft and replaced by Address Book Policies in Exchange 2010 SP2 and the Address Book Policies solution is continued in Exchange 2013.
Almost two years ago I wrote a couple of blog posts regarding Hosted Exchange 2010 SP2 (or later):
- Building Hosted Exchange Part I (overview)
- Building Hosted Exchange Part II (Active Directory)
- Building Hosted Exchange Part III (Exchange and ABP’s)
- Building Hosted Exchange Part IV (Global Settings)
- Building Hosted Exchange Part V (SMTP routing in a multi-tenant environment)
When building Hosted Exchange 2013 things are not very different. You have to prepare Active Directory for hosting purposes and set the permissions in Active Directory on OU level. When it comes to Exchange 2013 itself, address list segregation is still achieved by using Address Book Policies. One thing that is fundamentally different is SMTP routing in a hosted Exchange. In Exchange 2010 3rd party Routing Agents were used, but in Exchange 2013 there’s an Address Book Policy Routing agent that respects the Address Book Policies that are provisioned for every tenant. Continue reading
When installing an Exchange 2013 Edge Transport server a self-signed certificate is created and configure for use with the SMTP Transport server. The self-signed certificate has the NetBIOS hostname as the Common Name and the FQDN in the Subject Alternate Names field.
You can view this self-signed certificate using the Certificate MMC snap-in: