Subscribe to Windows IT Pro

 

Get Newsletters

  • Get the Latest News
  • Product Updates
  • Helpful Tricks
  • Productivity Tips

Subscribe Now!

October 17, 2006 12:00 AM

What are the Microsoft Exchange Server 2007 server roles?

Windows IT Pro
InstantDoc ID #93951
Rating: (6)

A. Exchange Server 2003 had a basic set of server roles: a back-end server that hosts information stores and performs the bulk of processing and front-end servers that accept client requests and proxies them to the appropriate back-end server. Exchange 2007 has a more granular set of server roles to give flexibility to larger Exchange deployments, while still allowing small to medium deployments to host all the required roles on one server if appropriate. The server roles are:

  • Mailbox. Hosts mailbox and public folder data. This role provides Messaging API (MAPI) access for Microsoft Outlook clients. Additionally a variation exists called the Clustered Mailbox role when hosting as part of a clustered environment; it requires no other Exchange roles running on the cluster instance
  • Client Access. Similar to the old front-end server role. Provides all other client protocol access, apart from MAPI (i.e., Outlook Web Access--OWA, POP3, IMAP, and ActiveSync)
  • Unified Messaging. Provides client access to mailbox, address box, and calendar via telephone and voice. Require Special IP-PBX or VoIP gateway software.
  • Hub Transport. Mail routing server that forwards mail to another hub transport server, edge server, or mailbox server. Unlike Exchange 2003, which uses Exchange routing groups, Exchange 2007 uses Active Directory (AD) sites.
  • Edge Transport. Gateway from the Exchange organization to the outside world. This is the last hop for outbound mail and the first hop for incoming mail. This is the server that provides mail quarantine. This role doesn't require AD access, making it ideal for perimeter deployment without opening up ports for AD access. This role must always be deployed on a server with no other Exchange roles.

The Mailbox, Client Access, Unified Messaging, and Hub Transport roles can be distributed across multiple servers or in combination with each other on potentially one server. Any AD site with a Mailbox role also requires a server in the same AD site running the Hub Transport and Client Access roles (or they can be installed on the Mailbox role server).

Related Content:

ARTICLE TOOLS

Comments
    There are no comments to display. Be the first one!
You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

White Papers

Get your Windows 7 deployment off to the right start by implementing PC lockdown. A locked-down environment is easier and cheaper to support since users are less likely to make unnecessary changes to the core system configuration - read more here!

Essential Guides

Is your iSCSI "lossy"? The reality is that most off-the-shelf Ethernet hardware deployed for iSCSI can lose packets, resulting in slow performance or application downtime. Learn how to assess your current iSCSI infrastructure and engineer an advanced iSCSI SAN infrastructure.

Web Seminars

What's the best way to keep your network safe from malware? In this web seminar, security expert Greg Shields suggests an alternative method to the traditional blacklisting approach that is common with anti-virus and anti-malware solutions.

eLearning Series

We bring the experts direct to you to share their real-world perspective and expertise. During each event, three sessions stream in real time, so you can learn, ask questions, and get solutions.
Upcoming event: Getting the Most with Exchange 2010 with Paul Robichaux

Subscribe to Windows IT Pro!

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.