Exchange 2010 SP2: The HCW Makes it Easier to Adopt the Cloud

Microsoft Exchange Server 2010 Service Pack 2 (SP2), released earlier this week, includes the Hybrid Configuration Wizard, which makes setting up coexistence between Microsoft Office 365 and on-premises Exchange much easier.

Paul Robichaux

December 8, 2011

4 Min Read
ITPro Today logo

This week, Microsoft announced the release of Exchange Server 2010 Service Pack 2(SP2). Earlier in theyear, Microsoft promised that SP2 would be released before year's end. Sure enough, there's still plenty of December left and SP2 is available for download. You've probably already heard about its major features: OWA Mini (which I suppose can be considered "major" despite its lightweight nature),address book policies, and the new Hybrid Configuration Wizard (HCW). Of these, the HCW is probably the most interesting, both from a technicalstandpoint and the standpoint of Microsoft's strategy to make Office 365 more appealing.

Microsoft has always used a specific vocabulary when talking about moving from one version of Exchange Server to another. For example,migration and upgrade have different nuances. In the same vein, what Microsoft considers a migration to Office 365 involves movingall of your mailboxes, Lync users, and SharePoint data to the hosted service. By contrast, coexistence means what the name implies: twosystems happily exchanging mail with each other. In Microsoft lingo, hybrid mode means coexistence between your own on-premises Exchange 2010servers and Office 365.

When you understand that distinction, the rationale behind shipping a wizard to ease the process of hybrid set up makes perfect sense. Smoothing thehybrid path makes it easier for organizations to sample Office 365, as well as possibly lowering the entry cost and support burden for new Office 365customers-both for the customers and for Microsoft itself.

In a presentation at TechEd North America earlier this year, Microsoft's Jim Lucey claimed that there were roughly 50 steps required to set up fullhybrid coexistence between an on-premises Exchange 2010 environment and Office 365. I never counted the steps, but this number certainly seemsplausible. Many of these steps are things you would need to do anyway, such as correctly configuring Autodiscover, but some are unique to setting uphybrid mode. The HCW cuts the number of required steps to about 6.

The HCW can actually be run in two distinct phases. In the first phase, the wizard creates a new Active Directory (AD) configuration object that's usedto hold hybrid configuration information. In the second phase, the Manage Hybrid Configuration wizard configures the actual parameters you specify onthat AD object. This two-step approach means that you can run the HCW now, well before you're ready for hybrid operation, so that your directorychanges are made and have time to replicate and stabilize. Now would probably be a good time to point out that SP2 requires an AD schema update, withall the attendant planning and testing that such updates involve.

So what does the HCW actually do? The changes it makes are all fairly simple. It adds an accepted SMTP domain for your Office 365 domain (which has theform so that your servers can interchange email with the cloud. If you have a federation trust with theMicrosoft Federation Gateway, it's added to the hybrid configuration object; if not, a trust is created. Either way, the necessary organizationalrelationships are added to the trust so that your organization can share calendar data, MailTips, and so on.

The wizard also turns on the proxy necessary for the Mailbox Replication Service (MRS). This step is critical because without the proxy, you can't movemailboxes between your organization and the cloud. In addition, the HCW makes the necessary changes to enable mail flow between your organization andthe cloud; this process consists of setting up send and receive connectors to funnel mail back and forth to the cloud through Forefront OnlineProtection for Exchange (FOPE).

None of the steps the HCW takes are particularly difficult; they do, however, require a pretty good understanding of both on-premises Exchange 2010 andMicrosoft's Office 365 implementation, whether or not you're using the wizard. Packaging the configuration process into a simple wizard is a smart moveon Microsoft's part, and I believe it will nudge customers who've been considering testing Office 365 in hybrid mode to do so. Clearly, Microsoft hopesto convince many of these try-before-you-buy customers that adopting in the cloud is the right move for their businesses. Anything that helps smooththe path for customers is thus a good strategy for Microsoft to take.

The HCW documentation is available from the Microsoft TechNet article "Understanding the Hybrid Configuration Wizard." If you're considering using the HCW, understanding what it does and how it works arecritical.

As for the rest of Exchange 2010 SP2, I'll have more to say after I've spent more time working with it in production. In the meantime, I'd love to hearyour thoughts on whether Microsoft's focus in SP2 matches the things you most hope to see. Drop me a line and let me know what you think.

Sign up for the ITPro Today newsletter
Stay on top of the IT universe with commentary, news analysis, how-to's, and tips delivered to your inbox daily.

You May Also Like