Exchange 2010 SP1 has built-in multi-tenant support, which helps service providers to host multiple organizations in a single Active Directory environment. There are few features which are available only in hosting mode and few others which are not available, compared to a normal deployment of Exchange 2010 SP1. 2010 SP1 will form part of the suite of multi-tenant capable products that will replace the Hosted Messaging and Collaboration solution.

 

Few points to note about installing 2010 SP1 in hosting mode:

  • The installation can only be done in command line.
  • You need to use /InstallWindowsComponents while running the setup to install all windows components required for Exchange.
  • You need to use /Hosting switch while running the setup to install Exchange in hosting mode.
  • 2010 SP1 is required.
  • Exchange Management Console will not be installed.

Exchange 2010 SP1 doesn’t support the following features in Hosting mode (from Technet):

  • Exchange Management Console
  • Public Folders
  • Unified Messaging Server role
  • GalSync
  • Federation
  • Business-to-Business features such as cross-premises message tracking and calendar sharing
  • IRM
  • Outlook 2003 support (EnableLegacyOutlook)
  • Edge Transport Server role
  • Same forest upgrade from Exchange 2007
  • Resource forest
  • Parent-child domains
  • Discontiguous namespace
  • Disjoint namespace

In order to install Exchange 2010 SP1 in hosting mode, run the following from an elevated command prompt.

Setup.com /Roles:m,h,c /InstallWindowsComponents /Hosting /OrganizationName:

Install 2010 SP1 in hosting mode

Don’t press any key as it will cancel the setup process.

No keypress in 2010 SP1 Hosting mode install

Installation pre-checks are carried out.

Role Checks

After the pre-checks are completed successfully, setup starts installing the three roles.

Hosting Mode Install Complete

As explained above, there is no EMC after the installation, only Exchange Shell & Help.

Tools in 2010 Sp1 hosting mode

 


Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts

Microsoft

Azure AD and Manual UPN Update

In Azure AD, the UserPrincipalName (UPN) can be manually updated using Set-MsolUserPrincipalName Power Shell cmdlet.  The details and syntax are explained here – https://msdn.microsoft.com/en-us/library/azure/dn194135.aspx One of the common issues you experience during this process is Read more…

Microsoft

Azure Password Reset – The Password you’ve selected does not meet your Active Directory password policy

This is a common error message when you try to reset a password from Azure management port or Self service portal.  The error message is very clear here – “The Password you’ve selected does not Read more…

Microsoft

Azure – Your account is temporarily locked to prevent unauthorized use

Here is the another common error message when dealing with directory and password synchronization.  Error Message: Your account is temporarily locked to prevent unauthorized use. Try again later. Contact Customer Support if the problem persists Read more…