Friday, 27 March 2009

Exchange 2010 Installation Requirement



To run Microsoft Exchange Server 2010 Enterprise Edition Beta on x64 platforms, you need:
·        PC―x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T) or AMD processor that supports the AMD64 platform
·        Operating system―Microsoft Windows Server 2008 Standard x64 Edition or Enterprise x64 Edition
·        Operating system for installing management tools―The 64-bit editions of Microsoft Windows Vista SP1 or later, or Windows Server 2008. Note: Requirements only for management tools installation.
Additional requirements to run Exchange Server 2010 Beta
·        Memory―Minimum of 4 gigabytes (GB) of RAM per server plus 5 megabytes (MB) of RAM recommended for each mailbox
·        Disk space
o   At least 1.2 GB on the drive used for installation
o   An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install
o   200 MB of available disk space on the system drive
·        Drive―DVD-ROM drive, local or network-accessible
·        File format―Disk partitions formatted as NTFS file systems
·        Monitor―Screen resolution 800x600 pixels or higher


Exchange Server 2010 Beta Prerequisites
If these prerequisites are not already installed, the Exchange Server 2010 Beta setup process will prompt and provide links to the installation locations; Internet access is required if the prerequisites are not already installed or available on a local network.
·        Microsoft .NET Framework 3.5
·        Windows PowerShell V2
·        Windows Remote Management


The following is a list of new rights-protected e-mail functionality with Active Directory Rights Management Services (AD RMS) that has been included in Exchange 2010:
  • Transport rules to apply AD RMS protection to messages based on conditions.
  • Persistent protection of attachments in rights-protected messages.
  • Support for AD RMS templates.
  • An Internet confidential AD RMS template for protection over the Internet.
  • AD RMS protection for Unified Messaging voice mail messages.
 

New Transport and Routing Functionality


The following is a list of new transport and routing functionality that has been included in Exchange 2010:
  • Cross-premises mail routing    An organization can choose to outsource some of their mailboxes to a hosted solution while maintaining their on-premises deployment. For example, a university can choose to host the mailboxes for all faculty and staff in their on-premises deployment and use a hosted solution for student mailboxes. Exchange 2010 allows routing of messages between the on-premises and hosted mailboxes.
  • Enhanced disclaimers   Exchange 2010 lets you add disclaimers that can include hyperlinks, images, and HTML-formatted text. You can also insert Active Directory attributes that are substituted for the sender's attributes when a disclaimer rule is triggered.
  • Transport rules integration with AD RMS   Exchange 2010 gives you the ability to create rules that require AD RMS protection based on keywords or patterns.
  • Moderated Transport   Exchange 2010 provides an approval workflow for sending messages to recipients. When you configure a recipient for moderation, all messages sent to that recipient must go through an approval process.
  • Shadow redundancy   Messages that are submitted to an Exchange 2010 Hub Transport server are stored in the transport database until the next hop reports successful delivery of the message. If the next hop doesn't report successful delivery and it fails, the message is resubmitted for delivery.
  • Transport dumpster truncation based on log copy status   When messages that are in the dumpster are replicated to all mailbox databases, they're removed from the dumpster.
  • Latency SLA management   Exchange 2010 Transport lets you measure service levels delivered relative to your service level agreement (SLA) goals. Exchange 2010 gives you the ability to measure latencies for each hop, as well as end-to-end latency.
  • Transport database improvements   Performance improvements in the Transport database result in reduced database I/O per second (IOPS) per message, which increases message throughput.


 New Permissions Functionality


In Exchange 2010, Role Based Access Control (RBAC) has replaced the permissions model that was used in Exchange 2007. RBAC lets you define extremely broad or extremely precise roles and assignments based on the roles of your administrators and users, and the tasks they perform. Access to the cmdlets and parameters required to perform a task is granted by assigning the related RBAC management role to a user or universal security group. If you want to grant an administrator or user the ability to perform tasks in Exchange 2010, you must either add the administrator or user to a universal security group that already has been assigned a specific RBAC role, or you must assign the role directly to the administrator or user.
Note: - How RBAC is implemented, and the management roles that are available to you by default, will likely change in a later release of Exchange 2010.
Note: - The information about permissions and roles provided in procedural and cmdlet reference topics in the Exchange 2010 Help hasn't been updated yet for Exchange 2010. The role names provided in Exchange 2010 may be similar to those in Exchange 2007. However, there are differences in implementation, scope, and management.

 New High Availability Functionality


Exchange 2010 integrates high availability into the core architecture of Microsoft Exchange to enable customers of all sizes and in all segments to economically deploy a messaging continuity service in their organization.
Exchange 2010 combines the key availability and resilience features of cluster continuous replication (CCR) and standby continuous replication (SCR) into a single high availability solution that handles both on-site data replication and off-site data replication. Mailbox servers can be defined as part of a Database Availability Group to provide automatic recovery at the individual mailbox database level instead of at the server level. Each mailbox database can have up to 16 copies.
The following features in Exchange 2007 and Exchange 2007 Service Pack 1 (SP1) no longer exist in Exchange 2010:
  • Local continuous replication (LCR)
  • Single copy clusters (SCC)
In addition to these features, the concept of a clustered mailbox server no longer exists in Exchange 2010.
The following features in Exchange 2007 and Exchange 2007 SP1 no longer exist in Exchange 2010:
  • Local continuous replication (LCR)
  • Single copy clusters (SCC)
  • Clustered mailbox servers

New Features on Exchange 2010 HA Features…

Database Availability Group: A set of Mailbox servers that uses continuous replication to provide automatic recovery from a variety of failures (disk level, server level, datacenter level).
Database-Level Failover: Exchange Server Database Availability Groups provide automatic failover at the database level, without the complexity of traditional clustering. A database-level disruption, such as a disk failure, no longer affects all the users on a server. Because there is no longer a strong tie between databases and servers, it is easy to move between database copies as disks fail. This change, coupled with faster failover times (30 seconds), dramatically improves an organization’s overall uptime.
Improved Site Resiliency: Exchange Server Database Availability Groups makes it easier to implement site resilience by simplifying the process to extend data replication between datacenters to achieve site failover. Log files are also compressed to improve transmission time and reduce network bandwidth usage.
Easier Deployment: Administrators can add high availability to their Exchange environment after their initial deployment, without reinstalling servers. Small organizations can deploy a simple two-server configuration that provides full redundancy of mailbox data along with Client Access and Hub Transport roles. These changes put high availability within the reach of organizations that once considered it impractical.
Integrated Cluster Administration: Exchange Server Database Availability Groups feature automatic failover without the complexity of traditional clustering. The proven capabilities of Windows clustering are integrated with Exchange and are transparent to the administrator. Administrators no longer need to master clustering concepts or deal with separate administration tools in order to provide enterprise-class uptime.
Backup-less Support: The Exchange Server Database Availability Group architecture allows log file replay to be lagged, enabling administrators to perform point-in-time database restores without the need for tapes. Organizations can rely on their high availability infrastructure rather than tape backups to recover from failures, and substantially decrease their operating costs.
Transport Resiliency: Transport servers in Exchange Server 2010 feature built-in protection against the loss of message queues due to disk or server failure. Servers retain a "shadow" copy of each mail item after it is delivered to the next hop inside the organization. If the subsequent hop fails before reporting successful delivery, the message is resubmitted through a different route.
Online Mailbox Moves:  Administrators can move mailboxes between databases without taking users offline. Users can connect to their mailboxes, sending and receiving mail, while the move is taking place.  This gives administrators the flexibility to perform system maintenance during business hours instead of during the night or weekends.

Exchange 2010 has been re-engineered around the concept of continuous availability, in which the architecture has changed so that automatic failover protection is now provided at the individual mailbox database level instead of at the server level. In Exchange 2010, this is known as database mobility. The continuous availability architecture built into Exchange 2010 provides new benefits for organizations and their messaging administrators:
  • Multiple server roles can co-exist on servers that provide high availability. This enables small organizations to deploy a two-server configuration provides full redundancy of mailbox data, while also providing redundant Client Access and Hub Transport services.
  • An administrator no longer needs to build a failover cluster in order to achieve high availability. Failover clusters are now created by Exchange 2010 in a way that is invisible to the administrator. Unlike previous versions of Exchange clusters which used an Exchange-provided cluster resource DLL named ExRes.dll, Exchange 2010 no longer needs or uses a cluster resource DLL. Exchange 2010 uses only a small portion of the failover cluster components, namely, its heartbeat capabilities and the cluster database, in order to provide database mobility.
  • Administrators can add high availability to their Exchange 2010 environment after Exchange has been deployed, without having to uninstall Exchange and then re-deploy in a highly availability configuration.
  • Exchange 2010 provides a view of the event stream that combines the events from the operating system with the events from Exchange.
  • Because storage group objects no longer exist in Exchange 2010, and because mailbox databases are portable across all Exchange 2010 Mailbox servers, it is very easy to move databases when needed.

Incremental Reseed version 2

  • After an automatic failover for all of the configured copies of a database
  • When a new copy is enabled and some database and log files already exist at the copy location
  • When replication is resumed following a suspension or restarting of the Microsoft Exchange Replication service.

Backup-less Exchange Organization

·        There are several changes to the core architecture of Exchange 2010 that have a direct effect on the backup or restore of Exchange databases. One significant change is the removal of storage groups. In Exchange 2010, each database is associated with a single log stream, represented by a series of 1 megabyte (MB) log files. Each server can host a maximum of 50 databases.
·        Another significant change for Exchange 2010 is that databases are no longer closely tied to a specific Mailbox server. Database Mobility expands the system's use of continuous replication by replicating a database to multiple, different servers. This provides better protection of the database and increased availability. In the case of failures, the other servers that have copies of the database can mount the database.
·        Because you can have multiple copies of a database hosted on multiple servers, you can effectively have backup-less Exchange organization

Changes to Continuous Replication from Exchange Server 2007


The underlying continuous replication technology previously found in CCR and SCR remains in Exchange 2010, and it has been further evolved to support new high availability features such as database copies, database mobility, and database availability groups. Some of these new architectural changes are briefly described below:
  • Because storage groups have been removed from Exchange 2010, continuous replication now operates at the database level. Exchange 2010 still uses an Extensible Storage Engine (ESE) database that produces transaction logs which are replicated to one or more other locations and replayed into one or more copies of a mailbox database.
  • Log shipping and seeding no longer uses Server Message Block (SMB) for data transfer. Exchange 2010 continuous replication uses a single administrator-defined TCP port for data transfer. In addition, Exchange 2010 includes built-in options for network encryption and compression for the data stream.
  • Database copies are for mailbox databases only. For redundancy and high availability of public folder databases, we recommend that you use public folder replication. Unlike CCR, where multiple copies of a public folder database could not exist in the same cluster, you can use public folder replication to replicate public folder databases between servers in a DAG.
Several concepts used in Exchange 2007 continuous replication also remain in Exchange 2010. These include the concepts of failover managementdivergence, the use of the auto database mount dial, and the use of public and private networks.

 

DAG (Database Availability Group) Overview

The new concept of the Database Availability Group (DAG) is exciting Exchange 2010 technology to bring low cost high availability without costly hardware SAN infrastructure.
 
Microsoft Exchange Server 2010 clients will connect to Client Access Servers, which will proxy the requests to the client.  No more LCR, SCR, or CCR…DAG (or Super CCR) uses low cost DAS storage to leverage a “Raid 5” striping of databases to multiple servers.  Client Access Servers (set in load balanced server farms), will provide primary HTTP and a new “distributed RPC endpoint” for Office 2010, Office 2007, Office 2003 emulation of a “standard exchange mailbox server” without needing to upgrade the clients.
Since clients connect to the CAS servers to proxy requests to the mailbox servers, failover from mailbox server to another in the DAG happen in less than 30 seconds in a failover or move command.
Some other notable highlights in Exchange 2010 database and HA architecture:
  • Replication between databases will change from being a RPC method, to a TCP socket method which will increase performance on heavily loaded servers.  
  • Replication can be locally or remote (cross-subnet).  You will need CAS servers at the DR site however if you lose the primary datacenter.
  • You can have to 16 mailbox servers in a DAG.
  • There will be no integration with Microsoft Online at the DAG level.   Microsoft Online cannot be used as DR site for a on-premise hosted mailbox.  Either it’s on-premise or hosted, not a mixture of the two.
  • You still Windows Server 2008 Enterprise, as failover clustering feature is required.
  • The concepts of Storage groups are a depreciated.
  • Jet is still the storage engine for Exchange 2010 databases.
  • Exchange IO has been reduced 50% from 2007 to 2010 (and already a 70% IO reduction from Exchange 2003 to 2007).
  • Single Instance Storage is going away, as well as the per database table.  A new table is created for each mailbox, creating the scenario for 10,000+ messages in mailboxes due to the sequential read capability. 
  • Server based PST files allows archiving with anywhere access. Helps for e-discovery, OWA searches, and compliance management.
Public folders are not covered by the new DAG changes, and the only way to replicate Public Folders in Exchange 2010 is using the same 10 year old Public folder replication methods we have used for years.  SCR replication of the public folder database for DR scenarios, possible in Exchange 2007, is depreciated in Exchange 2010.  Also, clients will continue to connect to public folder on mailbox servers in the DAG directly.  Public Folders will not take part in the new Client Access Server 2010 model that is introduced with Exchange 2010 mailbox databases. Public folders are a legacy platform and significant changes won’t be introduced.

New Messaging Policy and Compliance Features

Exchange 2010 compliance features make retention independent of users' mailbox management and filing habits, and these features ensure retention policies are applied continuously. The following is a list of new messaging and compliance features that have been included in Exchange 2010:
  • New interface for applying retention policies
  • Auto tagging for retention policies
  • Mailbox search features for cross-mailbox search with Advanced Query Syntax (AQS) support
  • New transport rules predicates and actions

Messaging Records Management


·        Messaging Records Management allows organizations to implement message retention policies. Exchange 2010's new MRM feature allows you to granularly apply retention policies, without impacting users' e-mail filing methods. 
·        Exchange Server 2007 addressed retention needs with Managed Folders. Managed Folders allow administrators to specify Managed Content Settings for for mailbox folders, relying on users to move items to appropriate folders, based on retention settings of such folders.
·        Exchange 2010 uses a combination of Retention Tags, Retention Policies, and AutoTagging

Discovery


Exchange 2010 Discovery allows a user with delegated Discovery Management role to search mailbox content in selected mailboxes across the entire Exchange 2010 organization. Messages returned by the search are copied to a folder in the specified mailbox. Discovery allows legal and IT departments to easily comply with legal discovery requirements, or search message content for purposes such as internal investigations, and messaging policy compliance. The new Discovery Management role can be assigned to a user or a security group to perform Discovery-related tasks. An easy-to-use browser-based interface accessible from the Exchange Control Panel (ECP) allows non-technical professionals to easily perform Discovery functions.

 New Outlook Web Access Features

The following is a list of new features in Outlook Web Access in Exchange 2010:
  • Favorites in the Navigation Pane
  • Search folders
  • Message filtering
  • The ability to set categories in the message list
  • Options in the Web management interface for Outlook Web Access
  • A side-by-side view for calendars
  • Multi-client language support
  • The ability to attach messages to messages
  • Expanded right-click capabilities
  • Integration with Office Communicator, including presence, chat, and a contact list
  • Conversation view
  • The ability to send and receive text (SMS) messages from Outlook Web Access
  • Outlook Web Access mailbox policies

 New Unified Messaging Features

The following is a list of new Unified Messaging features that have been included in Exchange 2010:
  • Personal auto attendants (call answering rules)
  • Additional language support including in Outlook Voice Access and Voice Mail Preview
  • Enhancements to name lookup from caller ID
  • Voice Mail Preview
  • Messaging Waiting Indicator
  • Missed call and voice mail notifications using text messaging (SMS)
  • Protected Voice Mail
  • Built-in Unified Messaging administrative roles
For more information about the new Unified Messaging functionality and new voice mail features.

Functional Descriptions
Voice Mail Preview: Exchange Server 2010 will facilitate the cumbersome task of navigating through voice messages. With Exchange Server 2010 speech-to-text translation, the user can read the contents of the audio recording in the same fashion they would read an e-mail. Furthermore, if the resulting voice messages are opened using Microsoft Office Outlook 2010, the text of the voice mail preview will become "actionable". Recognized names, contacts, and phone numbers will all be identified with icons that the user can select to add contacts, call using Office Communicator, or send e-mail. To facilitate navigation of the audio, clicking in the text will cause the voice mail to jump to that word and continue playing.
Protected Voice Mail: Exchange Server 2010 solves the problem of unauthorized distribution of the messages by securing the message content, specifying the users who may access that content, and the operations that they may perform on it. It uses Active Directory Rights Management Services to apply Do Not Forward permissions to voice messages that are designated either by the sender (by marking the message as private) or by administrative policy. This prevents the forwarding of protected voice mails in a playable form to unauthorized persons, whatever the mail client used.
Message Waiting Indicator (MWI): Now with Unified Messaging, users are notified of the presence of new/unread voice mail by lighting the lamp and providing a count on their supported desk phone. Additionally, users can configure their text messaging notification account to receive the beginning content of the voice mail preview in the SMS.
Auto Attendant: Users are often looking for a person in an organization, but are unsure of the extension or exact phone information. Exchange Unified Messaging's Auto Attendant enables users to easily navigate to the person they are trying to reach when calling an organization with either the telephone keypad or speech inputs to navigate the menu structure, place a call to a user, or locate a user and then place a call to that user. An auto attendant gives you the ability to:
·        Create a customizable set of menus for callers
·        Define informational greetings, business hours greetings, non-business hours greetings, and holiday schedules
·        Describe how to search the organization's directory and connect to a user's extension
·        Enable external users to call the operator
Call Answering Rules: Unified Messaging enables users to have more control over their call flows. For a salesman, this could mean the difference between sending an important sales lead to his voice mail instead of finding him on his cell phone or home phone. Call Answering Rules present callers with custom greetings, Find-Me, and call transfer options, in addition to leaving a voice mail. Moreover, these rules can be preceded by conditions (such as caller-IDs, time-of -day and Exchange free/busy status), giving end-users greater control over how they can be reached over the phone.
Outlook Voice Access: Users now have control over their Inbox with Outlook Voice Access via a telephone keypad or voice inputs. This enables anywhere access to their mailbox when a user is away from a computer or Internet-connected device. Now users no longer have need to worry about being late for appointments or being disconnected when traveling, as they can instantly call into their mailbox to manage their calendar, contacts, and e-mail.
Enhanced Caller ID: Users can get more context and information about their callers with Enhanced Caller ID.  Callers are often not a part of a user contact list or organization's directory.  For these cases, Windows Live Search will be used to try and determine the calling party.  If a match is found, the result will be placed on the calling line of the message to better inform the user where the call came from.
Language Support: More users can now listen to and interact with their e-mail and voice mail in their native language or dialect. Exchange Server 2010 offers a broad range of language support with support for 16 languages including three varieties of English, plus Mandarin, Cantonese, European and North American versions of Spanish and French, and several other European languages.

 Web Management Interface

The following is a list of the features available in the new Web management interface for Exchange 2010:
  • Text messaging (SMS) integration
  • Voice messaging integration
  • Mailbox Search
  • Distribution list creation and management
  • Moderation and approval for distribution list submission
 

New Exchange Core Store Functionality

The following is a list of core store functionality that is included or has been changed in Exchange 2010:
  • Storage groups are deprecated.
  • Mailbox databases are no longer connected to the server object.
  • Extensible Storage Engine (ESE) has many improvements for high availability, performance, and database mobility.
  • The Store schema has been flattened.

 

Database Management

Databases are no longer associated with storage groups. In Exchange 2010, storage group functionality has been moved to the database.
In Exchange 2010, you can manage mailbox and public folder databases in the Organization Configuration node of the EMC. In Exchange 2007, database management was performed in the Server Configuration node.
Note: -Although public folder database management has been moved from the Server Configuration node to the Organization Configuration node with the mailbox databases, the functionality of public folder databases hasn't changed in Exchange 2010. Just like in Exchange 2007, you can't create database copies of public folder databases, and you can't add public folder databases to a database availability group. Public folders still use public folder replication.

 New Administration Functionality in the Exchange Management Console

The core EMC refers to new functionality that affects how you use the Exchange Management Console, not how you use specific features. The following is a list of the new core Exchange Management Console (EMC) features that have been included in Exchange 2010:
  • Customer Experience Improvement Program (CEIP)
  • Organizational Health
  • Community and Resources
  • Command logging
  • Property dialog command exposure

Feature Changes


This section briefly describes the new features that have been added to EMC.

Organization Configuration node

Database management has moved from the Server Configuration node to the Organization Configuration node. In addition, the following wizards have been added to the node:
  • Manage Federated Organization Identifier wizard
  • New Federation Trust wizard
  • New Sharing Relationship wizard
  • New Sharing Policy wizard
  • Outlook Web Access Mailbox Policy wizard

Server Configuration node

Manage Diagnostic Logging Properties wizard

Recipient Configuration node

  • Send Mail   you can now send mail to a recipient from EMC. You will need to setup an e-mail account on the computer from which you are sending mail before you can send mail.
  • Resource Scheduling   Configuring calendaring and scheduling for resources has been added to the Recipient properties dialog box. For more information.

 New Administration Functionality in the Exchange Management Shell

The following is a list of features available in the new Exchange Management Shell:
  • Remote administration   With the new Shell, you can connect to remote Exchange 2010 servers across the network with only Windows Power Shell V2 CTP3 and Windows Remote Management 2.0 CTP installed.
  • Administrator audit logging   Actions that result in the modification of Exchange organization configuration and other object properties in the Exchange Management Console, the Web management interface, and the Shell can now be logged for later review. For more information.

Archiving and Retention New Features


Personal Archive: is an additional mailbox associated with a user's primary mailbox.  It appears alongside the primary mailbox folders in Outlook. In this way, the user has direct access to e-mail within the archive just as they would their primary mailbox. Users can drag and drop PST files into the Personal Archive, for easier online access – and more efficient discovery by the organization. Mail items from the primary archive can also be offloaded to the Personal Archive automatically, using Retention Polices, reducing the size and improving the performance of the primary mailbox. In addition, users can search both their Personal Archive and primary mailbox simultaneously using Outlook.
Retention policies: enable application of retention settings to specific items or folders in a mailbox. Policies are configured by the Exchange Administrator and are displayed inside each e-mail, along with a header stating the applied policy and delete date. These headers make it easier for the end user to identify when an e-mail is set for expiration and apply a new expiration policy if the e-mail needs to be retained for a longer period. Administrators can set also default policy that can move messages from the primary mailbox to the Archive automatically.
Multi-Mailbox Search: enables multi-mailbox searches of mailbox items, including e-mail, attachments, calendar items, tasks and contacts as well as IRM-protected files.  Multi-mailbox search works simultaneously across both primary mailboxes and Personal Archives with an easy-to-use control panel. This enables authorized HR, legal, and compliance users to perform searches without reliance on IT. For legal discovery purposes, mail located through search can be copied and moved to a specified mailbox or external store, as defined by the administrator for further investigation. Advanced filtering capabilities include: sender, receiver, expiry policy, message size, sent/receive date, cc/bcc, and regular expressions.
Legal Hold: enables immediate preservation of a user’s deleted and edited mailbox items (e-mail, appointments, tasks, etc.) from both their primary mailbox and Personal Archive. Litigation Hold can be set on individual mailboxes or across the enterprise and also includes an option that automatically alerts users that a hold has been placed on their mailbox.

Information Protection and Control

Transport Protection Rules: when used with Active Directory Rights Management Services (AD RMS), transport protection rules enable an administrator to automatically apply Information Rights Management (IRM) protection to e-mail (including Office and XPS attachments) after a message is sent. This provides persistent protection to the file no matter where it is sent and prevents forwarding, copying, or printing depending on the set of AD RMS Policy Templates available from the AD RMS deployment. Voicemail can also be protected to prevent forwarding to unauthorized persons.
Support for IRM in Outlook Web Access (OWA): enables users to read and create IRM-protected messages natively, just like in Outlook. IRM-protected messages in OWA can be accessed through Windows Internet Explorer, Firefox, and Safari (no plug-in required) and includes full-text search, conversation view, and preview pane.
Outlook Protection Rules: automatically trigger Outlook to apply an RMS template based on sender or recipient identities, before it is sent. Since the messages are protected at the desktop before being sent out to Exchange, this feature allows an organization to block 3rd party service providers or onsite Exchange administrators from viewing sensitive content that is sent between employees.
Transport Decryption: enables access to IRM-protected messages by Transport Agents to perform actions such as content filtering, applying signatures via transport rules, as well as anti-spam and anti-virus scanning. Transport Decryption can also be used with journaling to ensure that journal reports sent to journal mailboxes or 3rd party archiving products will contain a decrypted (clear-text) copy of IRM-protected messages, including and Office and XPS attachments. This allows for indexing and searching of IRM-protected messages for legal discovery and regulatory purposes.
Dynamic Signatures: automatically apply a signature to the bottom of an e-mail based on sender’s Active Directory (AD) attributes. This feature can also be configured to apply rich, HTML signatures with specific fonts, company logos, and more.
Expanded Transport Rule Conditions: enable you to moderate, IRM-encrypt, sign, and block e-mail based on more granular conditions such as the actual contents within an Office attachment, a user's Active Directory attributes (e.g. department, country, manager), and multiple message types (such as auto-replies, calendaring, etc.).
MailTips: alert the sender of an e-mail as to certain conditions that may result in policy violations or risk of unintended delivery. For example, MailTips will generate an alert message within an e-mail if: sender is about to reply-all or mail to a large group or external recipient. MailTips is available in both OWA and Outlook 14.
Moderation: re-directs mail to a manager or trusted moderator for review. The reviewer can then approve or block the message and if blocked, provide an explanation back to sender.

Mobile Devices New Features


IT administrators can control the devices that connect to their network though a block/allow list. This list ensures that only approved devices are connecting to the messaging data while still offering a wide array of Exchange ActiveSync® enabled devices.
The best part of mobile access in Exchange Server 2010 is that it is all built into Exchange. There is no need to buy extra servers and client access licenses (CALs) from third-party providers or manage another, separate system for mobile access.
Conversation View:  the new conversation view quickly and easily enables users to identify the most recent messages and, the series of responses. Conversation view is always preserved, even if individual e-mail messages are located in different folders in the mailbox.  By treating multiple messages as a single conversation it can be managed, ignored, moved, and deleted as a whole vs. having to address each e-mail individually. New messages to old conversations will automatically be placed in the folder to which you have directed the conversation, even if you have deleted or ignored a conversation.
Free/Busy Lookup: Exchange ActiveSync now enables users to look at a contact's calendar availability. Right from a user's contact information, a free/busy timeline show users when their contacts are available for a call or meeting.
Nickname Cache: By storing the e-mail addresses of recent recipients, the Nickname Cache helps users address e-mail more quickly by providing a suggested name list as a new address is typed. This automatically populated list narrows itself as the user types more letters of the recipient's name and is a combined cache of recent recipients of e-mail sent from Outlook Web Access and Outlook Mobile.
SMS Sync: Exchange ActiveSync now provides the ability to send and receive SMS text messages from Outlook and Outlook Web Access. Incoming messages, sent via EAS to the user's mobile device, can be seen both in the usual SMS message location and the e-mail inbox.
Reply State: The icon update helps answer the question, "Did I handle that e-mail yet?" Now you can see if you replied to or forwarded an e-mail just by looking at the icon on the device, even if you replied from Outlook.
Installable client:  Upgrading your e-mail functionality no longer requires you to update your phones. All the latest features of Exchange Server are available to any mobile device that has Windows Mobile 6.1 or later. Users of Exchange Server can download an update to Outlook Mobile so that their existing devices can take advantage of all the benefits in the latest version of Exchange ActiveSync.

Storage New Features

The improvements made to Exchange Server 2010 storage add new options to the menu of Exchange storage choices, including the use of Serial Advanced Technology Attachment (SATA) hard disk drives and Redundant Array of Inexpensive Disks (RAID)-less configurations. Whether administrators choose SAN, direct attached, or JBOD storage, Exchange helps them provide larger mailboxes at lower cost without sacrificing system availability.
IO Reductions: Exchange 2010 delivers up to a 50% reduction in disk IO from Exchange 2007 levels.  This means that more disks meet the minimum performance required to run Exchange, driving down storage costs.
Optimizations for SATA Disks: IO patterns are optimized so that disk writes do not come in bursts. This removes a barrier that had previously limited the use of Serial Advanced Technology Attachment (SATA) desktop class hard disk drives disks.
Automatic Page Patching: Exchange Server 2010 is more resilient to storage problems. When corruption is caused by minor disk faults, Exchange automatically repairs the affected database pages using one of the database copies configured for high availability. Automatic detection and repair of data corruptions from minor disk errors means that you can take advantage of lower-cost storage options while maintaining system reliability.
JBOD Support: Exchange 2010 can be deployed with up to 16 replicated copies of each mailbox database, and fast database-level failover makes it possible for administrators to swap failed drives with minimal impact to users. This application-level redundancy allows RAID-less (JBOD) storage configurations to be used, resulting in dramatic cost savings.

Top 10 reason to upgrade with Exchange 2007 to Exchange 2010

1.   Solution Deployment Flexibility and Choice
Exchange Server 2010 offers new, flexible deployment options, which allows you to deliver powerful productivity tools to your users, in a way that best fits your business or technology needs.
2.   Simplified High Availability and Disaster Recovery
Exchange Server 2010 introduces a simplified approach to high availability and disaster recovery, to help you achieve new levels of reliability and reduce the complexity of delivering business continuity.
3.   Ease Administration and Lower Help Desk Dependency
Exchange Server 2010 provides new self-service capabilities to help users perform common tasks without calling help desk.
4.   Greater Mobility and Flexible Access
Exchange Server 2010 offers an enhanced universal inbox experience, which provides your users with access to all of their business communications from a single location.
5.   Ease Inbox Overload and Increase Productivity
Exchange Server 2010 adds new productivity features which help your users organize and prioritize the communications in their inboxes efficiently.
6.   Transform Traditional Voice Mail
With Exchange Server 2010, users can receive their voice mail messages in their inbox with text preview.
7.   Achieve and Maintain Compliance
Exchange Server 2010 delivers new integrated archiving functionality to help simplify compliance and discovery.
8.   Safeguards for Sensitive Information
With centrally managed and enforced information protection and control capabilities, Exchange Server 2010 makes it easy to encrypt, control and moderate your company's communications.
9.   Reduced Risk of Malware and Spam
Exchange Server 2010 actively helps protect your communications through built-in defenses against viruses and junk e-mail, and support for an array of third party security products.

New Mailbox and Recipient Functionality


·        Calendaring
Users can share information such calendar free/busy and contacts with users who reside in a different organization.
·        Resource Scheduling
You can now manage resource scheduling in the EMC by editing the resource mailbox's properties
·        Moving Mailboxes
You can now move a mailbox while the end user is still accessing it.
·        Bulk Recipient Management in the EMC
In Exchange 2007 SP1, you could perform bulk recipient management to move, remove, and disable or enable mailboxes in the EMC.
·        Send Mail
You can send mail to recipients from the EMC. Select the recipient in the result pane, and then click Send Mail in the action pane. You must configure an e-mail account setup on the computer from which you are sending mail.
·        Mailbox Folder Permission Management
You can manage folder-level permissions for all folders within a user's mailbox. Sharing mailbox folders and calendar folders is managed through a new set of cmdlets. These cmdlets allow you to view, remove, and add permissions for specific users on all designated mailbox folders.
Another great feature in the Exchange 2010 Management Console is that you now can do cross-forest mailbox moves using the new “New Move Request” wizard. To launch this wizard right-click a User Mailbox in the EMC.

Installation of Exchange Server 2010 Beta Installation


Introduction                                                                             

Most of Exchange Administrator was waiting for this product to make their hand dirty and finally we got 
Exchange Server 2010 Beta available for download. The released version is beta version which can be installed only on 64bit. 32-Bit is still on the pipeline for testing purpose, no clue when it will released on public website.

This Exchange 2010 is simply amazing one, as compare to Exchange 2007 technology lots of changes can be seen on the features and functionalities. We will be posting soon on the changes made in Exchange 2010 as compare Exchange 2007.

As a start-up we would like to share out the basic installation of Exchange 2010 like pre-requisites and guidelines on the installation of Exchange 2010.
Installation of Exchange 2010 Beta

Installation of Exchange 2010 is not making any difference when we are comparing with Exchange 2007, it is still the same method. The only thing got changed is technology support version which needs to be suited for Exchange 2010.

Whenever we are thinking of Exchange 2010\ Exchange 2007 installation there are two major places which we need to focus – first one is Active Directory Preparation and second one is Local Server Preparation.

  • Schema Master: Windows Server 2003 either standard or enterprise edition, recommendation have “window server 2003 with sp2”, this can be either 32-bit or 64-bit.
  • Global Catalog Master: Windows Server 2003 either standard or enterprise edition, recommendation have “window server 2003 with sp2” this can be either 32-bit or 64-bit.
  • The Active Directory domain  & forest functional level must be Windows Server 2003-native or higher for all domains in the Active Directory forest where you will install Exchange 2010.
  • Upgrade Schema - /prepareschema
  • Exchange Security Groups & Permission : /PrepareAD
  • LegacyExchange Support : /PrepareLegacyExchangePermissions
Existing Exchange 2003 in the Domain:

If you have exchange 2003 in the organization then ensure that:
  • Exchange 2003 has Service Pack 2 Installed
  • It should be in the native mode.
Note: Exchange 2010 Beta Upgrade – If you want to upgrade from Exchange 2007, you can’t go with in-place upgrade, and one more thing there is no direct transition from Exchange 2007 to Exchange 2010 Beta. You need to create separate AD Site for Exchange 2010, Exchange 2007 co-existence transition will be supported after the release of Exchange 2007 sp2.


Hardware Requirement:

  • Processor : Intel 64-bit Processor\ AMD64 Processor (Production)
  • Processor supported for 32-bit : Intel Pentium or compatible 800-megahertz (MHz) or faster 32-bit processor
  • Memory: Depends upon the actual requirement minimum 2 GB plus 2\3.5\4 MB per mailbox and can be support upto 64 GB.
  • Mailbox server memory recommendations            
User Type 
 Mailbox server memory recommendation
 Light
 2 GB plus 2 MB per mailbox
 Average
 2 GB plus 3.5 MB per mailbox
 Heavy
 2 GB plus 4 MB per mailbox
Source: Microsoft
  • Disk Space : 1.2 GB free for the drive where we are installing the Exchange, 500 MB more space if we are installing UM, 200 MB free on the system drive and 500 MB free space for Transport Server role
  • Drive : DVD-Rom or Network Access
  • Software:
    Operating System: Windows Server 2008 Standard or Enterprise or just to install the console Vista is supported.
  • Other Software Requirement: there many other software required and actually it depends upon which roles you are installing and based on that you can select the required one. 
My requirement is very simple, clean installation of Exchange 2010 on windows server 2008 where I will install all the Exchange Server roles except Edge Transport Server Role.

Raising The Domain & Forest Functional Level

  • Raising the Domain Function level & Forest Functional Level  to Windows Server 2003:
    • Log into to the windows server 2003 domain controller => Administrative Tools => Active Directory Domain and Trusts => Right click the domain name and select “Raise Domain Functional Level” and raise it to “Windows Server 2003”
  •  Forest Functional Level : Right click “Active Directory Domain and Trusts and select “Raise Forest Functional Level”  as Windows Server 2003
Windows 2008 Server – Level Configuration

1) Install IIS 7.0 : In order to do this, open Server Manager Console => Roles => Add Roles and select “Web Server (IIS)”



Under Role Services Windows select the following component:
  • Basic Authentication
  • Windows Authentication
  • Digest Authentication
  • Dynamic Content Compression
  • .net extensisbility


2) Remote Server Administration Tools pack : It is a feature included with Windows Server 2008. You can install the Remote Server Administration Tools pack by using either the Add Features Wizard in Windows Server 2008, or by using a command line to install the feature.
Command prompt: ServerManagerCmd -i RSAT-ADDS
From GUI:
  • Open the Server Manager Console
  • Click on Features and  then  Add Features and select Remote Server Administration Tools
  • It will ask you to install IIS6 Management Compatibility also select “Add Required Role Service and then click on NEXT


3) Install HTTP Activation:
  • Open the server manager console
  • Features =>  Add Features
  • Expand .Net Framework 3.0 Features
  • Expand WCF activation and Select “HTTP Activation”


4) For Unified Messaging Role we need to have "Windows Media Audio Voice Codec" and "windows Media Encoder" this can be installed by installing Desktop-Experience Component via server manager
  • Open the server manager console
  • Features =>  Add Features
  • Select Desktop Experience


OR else you can execute the installation of Server Manager Role and Features from the command prompt by running below command:
For Client Access Server Role:
ServerManagerCmd -i RSAT-ADDS
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
ServerManagerCmd -i NET-HTTP-Activation
ServerManagerCmd -I RPC-over-HTTP-proxy


For Hub  Transport Server Role:
ServerManagerCmd -i RSAT-ADDS
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Windows-Auth



For Mailbox Server Role:
ServerManagerCmd -i RSAT-ADDS
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Failover-Clustering (for Clustering)


For Unified Messaging Server Role:
ServerManagerCmd -i RSAT-ADDS
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Desktop-Experience






For Edge Transport Server Role
ServerManagerCmd -i ADLDS
Run Exchange 2010 setup


Click on Step 4: Install Microsoft Exchange

12) Next Screen will be Introduction page, click on NEXT




 13) Now you will get "Language File Location" in which you can download the other languages apart from English and size of the package will be 200 MB. By default I had choosed the "English"




14) Next Screen will be "Language Pack Confirmation" - Click on Next


 
 15)  EULA - Select "I Agree"  and Click on Next

16) Error Reporting : It is upto you how you to set the option and click on NEXT

17) Installation Type : Select either Typical or Customize Option based on the required role to be installed, i have selected customized options


Note : The path of the Exchange Database "C:\Program Files\Microsoft\Exchange Server\V14"

18) Server Role Selection : Depends upon your requirement, I had selected Mailbox, Clien Access, Hub Transport & Unified Messaging



19) Organization : If you have not ran /PrepareAd and you are running the setup from GUI it will ask you to provide Organization Name



20) Customer Experience Improvement Program : You can select either "Join" or "I don't Want to Join"

21) Readiness Check:  In this step, Exchange 2010 will check will the required pre-requisite has been met or not like you have required schema master server, global catalog server, domain controller, schema is updated or not, domain functional level setting, all the software have been installed on this specific serve or not, in other words it will do a readiness check on the Active Directory requirement part and Server Level Requirement Part.



22) Click on Install as per the above figure: It will install Exchange Server Roles and then take a reboot of the server.



Let's take a look on the Exchange 2010 Options under program files:


If you see the above screen, there is two power shell command I) Exchange Management Shell & ii) Exchange Management Shell (Local Powershell).

Console View:
Some of the new changes (marked one) - This is just a glance view


You can see that database is in the organization level, under recipient configuration we have "mailbox migration"






DAG (Database Availability Group)


So now it’s time to forget everything that I just mentioned previously in this article about Exchange clustering.
What has been removed?
  1. No more EVS/CMS
  2. Database is no longer associated to a Server but is an Org Level resource
  3. There is no longer a requirement to choose Cluster or Non Cluster at installation, an Exchange 2010 server can move in and out of a DAG as needed
  4. The limitation of only hosting the mailbox role on a clustered Exchange server
  5. Storage Groups have been removed from Exchange
Is anything the same?
1. Window Enterprise Edition is still required since a DAG still uses pieces of Windows Failover Clustering
What’s New?
 1. Other roles can be install on the mailbox server when it is a member of a DAG
2. A database name must be unique in the Exchange Org

 Let’s walk through the installation of Exchange 2010 and then setup our DAG

1. Open EMC -> Expand Organization components and select the database availability group tab

2. Right click and select New Database Availability Group

3.  We are now ask to fill in 3 pieces of information for our DAG
a. DAG name
b. FileShare witness (fsw) UNC path (can be any machine)
c.  phycial location on the server that will host the fsw

You can see I am using my DC in the lab for the fsw machine, note that whatever machine you are using as the fsw needs to have the Exchange Trusted Subsystem group in the local Admins group
4.  Click Finish on the completion page

We have now created our first DAG; if we open active directory users and computers we will see a computer objects gets created with the DAG name we supplied

This object is used by Windows clustering
After the wizard completes we can verify in EMC that our DAG was created as well

by itself the DAG does not do anything for us and there are no properties to manage in EMC, however if we use the shell we can see a few additional properties like:
NetworkCompression                 : InterSubnetOnly
NetworkEncryption                  : InterSubnetOnly
[PS] C:\>Get-DatabaseAvailabilityGroup | fl

Name                               : LABDAG
Servers                            : {E14-EX1}
FileShareWitnessShare              : \\E14-DC1\GENIEFSW
FileShareWitnessDirectory          : C:\GENIEFSW
AlternateFileShareWitnessShare     :
AlternateFileShareWitnessDirectory :
NetworkCompression                 : InterSubnetOnly
NetworkEncryption                  : InterSubnetOnly
DatacenterActivationMode           : Off
StoppedMailboxServers              : {}
StartedMailboxServers              : {}
OperationalServers                 :
ControllingActiveManager           :
ReplicationPort                    : 0
NetworkNames                       : {}
AdminDisplayName                   :
ExchangeVersion                    : 0.10 (14.0.100.0)
Identity                           : LABDAG
WhenChanged                        : 4/17/2009 7:22:42 PM
WhenCreated                        : 4/17/2009 7:22:42 PM
OrganizationId                     :
OriginatingServer                  : E14-DC1.ExchangeGenie.Local
IsValid                            : True
Let’s add our first node to the DAG
1. In EMC right click our DAG and select manage database availability group

2.  On the manage database availability group page click the Add button

3. In the select mailbox server window select the appropriate mailbox server in my case its e14-ex1

4.  Click Manage

after selecting manage Windows clustering is installed at this time

5. Click finish on the completion page

6. We can now see that E14-ex1 was added to the DAG


If we open our Admin tools we will see the Windows clustering is installed and that E14-ex1 is a member of the cluster

note: by default the DAG is set to use DHCP to assign and address to it, in the current build there is no way to assign an IP to the DAG in gui. This can be done when adding a node to the DAG from EMS.
Let see what it looks like to add the server from EMS
1. Open EMS (use the local shell currently) add-databaseavailabilitygroupserver LABDag -mailboxserver E14-ex1 -databaseavailabilitygroupIpAddress 192.168.11.60

Let open Windows Failover Clustering and see that the IP is assigned to the cluster.
 
Another item you will notice that is different from previous versions of Exchange is there are not clustered resources, no disks, not CMS/EVS.
The DAG only users Windows Clustering for hear beat and quorum the new Active Manager is used to manage the DAG failover.
We have currently created a DAG with only 1 Exchange server which does not do us any good as DAG nodes can only replicate to another server, so we will need to add another node.

Shadow Redundancy Mail Flow Scenarios

The shadow redundancy feature in Exchange 2010 provides redundancy for messages for the entire time they are in transit. The general message flow is explained in Understanding Shadow Redundancy. This document explains in detail what happens for each specific message flow scenario that can involve Exchange.
 Mail Flow Scenarios
The following figure shows each possible redundancy scenario in an Exchange organization and how message redundancy is achieved in each scenario. The shaded area shows where shadow redundancy is in effect. Exchange 2010 shadow redundancy will prevent data loss while messages are in transit within the shaded area.
Figure 1 Shadow Redundancy Mail Flow Scenarios
As can be seen from the figure, all mail flow paths possible in an Exchange organization fit into one of the following six scenarios:
  1. MAPI/Windows Mobile client submission
  2. Mail flow from mailbox server to hub server
  3. Message delivery from hub server to mailbox server
  4. Mail flow between Exchange 2010 transport servers
  5. Mail flow from Exchange 2010 transport servers to mail servers that don't support shadow redundancy
  6. Mail flow from mail servers that don't support shadow redundancy to Exchange 2010 transport servers
The following sections explain what happens for each mail flow scenario.

1. MAPI/Windows Mobile Client Submission

Message submissions from MAPI or Windows Mobile clients are not redundant. Once the message is successfully stored on the mailbox server, Exchange high availability features can take effect and prevent data loss. This scenario is listed here to provide a complete picture of message flow, from beginning to end.

2. Mail Flow from Mailbox Server to Hub Server

The following actions take place when an Exchange 2010 mailbox server submits messages to an Exchange 2010 Hub Transport server.
  1. Mail submission service notifies the Hub server that there is a new message.
  2. Hub server picks up the message from the Outbox of the mailbox submitting the message and stores it in its database.
  3. If the message has recipients on mailbox servers that are in the same AD site, the Hub server delivers the message to the destination mailboxes, following the steps listed in scenario 3. For all other recipients, the Hub server delivers the message to the next hops.
  4. Once delivery to the next hops is complete, Hub server notifies the mailbox server that it has finished processing the message and assumed ownership of the message. After this notification, the message is deleted from the Outbox.
  5. If none of the other hops for the message support shadow redundancy, hub will delete the message. Otherwise, it will convert the message to a shadow message by storing it in the shadow queues for the hops to which it delivered the message.

3. Message Delivery from Hub Transport Server to Mailbox Server

The following actions take place when an Exchange 2010 Hub server delivers messages to an Exchange 2010 mailbox server.
  1. Hub server delivers the message to the destination mailboxes.
  2. Once the message is delivered to all the destination mailboxes, Hub server adds the message to the Transport Dumpster.
  3. Hub server queues discard notifications to the hop from which it has received the message.

4. Mail Flow between Exchange 2010 Transport Servers

The mail flow process is identical for all message exchanges between transport servers running Exchange 2010, whether it is between two Hub servers or between a Hub and an Edge server. The following actions take place when a message is transferred from one Exchange 2010 Transport server to another. For clarity purposes, assume that the server that is sending the message is called Hub01 and the server that is receiving the message is called Edge01.
  1. Hub01 establishes an SMTP connection to Edge01
  2. Edge01 advertises shadow redundancy support.
  3. Hub01 requests shadow redundancy in the SMTP session by issuing an XSHADOW command. The process is similar to establishing TLS on an SMTP session.
  4. For each message that Hub01 needs to send to Edge01,
    1. Hub01 transmits the message to Edge01.
    2. Edge01 marks the message as shadowed by Hub01.
    3. Hub01 converts the message to a shadow message and marks Edge01 as the primary server and adds it to its shadow queue for Edge01.
    4. Hub01 prepares discard notifications for the message to be sent to the hop from which it received the message.
  5. Hub01 queries Edge01 for discard status of messages it has previously submitted to Edge01.
  6. Edge01 sends all discard notifications that it has prepared for Hub01. These could be for messages that are sent in the same SMTP session or for those that were sent during previous SMTP sessions.
  7. Hub01 deletes all shadow messages for which Edge01 has sent a discard notification.

 

5. Mail Flow from Exchange 2010 Transport Servers to Mail Servers That Don't Support Shadow Redundancy

Neither Exchange 2007 transport servers nor Exchange 2003 bridgehead servers support shadow redundancy. Therefore, if you have a coexistence scenario with previous versions of Exchange, Exchange 2010 redundancy features can guarantee message delivery only until the legacy Exchange hop, and not all the way to its destination. The same applies to the scenario where Exchange 2010 Edge servers send messages to non-Exchange mail servers.
The following actions take place when an Exchange 2010 Hub server sends a message to an Exchange Transport server running a previous version of Exchange, or an Exchange 2010 Edge server sends a message to a non-Exchange mail server. For clarity, assume that an Exchange 2010 Hub server called Hub01 is sending a message to an older Exchange transport server called Legacy01.
  1. Hub01 establishes an SMTP connection to Legacy01.
  2. Legacy01 does not advertise shadow redundancy support.
  3. Since Legacy01 did not advertise shadow redundancy, Hub01 will not initiate shadow redundancy on the SMTP session.
  4. Hub01 delivers the message to Legacy01.
  5. Hub01 will delete the message.
  6. Hub01 will prepare discard notifications for the hop from which it received the message.

 

6. Mail Flow from Mail Servers That Don't Support Shadow Redundancy to Exchange 2010 Transport Servers

There are three entry points to an Exchange organization where a mail server that does not support shadow redundancy may establish an SMTP connection to an Exchange 2010 Transport server and send messages.
  • An Exchange Transport server that is running Exchange 2007 or Exchange 2003 connecting to an Exchange 2010 Hub server.
  • A non-Exchange mail server on the Internet connecting to an Exchange 2010 Edge server.
  • A non-Exchange mail server in the organization, like a UNIX server, or an SMTP client that is submitting messages to an Exchange 2010 Hub server.
In this scenario, Exchange 2010 achieves shadow redundancy using a feature called Delayed Acknowledgement. When an Exchange 2010 Transport server receives a message from a mail server that doesn't support shadow redundancy, it delays sending an acknowledgement to the sending mail server until it has confirmed that the message has been successfully delivered to its destination. For more information about delayed acknowledgement.
To illustrate this scenario, assume that an Exchange 2010 Edge server called Edge01 is receiving a message from a non-Exchange mail server on the Internet called Internet01. In this example, the following actions take place:
  1. Internet01 establishes an SMTP connection to Edge01
  2. Edge01 advertises shadow redundancy support.
  3. Since Internet01 does not support shadow redundancy, it simply sends the message to Edge01.
  4. Edge01 marks the message as a delayed acknowledgement message.
  5. Edge01 delivers the message to the next hops using the steps outlined in scenario 4.
  6. Edge01 queries the next hops for the discard status of the message.
  7. Once Edge01 receives discard notifications from all of the next hops, it sends the acknowledgement to Internet01.
  8. Edge01 deletes the message from its database.

No comments:

Post a Comment