UPDATE: be sure to see this important development:
Check it out:
“This download contains topics that will help you plan, deploy, and manage Exchange Server 2010 SP1 (beta) in a multi-tenant organization.”
“Microsoft Exchange Server 2010 SP1 will form part of the suite of multi-tenant capable products that will replace the Hosted Messaging and Collaboration 4.5 solution.”
There have been several TechNet threads on Address List Segregation, which this approach encompasses – but only indirectly. Deploying Exchange in the abovementioned multi-tenant configuration requires a special configuration of Active Directory. This is not something you simply choose to implement one day; but instead you build your forest to support in the first place. Exchange 2010 (with the /hosting switch) must be deployed in a new forest at Windows Server 2008 functional level.
The infamous “Address List Segregation” whitepaper is still not released. Don’t consider deploying Exchange in a hosted configuration just for this feature. I would hang on. Watch Dave’s Blog for updates.
Some other interesting points about multi-tenant support:
- You must install Exchange 2010 (SP1) from the command line in order to use the /hosting switch.
- Correction: You must disable the Exchange Control Panel (ECP) [This is optional, not required]
- The following cmdlets listed in this section are those that are only available for Hosting Deployments.
Exchange 2010 SP1 doesn’t support the following features in Hosting mode:
- Exchange Management Console
- Public Folders
- Unified Messaging Server role
- Business-to-Business features such as cross-premises message tracking and calendar sharing
- Outlook 2003 support (EnableLegacyOutlook)
- Edge Transport Server role