Almost two years ago I wrote a couple of blog posts regarding Hosted Exchange 2010 SP2 (or later):
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 Hosted Exchange 2013
In Exchange 2010 a new feature will be available called Address Book Policies which makes it possible to use multiple Address Books in Exchange 2010, completely separated from each other. It is sometimes referred to as multi-tenancy for Exchange 2010 although this is not entirely true. In this article I’d like to explain a bit more.
Address List Segregation
For Exchange 2007 Microsoft has a whitepaper available that describes how to implement Address List Segregation to achieve multiple Address Lists completely invisible for each other. In other words, users in the Contoso.com Address List don’t see other Address Lists and users, like the Fabrikam Address List or the Tailspintoys Address List. In Exchange 2007 this is implemented using Access Control Lists (ACL’s) to set permissions for specific Address Lists. This works fine for Exchange 2007 but Exchange 2010 uses a different technique called the Address Book Service running on the Client Access Server. Therefore, if using (or trying to use) the Address List Segregation whitepaper on Exchange 2010 things will horribly break. Continue reading Exchange 2010 SP2 Address Book Policies
In my earlier blog posts Building Hosted Exchange Part I (overview) and Building Hosted Exchange Part II (Active Directory) I explained the basics and how to configure Active Directory for a multi-tenant environment. In this posting we’re going to continue with the Exchange part of the multi-tenant environment.
Exchange 2010 SP2
In the previous post I used a simple Powershell script to create the Organization Units in Active Directory for three different companies that will be hosting in our sample environment. Besides the creation of the OU’s the script also sets the appropriate permission on the OU’s. The structure looks like this: Continue reading Building Hosted Exchange – Part III
Everybody that has hosted Exchange 2010 running using the /hosting switch knows it is a real painful experience. It is difficult to implement, it is difficult to maintain and there quite a lot of functionality missing like UM, Public Folders, the Exchange Management Console and integration with other products like Lync Server 2010 or Sharepoint Server 2010.
There has been a lot of complaints from hosters about this situation at Microsoft and Microsoft had to make a painful decision: Microsoft will no longer invest in the /hosting version of Exchange Server 2010 and it will be discontinued in the next version of Exchange Server (code name Exchange 15).
Continue reading Exchange /hosting discontinued