fern's Blog

Category Exchange Server 2007

November 16, 2007
What's New with Tools in Exchange 2007

Topic Last Modified: 2006-11-16

Our Microsoft® Exchange Server tools team has been busy working with existing tools to have them able to run in a Microsoft Exchange Server 2007 environment. This can be a relatively straightforward task such as adding new files to the build, or a complete overhaul, as in the case with the previous Load Simulator (LoadSim) tool, which has emerged as the new and improved Exchange Server Load Generator.

Here’s a brief rundown of some tools that are being released in the early part of 2007. The tools development and adaptation process is ongoing and we'll keep you informed about what’s happening through regular updates to Exchange TechCenter. For good, detailed articles about various tools see The Microsoft Exchange Team Blog.

Exchange Load GeneratorExchange Load Generator

The Exchange Load Generator will be replacing the current Exchange Load Simulator 2003. Exchange Load Generator will support Exchange Server 2007 and is backward compatible with Exchange Server 2003. Tests will now be run using a combination of methods, including a command line setup with which you can do many common tasks quickly. An example of a command line task is to generate a generic configuration xml file. This file then becomes the basis for achieving the setup and configuration of tasks through an easy-to-use xml configuration file.

There is also a new, clean approach to a graphical user interface (think Exchange Best Practices Analyzer), with an accompanying Help file in the left pane for accessing instructions for working with the user interface. Tasks that you can do by using the user interface include setting up remote users and generating reports.

Exchange Load Generator lets you simulate the delivery of multiple MAPI client messaging requests to an Exchange server. To simulate the delivery of these messaging requests, you run Exchange Load Generator tests on client computers. These tests send multiple messaging requests to the Exchange server, which causes a mail load.

You can look forward to better error recovery, if configured to do this, and an improvement in the code quality because of the issues that have been addressed over the past few months. Simulation accuracy has significantly improved and the tool will be supporting multiple types of Outlook clients. The new tool is currently in testing mode out in the community.

We hope you'll find that the improvements to this tool will make your job of benchmarking, pre-deployment validation, and stress-testing in a test (non-production) environment a bit easier and more robust. Expected date of release is January 2007.

 Exchange Server Profile AnalyzerExchange Server Profile Analyzer

The Exchange Server Profile Analyzer, which enables administrators to collect estimated statistical information from a single mailbox store or across an Exchange Server organization, has undergone the following updates.

  • Prerequisites now include Microsoft .NET Framework Version 2.0 Redistributable Package (x86). Additionally, servers that are to be analyzed by the tool will be able to run Exchange 2007 with the release of the upgraded tool.
  • New data collectors that include several for Microsoft Office Outlook® Web Access have been added for the tool to work with Exchange 2007. Read the document that is included with the tool for the current listing of supported data collectors. The Outlook Web Access data collectors have been conveniently categorized in the document according to the Exchange version number.
  • We’ve provided guidance in the document to help you configure accounts in Exchange 2007 to reflect using the new Exchange Management Console, and Exchange Management Shell.
  • Enhancements to the Exchange Server Profile Analyzer report.

Availability for the new version of the tool is January 2007.

Exchange Public Folder DAV-based Administration ToolExchange Public Folder DAV-based Administration Tool

At the start of November, we released version 2.7 of the PFDAVAdmin tool to the Tools for Exchange Server 2003 Web site. There were no new features in this release, but planning and coding is underway for a major update that includes new features and official supportability of Exchange 2007 in the first half of 2007.

The 2.7 version addressed several issues, and also provides our users with an early or preview version to try on Exchange 2007. (Note that this version is not officially supported.) This current version works in a "pure" Exchange 2007 topology, meaning you don't need to have Exchange Server 2003 or Exchange 2000 Server computers present. PFDAVAdmin does not have to be run on an Exchange 2007 server—it can also be run from a remote workstation.

Use PFDAVAdmin to perform several tasks related to public folder management, such as modifying folder permissions on folders in the MAPI tree, export and import replica lists, look for event registrations, modify the permissions of the Calendar folder in bulk, and many more.

 Exchange ActiveSync Certificate-based AuthenticationExchange ActiveSync Certificate-based Authentication

Look for a newly reorganized edition of the user documentation for the tool in early December. Note that at this point the tool will still be supported for Exchange Server 2003 only. However, in the first quarter of 2007, we will be releasing a new document that will cover support for Exchange 2007 and Windows Mobile® 5.0 Messaging and Security Feature Pack (MSFP).

The Exchange ActiveSync Certificate-based Authentication tool is intended primarily for IT professionals who must deploy and manage certificate-based client enrollment and authentication of Microsoft Exchange ActiveSync®, which is a feature of Windows Mobile 5.0 Messaging and Security Feature Pack.

 Exchange JetstressExchange Jetstress

Exchange Server Jetstress is an updated version of the Jetstress tool that was designed to help deploy Exchange Server 2007. This version is backward compatible as well with Exchange Server 2003. The updated Jetstress, which is what you should be using for your storage validation for Exchange 2007, offers several new features from previous releases.

This new version has been in a preview state for our partners for several months now, and the feedback was much appreciated. It has been very useful in addressing the new features and operational requirements of running stress testing on Exchange Server 2007. Here are some of the highlights of the new version.

  • More accurate measurement of maximum I/O throughput
  • Improved reporting
  • New graphical user interface (looks like the one for Exchange Server Best Practices Analyzer) for consistency with the rest of our tools

Jetstress will be available in the January 2007 timeframe.

Exchange Server Stress and PerformanceExchange Server Stress and Performance

The Exchange Server Stress and Performance tool is being upgraded to work with Exchange 2007 with the addition of a new test module for Outlook Web Access. This new module has been designed to stress Exchange 2007 Outlook Web Access. However the current WebDAV test module will still need to be used if you are running and testing Exchange 2003.

Other changes in the Exchange Stress and Performance tool include the removal of two of the previously supported protocols: OLEDB and Outlook Mobile Access.

This new version will be available in January 2007.

sb
November 16, 2007
Getting Started with Exchange Server 2007: Server Roles

Topic Last Modified: 2007-02-06

With the recently released Beta 2 of Microsoft® Exchange Server 2007 (formerly code-named “Exchange 12”), you will be able to install Exchange 2007 and experience the newly re-engineered technologies, features, and services that have been added into the Microsoft Exchange product line. I will explain the Exchange 2007 server roles and show you how Exchange 2007 has been re-designed to be the most comprehensive and flexible messaging solution that is available.

Exchange Server 2007 OverviewExchange Server 2007 Overview

Exchange 2007 has been redesigned to add extensive new features and functionality, and to improve the administrative and management experience. To support this improved administrative and management experience, Exchange 2007 introduces five distinct server roles. Each role provides specific functionality and features. These server roles are as follows: Client Access, Edge Transport, Hub Transport, Mailbox, and Unified Messaging. The server roles, except for the Edge Transport server role, can all be installed on a single physical server or be distributed across multiple servers, depending on your company’s needs and requirements. By using this modular approach to installing, deploying, and administering Microsoft Exchange, you can now more effectively control the features that are included with Exchange 2007.

Server RolesServer Roles

When a front-end and back-end Exchange topology was configured in earlier versions of Microsoft Exchange, the two servers performed very different functions. The front-end server acted as the gateway or proxy that would enable Internet mail clients like Microsoft Office Outlook® Web Access and RPC over HTTP access to a back-end server. The back-end server housed the mailbox and public folder databases. It serviced internal mail requests by using various clients, including Outlook and Outlook Web Access, directly over a LAN. The back-end server also serviced external requests from the front-end server for Internet mail clients.

Exchange 2007 provides five server roles that align with the way that messaging systems are typically deployed and distributed. A server role is a unit that logically groups the required features and components that are required to perform a specific function in the messaging environment. Each server role includes features that support its function together with related configuration and security settings and a list of predefined tasks for managing and configuring those features. By using the Exchange 2007 server roles, you can better control and secure your messaging environment. Exchange 2007 server roles are designed to install only the services that are needed for each role.

The following sections provide an overview of each Exchange 2007 server role and describe some of their features and functionality.

Mailbox Server Role

The Exchange Server 2007 Mailbox server role hosts both mailbox and public folder databases, and provides calendar access for users and messaging records management (MRM). The Mailbox server role is required if you plan to host user mailboxes, public folders, or both, on an Exchange 2007 server. However, if you want to implement all the features and functionality found in Exchange 2007, you will also have to install each of the other server roles.

Note:
The Edge Transport server role cannot coexist on the same computer with any other server role.

In Exchange 2007, the Mailbox server role integrates with the Active Directory® directory service better than the mailbox features and functionality in earlier versions of Exchange. This improved integration makes deployment and operational tasks much easier.

The Mailbox server role enhances and improves high availability and recovery for clustered Mailbox servers by including such features as: local continuous replication (LCR), cluster continuous replication (CCR), and single copy cluster (SCC). These high availability features provide enhanced recovery opportunities to meet your availability requirements. The Mailbox server role also greatly improves the Information Worker experience by providing more rich calendaring functionality, resource management, and more efficient offline address book downloads.

Client Access Server Role

The Client Access server role supports Outlook 2007 and earlier versions, Outlook Web Access, and Exchange ActiveSync in addition to the Post Office Protocol version 3 (POP3) and Internet Message Access Protocol version 4 rev1 (IMAP4) protocols. The Client Access server role also makes it possible to use Exchange 2007 features such as the offline address book, the Autodiscover service, and the Availability service. You must have the Client Access server role installed in every Exchange 2007 organization. The Client Access server role handles communications between clients and Microsoft Exchange. Although Outlook communicates directly with the Mailbox server, it uses the Client Access server role to connect to Exchange mailboxes when you are using Outlook Anywhere (formerly known as RPC over HTTP) and for services such as the Autodiscover service and the Availability service. The Client Access server role also enables users to use such Unified Messaging features as Play on Phone.

The following is a brief explanation of the functionality and features that are included with the Client Access server role:

  • Outlook Web Access   Outlook Web Access in Exchange 2007 lets you access your e-mail from a Web browser. It includes new features such as smart meeting booking, enhanced reminders and notifications, and integration with Microsoft Windows SharePoint® Services and Windows file shares.
    There are two versions of Outlook Web Access in Exchange 2007: the full-featured Outlook Web Access Premium client and the Outlook Web Access Light client. Outlook Web Access Premium requires Internet Explorer 6 or a later version but adds many enhancements and more functionality to the user interface. Outlook Web Access Light provides fewer features and is sometimes faster. Users should use the Light client if they are on a slow connection or using a computer with unusually strict browser security settings. If they are using a browser other than Internet Explorer 6 or later versions, they can only use the Light client.
  • Exchange ActiveSync   Microsoft Exchange ActiveSync® lets you synchronize data between your mobile device and Exchange 2007. You can synchronize e-mail, contacts, calendar information, and tasks. Devices that run Microsoft Windows Mobile® software, including Windows Mobile powered Pocket PC 2003 and Windows Mobile 5.0, are supported. Exchange ActiveSync is also supported on third-party mobile devices. For more information, see the documentation for your device.
    If you use a device that has Windows Mobile 5.0 and the Messaging and Security Feature Pack installed, your mobile device will support Direct Push. Direct Push is a technology that is built into Exchange ActiveSync that keeps a mobile device continuously synchronized with an Exchange mailbox.
  • POP3 and IMAP4   Besides supporting Exchange ActiveSync and HTTP clients, Exchange 2007 supports POP3 and IMAP4 clients. By default, POP3 and IMAP4 services are installed but are not enabled when you install the Client Access server role.
  • Autodiscover   Microsoft Exchange Server 2007 includes a new Exchange service named the Autodiscover service. The Autodiscover service uses a user's e-mail address and password to provide profile settings to Outlook 2007 clients and supported mobile devices.
    The Autodiscover service makes it easier to configure Outlook 2007. Earlier versions of Exchange and Outlook required you to configure all user profiles manually to access Exchange. Extra work was required to manage these profiles if changes occurred to the messaging environment or the Outlook clients would stop functioning correctly.
    The Autodiscover service enables Outlook 2007 clients to automatically connect to Microsoft Exchange and Exchange features, such as the Availability service or Unified Messaging, without having to manually configure their Outlook profile.
  • Outlook Anywhere   The Outlook Anywhere feature for Microsoft Exchange Server 2007 lets Outlook 2007 and Outlook 2003 clients connect to their Microsoft Exchange servers over the Internet by using the RPC over HTTP Windows networking component.
    This technology wraps remote procedure calls (RPCs) with an HTTP layer, which allows the traffic to traverse network firewalls without requiring RPC ports to be opened. Exchange 2007 greatly reduces the difficulty of deploying and managing this feature. To deploy Outlook Anywhere in your Exchange messaging environment, you have to enable at least one Client Access server by using the Enable Outlook Anywhere Wizard.

Edge Transport Server Role

Exchange 2007 Edge Transport servers are deployed in your organization's perimeter network and handle all Internet-facing mail flow, provide protection against spam, and provide secure message paths between business partners.

Spammers, or malicious senders, use a variety of techniques to send spam into your organization. No single tool or process can eliminate all spam. Exchange 2007 builds on the foundation of Exchange Server 2003 to provide a layered, multipronged, and multifaceted approach to reducing spam and viruses. Exchange 2007 includes a variety of anti-spam and antivirus features that are designed to work cumulatively to reduce the spam that enters your organization. Exchange 2007 also includes improved infrastructure for antivirus applications. Servers that run Exchange 2007 Edge Transport services help prevent users in your organization from receiving spam by providing a collection of agents that work together to provide different layers of spam filtering and protection.

Edge Transport servers offer you the following features:

  • Attachment Filtering   Attachment filtering filters messages based on attachment file name, file name extension, or file MIME content type. You can configure attachment filtering to block a message and its attachment, to strip the attachment and allow the message to pass through, or to silently delete the message and its attachment.
  • Connection Filtering   Connection filtering inspects the IP address of the remote server that is trying to send messages to determine what action, if any, to take on an inbound message. The remote IP address is available to the Connection Filter agent as a byproduct of the underlying TCP/IP connection that is required for the Simple Mail Transfer Protocol (SMTP) session. Connection filtering uses a variety of IP Block lists, IP Allow lists, in addition to IP Block Providers services or IP Allow Provider services to determine whether the connection from the specific IP should be blocked or should be allowed in the organization.
  • Content Filtering   Content filtering uses Microsoft SmartScreen® technology to assess the contents of a message. Intelligent Message Filter is the underlying technology of Exchange content filtering. Intelligent Message Filter is based on patented machine-learning technology from Microsoft Research. During its development, Intelligent Message Filter learned distinguishing characteristics of legitimate e-mail messages and spam. Regular updates with Microsoft Anti-spam Update Service ensure that the most up-to-date information is always included when the Intelligent Message Filter runs. Based on the characteristics of millions of messages, Intelligent Message Filter recognizes indicators of both legitimate messages and spam messages. Intelligent Message Filter can accurately assess the probability that an inbound e-mail message is either a legitimate message or spam.
    Spam quarantine is a feature of the Content Filter agent that reduces the risk of losing legitimate messages that are incorrectly classified as spam. Spam quarantine provides a temporary storage location for messages that are identified as spam and that should not be delivered to a user mailbox inside the organization.
    Content filtering also acts on the safelist aggregation feature. Safelist aggregation collects data from the anti-spam safe lists that Outlook and Outlook Web Access users configure and makes this data available to the Content Filter agent on the computer that has the Edge Transport server role installed in Exchange 2007.
    When an Exchange administrator enables and correctly configures safelist aggregation, the Content Filter agent passes safe e-mail messages to the enterprise mailbox without additional processing. E-mail messages that Outlook users receive from contacts or that those users have added to their Outlook Safe Senders List or have trusted are identified by the Content Filter agent as safe. The result is that messages that are identified as safe are not classified as spam and unintentionally filtered out of the messaging system.
  • Recipient Filtering   Recipient filtering compares the message recipients on the RCPT TO: SMTP command to an administrator-defined Recipient Block list. If a match is found, the message is not permitted to enter the organization. The recipient filter also compares recipients on inbound messages to the local recipient directory to determine whether the message is addressed to valid recipients. When a message is not addressed to valid recipients, the message can be rejected at the organization's network perimeter.
  • Sender Filtering   Sender filtering compares the sender on the MAIL FROM: SMTP command to an administrator-defined list of senders or sender domains that are prohibited from sending messages to the organization to determine what action, if any, to take on an inbound message.
  • Sender ID   Sender ID relies on the IP address of the sending server and the Purported Responsible Address (PRA) of the sender to determine whether the sender is spoofed or not. PRA is calculated based on the following message headers:
    • Resent-Sender:
    • Resent-From:
    • Sender:
    • From:
  • Sender Reputation   Sender reputation relies on persisted data about the IP address of the sending server to determine what action, if any, to take on an inbound message. The Protocol Analysis agent is the underlying agent that implements the sender reputation functionality. A sender reputation level (SRL) is calculated from several sender characteristics that are derived from message analysis and external tests.Senders whose SRL exceeds a configurable threshold will be temporarily blocked. All their future connections are rejected for up to 48 hours. In addition to the locally calculated IP reputation, Exchange 2007 also takes advantage of IP Reputation anti-spam updates, available via Microsoft Update, which provide sender reputation information about IP addresses that are known to send spam.
  • Domain Security   Domain Security refers to the set of functionality in Exchange 2007 and Outlook 2007 that provides a relatively low-cost alternative to S/MIME or other message-level security solutions. The purpose of the Domain Security feature set is to provide administrators a way to manage secured message paths over the Internet with business partners. After these secured message paths are configured, messages that have successfully traveled over the secured path from an authenticated sender are displayed to users as "Domain Secured" in the Outlook and Outlook Web Access interface.
  • Address Rewriting   Address rewriting, which is provided by the Address Rewriting agent on Edge Transport servers, lets you modify the addresses of senders and recipients on messages that enter and leave an Exchange 2007 organization. You can use address rewriting to present a consistent appearance to external recipients of messages from your Exchange 2007 organization. Address rewriting can be valuable to organizations that use third-party vendors to provide e-mail support and services. Customers and partners expect e-mail messages to come from the organization, not a third-party vendor. Similarly, after a merger or acquisition, an organization might want all e-mail messages to appear to come from the single new organization. The address rewriting feature frees organizations to structure their businesses by business requirements instead of by technical requirements or limitations
  • Edge Transport Rules   Transport rules that run on Edge Transport servers give you another tool to help you reduce the viruses that affect your organization. Because viruses can be released before anti-virus vendors have the chance to update their software, there can be a window in which viruses can enter your organization undetected. By using transport rules on Edge Transport servers, you can create transport rules that identify virus infected messages and remove or quarantine them.
    You can also use Edge transport rules to reduce the effect of denial of service (DoS) attacks on your organization by blocking or refusing delivery of these attacks at your network perimeter. This reduces the effect on network resources and also the cost of dealing with these attacks.
    Finally, Edge Transport rules can also protect your partners and customers by preventing unwanted or harmful messages from leaving your organization. Because internal client computers can sometimes because infected by a virus and send virus infected messages, Exchange enables you to apply the same transport rules to outbound messages to help prevent them from being delivered to your partners and customers.

Hub Transport Server Role

Microsoft Exchange Server 2007 Hub Transport server role is deployed inside your organization's Active Directory. It handles all internal mail flow, applies organizational message routing policies, and is responsible for delivering messages to a recipient's mailbox. Here is a brief explanation of the functionality and features included with the Hub Transport server role:

  • Mail Flow   The Hub Transport server processes all mail that is sent inside the Exchange Server 2007 organization before it is delivered to an internal recipient's Inbox or routed to destinations outside the Exchange organization. There are no exceptions to this behavior; mail is always passed through a Hub Transport server, because the Hub Transport server contains the message queues and the associated Send connectors and Receive connectors that are used to transport mail. This is true even if recipients and senders are located on the same mailbox server.
  • Message Categorization   The categorizer performs recipient resolution, routing resolution, and content conversion for all messages that move through a Hub Transport server.
  • Local Message Delivery   Only messages that are sent to a recipient with a mailbox in the same Active Directory site as the Hub Transport server on which categorization occurred are delivered locally. All messages delivered locally are picked up from a delivery queue by the Store driver and put in the recipient’s Inbox on a Mailbox server.
  • Remote Message Delivery   Remote message delivery occurs for messages that are sent to recipients in Active Directory sites that differ from the Hub Transport server on which categorization occurred, or for recipients that exist outside the Exchange organization. All messages that are sent to a different Active Directory site, to a mailbox that resides on a computer that is running an earlier version of Exchange, or to a mailbox that resides in a different Active Directory forest must be routed through a Send connector to a Hub Transport server that can deliver the message to the intended recipient. All messages that require delivery through the Internet must be routed through a Send connector to an Edge Transport server that can send messages to the Internet for delivery outside the organization, or to a Hub Transport server that is directly connected to the Internet.
  • Message Submission   Message submission is the process of putting messages into the Submission queue on a Hub Transport server. The categorizer then picks up one message at a time for categorization. There are four types of message submission:
    • SMTP submission through a Receive connector.
    • Submission through the Pickup directory or the Replay directory. Correctly formatted message files that are copied into the Pickup directory or the Replay directory are put directly into the Submission queue.
    • Submission by the Store driver, which picks up messages from a sender’s Outbox as they are sent.
    • Submission by an agent.
  • Antivirus and Anti-spam   Hub Transport services can be configured to provide additional layers of antivirus and anti-spam protection within the organization. This configuration is only recommended for small organizations that are not running Edge Transport server in the perimeter network. This configuration is achieved by using tasks that are contained within the Exchange Management Shell.
  • Transport Rules   Hub Transport servers let you apply transport rules to all messages that are sent and received in your organization. These transport rules, which are applied by the Transport Rules agent on Hub Transport servers, enable you to control or modify the delivery and content of messages based on conditions and exceptions that you configure. You can easily apply disclaimers, ethical walls, rights management, and more, to messages as they flow through your organization. Transport rules created on Hub Transport servers are automatically replicated using Active Directory to all Hub Transport servers in the organization. This enables you to apply the same messaging policies to your entire organization with ease.
  • Journaling   Exchange 2007 has greatly improved the journaling of messages that in and through your organization. You can now target journaling rules to specific senders or recipients, distribution lists and even messages sent to or from recipients and senders outside of the organization. You can specify whether journal reports are sent to an Exchange 2007 mailbox, or to Microsoft Exchange Hosted Services, or to a third-party archival solution. Journaling is done on Hub Transport servers by the Journaling agent, and all Hub Transport servers contain the same journaling configuration thanks to Active Directory replication. Because all messages that travel in and through your organization pass through a Hub Transport server, all messages encounter the Journaling agent. This provides you with a seamless journaling solution that can be applied throughout your organization.

Unified Messaging Server Role

Unified Messaging (UM) is new to the Microsoft Exchange product line. The Unified Messaging server role enables voice mail, e-mail, and fax messages to be stored in a user's mailbox. Users can then access their Exchange 2007 mailbox from a telephone or from a computer.

The Unified Messaging server role lets users access voice mail, e-mail, fax messages, and calendar information from an e-mail client such as Outlook or Outlook Web Access, from a mobile device that has Exchange ActiveSync enabled, such as a Windows Mobile® powered Smartphone or a personal digital assistant (PDA), or from a telephone.

Currently, many users and IT departments manage their voice mail and fax messages separately from their e-mail. Voice mail and e-mail messages are hosted on separate servers that are accessed through the desktop for e-mail and through the telephone for voice mail. Fax messages are not received into a user's inbox, but are instead received by stand-alone fax machines or a centralized fax server. Unified Messaging offers an integrated store for all messages and also enables users to access to their messages through the computer and the telephone.

Exchange 2007 Unified Messaging provides a single point of message administration for Exchange administrators in an organization. The functionality and features included with the Unified Messaging server role enable administrators to do the following:

  • Manage the voice mail, e-mail, and fax systems from a single administrative platform.
  • Manage Unified Messaging by using scriptable commands.
  • Build highly available and reliable Unified Messaging infrastructures.

Unified Messaging in Exchange 2007 gives users features such as:

  • Auto Attendant   An auto attendant is a set of voice prompts and system menus that gives users access to the Exchange 2007 Unified Messaging system. An auto attendant lets a caller use either the telephone keypad or speech inputs to navigate the menu, place a call to a user, or locate a user and then place a call to that user.
  • Call Answering   The Call Answering feature includes functionality to answer an incoming call on behalf of a user, play their personal greeting, record a message, and submit a message from another caller that will be delivered to their mailbox as an e-mail message.
  • Fax Receiving   The fax receiving feature lets users receive fax messages in their mailbox.
  • Outlook Voice Access   The Outlook Voice Access feature enables dial-in access from a telephone for UM-enabled users in an organization. Subscribers or those users who are UM-enabled can dial in to an Exchange 2007 Unified Messaging system and access their mailbox by using Outlook Voice Access. Outlook Voice Access users can access the Unified Messaging system and their mailbox by using either touchtone or voice inputs.
 ConclusionConclusion

It is very exciting to see the scope of the new features that are introduced by these new server roles in Exchange 2007. I hope you have enjoyed this overview of Exchange 2007 server roles and look forward to hearing from you. Ideas and comments are welcome and can be sent to exwcfb@microsoft.com.

 For More InformationFor More Information
  • For the most up-to-date information and to find additional Exchange 2007 documentation, visit the Exchange Server TechCenter.
  • For more information about Exchange 2007, including frequently asked questions, see the Frequently Asked Questions a bout Exc h ange Server 2007.
sb
November 16, 2007
Exchange 2007: Anywhere Access

Topic Last Modified: 2006-08-18

Businesses are increasingly on the move. Employees need access to all of their messaging data anywhere they happen to be - on the road, at home, or in the office. Companies that provide this anywhere access can lower expenses, increase efficiency, and provide their employees with the tools they need to excel at their jobs.

Messaging data used to mean e-mail messages. Now, it means e-mail, calendar, contact and task items, faxes, and voice mail messages. Microsoft Exchange Server 2007 provides access to all of these types of messages in one centralized location - the user's mailbox. Through a suite of new and enhanced features, you can now access all types of messages from anywhere: the office, your home, the airport, the ballpark, or the local coffee shop.

In order to provide this anywhere access to your messaging data, Exchange 2007 relies on several different server roles. A server role is a predefined set of features that can be installed on an Exchange 2007 server. You can install multiple server roles on the same physical server.

Note:
All server roles can coexist on the same Exchange 2007 server with the exception of the Edge Transport server role. This role must be installed on a separate server.

The Mailbox server role hosts mailbox databases, which contain users' mailboxes. It also contains the Public Folder databases. The Client Access server role accepts connections to your Exchange 2007 server from a variety of different clients. These clients include software clients and hardware clients such as mobile devices. It also provides access to Free/Busy data via the Availability service. The Unified Messaging server role uses your organization's telephony network and combines all types of messaging into a single system that can store e-mail, voice mail, and fax messages.

 Unified MessagingUnified Messaging

The Unified Messaging server role is a completely new role for Exchange 2007. This server role allows you to combine all types of messages in one Inbox that users can access from a telephone, a computer, or a mobile device. Before Exchange 2007, most IT departments managed their voice mail and fax messages separately from their e-mail. Often, to provide all three types of messaging required three different systems: a PBX and voice mail server for voice mail messages, stand-alone fax machines or a centralized fax server, and an Exchange server. Unified Messaging combines all of those systems into one Inbox.

Unified Messaging Features

The Unified Messaging server role provides the following features for Exchange 2007 organizations.

  • Call Answering   This includes answering incoming calls for a user, playing their personal greeting, recording a voice mail message and submitting it for delivery to the Inbox.
  • Fax Receiving   This includes receiving incoming faxes and directing them to a user's Inbox as an attachment to an e-mail message.
  • Subscriber Access   This feature allows users to dial in to the Unified Messaging server and access their mailbox using Outlook Voice Access. Users can navigate through the system by using their telephone keypad or voice inputs. The user can perform the following tasks.
    • Listen to voice mail messages and act on those messages.
    • Listen, forward, and reply to e-mail messages.
    • Listen to calendar information.
    • Access contact information and dial contacts stored in the Global Address List or Contacts folder.
    • Accept or cancel meetings.
    • Play and record personal and Out of Office greetings.
    • Set user security preferences and personal options.
  • Auto Attendant   The Auto Attendant is a set of voice prompts that callers hear when accessing the Unified Messaging system. The Auto Attendant lets the callers navigate through the system using the telephone keypad or speech inputs to locate a user or place a call. The administrator can perform the following tasks.
    • Create customizable menus for external users
    • Define a variety of greetings
    • Define holiday schedules
    • Enable callers to call the operator
  • Scripting and Customization   Administrators can group users and offer different service options to each group. For example, one group of users could be able to receive only voice messages while another group of users could be able to receive voice messages and fax messages.
 Exchange ActiveSyncExchange ActiveSync

Exchange ActiveSync is a synchronization protocol based on HTTP and XML that is designed to work over a cellular or wireless Internet connection. A cellular connection is slower to transfer data than a high speed network connection. Exchange ActiveSync is designed to work with these high-latency, low-bandwidth networks and transfer information quickly between Microsoft Exchange Server and your mobile device.

Note:
For this article, a mobile device is assumed to be a cellular telephone running software that supports synchronization with Microsoft Exchange via Exchange ActiveSync.

Exchange ActiveSync can synchronize e-mail messages, contacts, calendar, and task data. With the addition of Unified Messaging to your organization, you can also synchronize voice mail and fax messages attached to e-mails in your Inbox.

Exchange ActiveSync Features

Exchange ActiveSync has been greatly enhanced in Exchange 2007. Some of the new or enhanced features include the following:

  • Support for HTML Messages   You can download messages to your mobile device in either Plain Text or HTML format. HTML formatted messages allow for left to right scrolling as well as embedded images and active links.
  • Direct Push   First introduced in Exchange Server 2003 Service Pack 2; Direct Push uses a long-standing HTTPS connection to ensure your device is always kept up-to-date. As new items arrive in your Inbox, Exchange ActiveSync notifies your mobile device which initiates the synchronization.
    Note:
    To use Direct Push, your device must be running Windows Mobile 5.0 with the Messaging & Security Feature Pack, or the latest version of Windows Mobile, currently in beta testing.
  • Enhanced Device Security   Exchange 2007 supports Exchange ActiveSync policies. These policies can be applied on a per-user basis and control such settings as password requirements, Windows SharePoint Services document access, attachment downloads, and device locking settings.
  • Support for Message Flagging   You can set message flags on your mobile device. These flags will also be shown in Microsoft Office Outlook and Outlook Web Access.
  • Support for Exchange Search   Mobile devices often have only limited storage available. By default, Exchange ActiveSync will only store three days worth of messages on your device. However, you can now search for messages older than three days or those in other folders. When a message is found, it will be downloaded to your device.
  • File Share Access   Exchange ActiveSync can provide access to documents stored in Windows file shares and Windows SharePoint Services shares. This access can be controlled through Exchange ActiveSync policies.
    Note:
    Many of these features require that your device have the latest version of Windows Mobile, currently in beta testing.
Outlook Web AccessOutlook Web Access

Outlook Web Access provides access to your Exchange mailbox from any web browser. There are two versions of Outlook Web Access in Exchange 2007, Premium and Light. Outlook Web Access Premium provides access to all of your Exchange 2007 mailbox data. You can also view and manage mobile devices, set Out of Office options, group, sort, and flag messages, browse the Global Address List, and search your Exchange mailbox. Outlook Web Access Light provides access to e-mail, calendar, and contacts. It does not support tasks or notes. You can sort messages, but you cannot group messages, change your message view, or flag messages for follow up.

Note:
To use Outlook Web Access Premium, you must be using Internet Explorer 6.0 or the latest version. Outlook Web Access Premium is not supported on other browsers. Outlook Web Access Light is supported on recent versions of Netscape Navigator, Opera, Safari, and Mozilla Firefox.

Outlook Web Access Features

Outlook Web Access in Exchange Server 2007 has a number of new and enhanced features. Some of these features include the following:

  • Flexible Message Views   You can select how the message list is displayed, the position of the Reading Pane, and configure multiple grouping and sorting options.
  • Improved Notifications   Reminders and new mail notifications appear within the Outlook Web Access window and can be accessed through use of a drop down menu in the toolbar.
  • Scheduling Assistant   You can use the Scheduling Assistant to help schedule meetings with coworkers. The Scheduling Assistant provides suggested times and color codes days on the Date Picker as Good, Fair, or Poor.
  • File Share Access   You can access documents and document libraries on Windows SharePoint Services and Windows file shares through Outlook Web Access.
  • Voice Mail Options   If the Unified Messaging server role is installed in your organization, you can use Outlook Web Access to manage your voice mail options. You can configure the telephone access options, reset your voice mail password, or change the folder Outlook Voice Access reads when you access e-mail messages over the telephone.
Outlook AnywhereOutlook Anywhere

Outlook Anywhere for Exchange 2007 allows you to use Outlook 2007 and Outlook 2003 clients to connect to your Exchange server over the Internet using the RPC over HTTP Windows networking component. This eliminates the need for a Virtual Private Network (VPN) connection to your corporate network and still provides full Outlook functionality. Outlook Anywhere was known as RPC over HTTP in Exchange 2003. Exchange 2007 has improved and built on this functionality while simplifying deployment and management. Deployment of RPC over HTTP used to require significant server configuration. In Exchange 2007, simply use the Outlook Anywhere setup wizard on an Exchange 2007 computer with the Client Access server role installed. All users with mailboxes on Exchange 2007 are automatically enabled for Outlook Anywhere access.

Accessing Exchange 2007 Anywhere, AnytimeAccessing Exchange 2007 Anywhere, Anytime

Through the use of Unified Messaging, Exchange ActiveSync, Outlook Web Access, and Outlook Anywhere, you can access your Exchange 2007 mailbox data almost anywhere you happen to be.

Exchange in the Office

If you are in the office connected to your corporate network, you can use Microsoft Office Outlook or Outlook Web Access to view your Exchange mailbox. You can view e-mail messages, calendar data, contacts, tasks, and notes. If you receive a voice mail message, you can play that message through your computer speakers or play that message on the telephone. To play the message on the telephone, you must designate a Play on Phone number in the Voice Mail options tab of Microsoft Office Outlook 2007 or Exchange 2007 Outlook Web Access. If you receive a fax message, Unified Messaging will automatically route it to your mailbox as an attachment to an e-mail. Simply open the attached file to view or print your fax.

Exchange on the Road

If you leave the office for business or pleasure, you can take Exchange with you in several ways. Before you leave the office, you can configure Unified Messaging to play your Out of Office voice mail greeting to callers. You can also configure your Out of Office options for e-mail in Microsoft Office Outlook or Outlook Web Access. Exchange 2007 allows you to configure both an external Out of Office message and an internal Out of Office message.

Note:
The ability to configure an external Out of Office message can be enabled on a per-user basis by an Exchange Administrator.

When you're away from the office, you can use Exchange ActiveSync and a mobile device to stay up to date on your e-mail messages. If you receive a voice mail message, you can download and play the attached .wma file on your mobile device or call the Unified Messaging Subscriber Access number to hear your messages over the phone. If a fax message is routed to your Inbox, you can view the attachment directly on your mobile device or use Outlook Web Access or Outlook Anywhere to connect to your Exchange mailbox and view the attachment.

Note:
Viewing a fax message on a mobile device may require the installation of a third party application to view image files.

Even if you don't have a mobile device, laptop computer, or even access to an Internet kiosk, you can still remain up to date with Unified Messaging. To access Unified Messaging, place a telephone call to the subscriber access number. When you have entered your extension and PIN, you will hear a prompt similar to the following: "Please say voice mail, e-mail, calendar, personal contacts, directory, or personal options." If your answer is e-mail, Unified Messaging will then read the message header, name, subject, time, and priority for messages contained in your Inbox. Finally, Unified Messaging will read the entire message.

Note:
If you would like Unified Messaging to read messages in another folder, you can change the default folder in Microsoft Office Outlook 2007 or Exchange 2007 Outlook Web Access. Unified Messaging can only read messages in one folder.

At any time during the reading of the message, use the voice commands or the telephone keypad to instruct Unified Messaging. Some of the actions you can take while listening to your e-mail messages are: move to the next message, delete the message, delete the conversation, reply to all, rewind, fast forward, or pause. If you need to reply to a message, you can record a .wma file and attach it to your message reply.

If you are on your way to a meeting and realize you are going to be late, you can call Unified Messaging and access your calendar. When Unified Messaging plays your upcoming meeting, say "I'll be late" and then tell Unified Messaging how late you will be. Unified Messaging will send a message to all attendees informing them you will be late.

Exchange Anywhere

Exchange 2007, with Unified Messaging, Exchange ActiveSync, Outlook Web Access, and Outlook Anywhere, can help your employees access all of their messaging data no matter where they are. For the latest information and resources on Exchange 2007, be sure to visit the Exchange Server TechCenter.

sb
November 16, 2007
Choosing Exchange Server 2003 Hardware for Reuse with Exchange Server 2007

Topic Last Modified: 2006-04-18

When selecting hardware for your computers running Microsoft® Exchange Server, there are many things that you must consider. Two of the most critical resources are processor and memory.

This article provides rough guidelines for processor and memory configurations that provide good performance for Exchange Server 2003 while also providing a strong platform for Exchange Server 2007. Recommendations will also be made on how server hardware deployed for Exchange 2003 roles can be reused for Exchange 2007 on a per-server role basis (for example, Mailbox and Client Access server roles). With this in mind, I have tried to make safe or highly confident predictions concerning what processor and memory configurations work well for Exchange 2007 server roles to help administrators maintain current Exchange 2003 environments with an eye toward the future.

Note:
This information is provided with the caveat that Exchange 2007 is still under development and processor and memory metrics may change. This information will be updated as "Best Practices" are defined for Exchange 2007.
var ExpCollDivStr = ExpCollDivStr; ExpCollDivStr = ExpCollDivStr + 'ctl00_LibFrame_ctl0420c0776,'; var ExpCollImgStr = ExpCollImgStr; ExpCollImgStr = ExpCollImgStr + 'ctl00_LibFrame_ctl04img,'; Why are the hardware requirements for computers running Exchange 2007 different from those for previous versions of Exchange (2003)?Why are the hardware requirements for computers running Exchange 2007 different from those for previous versions of Exchange (2003)?
var ExpCollDivStr = ExpCollDivStr; ExpCollDivStr = ExpCollDivStr + 'ctl00_LibFrame_ctl0526742e0,'; var ExpCollImgStr = ExpCollImgStr; ExpCollImgStr = ExpCollImgStr + 'ctl00_LibFrame_ctl05img,'; What processor types should I consider to ensure my server hardware will work with both Exchange 2003 (32-bit) and Exchange 2007(64-bit)?What processor types should I consider to ensure my server hardware will work with both Exchange 2003 (32-bit) and Exchange 2007(64-bit)?

We recommend that you choose a processor that will work with both 32-bit and x64-based versions of Windows 2003. The following server processors support both 32-bit and x64-based versions of Windows 2003, thereby supporting Exchange 2003 deployments today, and Exchange 2007 deployments tomorrow:

  • AMD Opteron
  • Intel Xeon with EM64 Technology
    Note:
    The third-party Web site information in this topic is provided to help you find the technical information you need. The URLs are subject to change without notice.

Each of these vendors also ships x64-capable desktop processors which can also run x64-based versions of Windows 2003 (for example, AMD Athlon64 and Intel Pentium D with EM64T) but for the sake of simplicity, this article will concentrate on processors designed for server deployments.

It is important to note that the Intel Itanium (IA64) processor will not work with Windows 2003 x64-based versions, and thus it will not work for Exchange 2007 deployments. Exchange 2007 is designed to run only on x64-capable processors such as those listed above; Exchange 2007 will not run on Itanium based systems.

Regardless of which server processor you select, it is necessary to have the server product pass the Designed for Windows test suite to ensure Microsoft support. Servers listed on the Windows Server Catalog meet these criteria. If your server is not listed, check with your vendor to see if either the "Designed for Windows" logo testing is in progress, or the server has passed the testing and is pending a Web site update.

The TechNet x64 Newsgroup is a good place to get more information about moving from 32-bit Windows to 64-bit Windows.

var ExpCollDivStr = ExpCollDivStr; ExpCollDivStr = ExpCollDivStr + 'ctl00_LibFrame_ctl12151b64b,'; var ExpCollImgStr = ExpCollImgStr; ExpCollImgStr = ExpCollImgStr + 'ctl00_LibFrame_ctl12img,'; Should I be considering multi-core processors for my Exchange 2003 or Exchange 2007 servers?Should I be considering multi-core processors for my Exchange 2003 or Exchange 2007 servers?

The short answer is yes. Extensive testing on dual-core processors has shown that Exchange benefits from dual-core processor technology. The performance benefit for Exchange from dual-core technology depends upon the specific processor used. The findings from Exchange 2003 dual-core testing have been summarized in Microsoft Knowledge Base article 827281, CPU and memory scalability for Exchange Server 2003 and for Exchange 2000 Server. Additionally, the performance benefit of specific dual-core implementations can be seen by comparing the MMB3 results of a 4-processor, single-core based server to a 2-processor, dual-core based server. These results have been published at the Performance Benchmarks for Computers Running Exchange Server 2003 Web site.

Today, dual-core processors are an attractive option for Exchange 2003 and Exchange 2007 servers based on price and performance. Please ask your server vendor about dual-core benefits for Exchange, specific to a given hardware architecture.

var ExpCollDivStr = ExpCollDivStr; ExpCollDivStr = ExpCollDivStr + 'ctl00_LibFrame_ctl15397d415,'; var ExpCollImgStr = ExpCollImgStr; ExpCollImgStr = ExpCollImgStr + 'ctl00_LibFrame_ctl15img,'; What do I have to know to ensure my x64-capable Exchange 2003 server can be upgraded with more memory when I deploy Exchange 2007?What do I have to know to ensure my x64-capable Exchange 2003 server can be upgraded with more memory when I deploy Exchange 2007?

Exchange 2007 enables much better memory utilization than Exchange 2003 due to its 64-bit architecture. Because of the virtual address space limitations of a 32-bit platform, Exchange 2003 is limited to using 4 GB or less of physical memory. In contrast, Exchange 2007 running on Windows 2003 x64-based versions will efficiently utilize upwards of 16 GB of memory and beyond (Mailbox role). This change needs to be factored in when putting together server hardware for Exchange 2003 that can be migrated to Exchange 2007 server roles. The following factors should be considered:

With this information, it is determined that 2 GB PC2700 or 2 GB PC3200 memory modules will provide a good memory configuration for Exchange 2003 (2x2 GB). Moreover, the server can be upgraded to 16 GB (8x2 GB) to significantly reduce the I/O for an Exchange 2007 Mailbox Server in the future. If 1 GB memory modules were chosen for the Exchange 2003 configuration, the server could not be upgraded to 16 GB without having to throw out the 1 GB memory modules and replace them with 2 GB memory modules. One caveat with this planning method is that some servers experience a performance improvement when more memory slots are filled, while others experience a reduction in performance. Check with your hardware vendor to understand this effect for a given server architecture.

var ExpCollDivStr = ExpCollDivStr; ExpCollDivStr = ExpCollDivStr + 'ctl00_LibFrame_ctl18c107873,'; var ExpCollImgStr = ExpCollImgStr; ExpCollImgStr = ExpCollImgStr + 'ctl00_LibFrame_ctl18img,'; SummarySummary

I hope I have offered some insight on how to choose server hardware for Exchange 2003 that can be used for Exchange 2007 deployments tomorrow. With effective planning and an understanding of the basic processor and memory requirements of both versions, the investments made today in current Exchange 2003 infrastructures can continue to be leveraged with Exchange 2007.

sb
November 16, 2007
Sorry, but the blog post could not be located.
sb
fern


to fern

Recent Posts
Top Posts
Recent Comments
Categories
Archive
Syndication Tools
  • Subscribe to Flixya Blog Feed
  • Ping your RSS Feed
  • Add to Technorati Favorites!