Access your Pro+ Content below.
Part 2: Deploying Exchange 2007 server roles
This article is part of the Exchange Insider issue of July 2009, Vol. 2
The entire Exchange Server architecture was redesigned for Exchange 2007. One result of this redesign is that Exchange 2007 servers have been assigned specific roles. Although server roles existed in Exchange Server 2003, there were fewer and they weren't as formally defined. When planning your Exchange Server migration, you'll have to take these server roles into account. This specifically means that you must deploy your Exchange 2007 servers in a particular order. The first server role that you must deploy is the Client Access Server (CAS), which, in Exchange 2007, is the equivalent of a front-end OWA server. Once your CAS is in place and has been tested, you can decommission the front-end OWA server. Deploy the Hub Transport Server next. In Exchange Server 2007, all messages flow through the Hub Transport Server, regardless of whether they're sent internally or externally. While the idea of a Hub Transport Server may seem odd, every Exchange Server 2007 organization has at least one. However, unless you have a very large ...
Access this PRO+ Content for Free!
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Features in this issue
Learn about the Exchange 2007 Client Access, Hub Transport, Mailbox, Edge Transport and Unified Messaging server roles and the order to deploy them.
Explore the importance of the email component in enterprises, how traditional communication has evolved and where unified communications fit with Exchange Server 2007.
News in this issue
Each organization handles Exchange Server email archiving differently. And the wrong approach can be detrimental. Can your archives get you in trouble?