microtix: 2009

What's New in Exchange 2010 Exchange Server 2010 Microsoft Exchange Server 2010 brings a new and rich set of technologies, features, and services to the Exchange Server product line. New features and functionality in Exchange 2010 support several key concepts: •Flexible and reliable •Anywhere access •Protection and compliance The following sections provide you with an overview of some of the important new features and functionality, which you can use when you're planning, deploying, and administering your Exchange 2010 organization. Flexible and Reliable The pressure to optimize your IT infrastructure to respond to changing business conditions demands agility and that means investing in solutions that provide you and your organization choice. Exchange Server 2010 gives you the flexibility to tailor your deployment based on your organization's unique needs and a simplified way to help keep e-mail continuously available for your users. High Availability Functionality Exchange 2010 integrates high availability into the core architecture of Exchange to enable customers of all sizes and in all segments to economically deploy a messaging continuity service in their organization. Exchange 2010 includes many changes to its core architecture. In Exchange 2010, new features such as incremental deployment, mailbox database copies, and database availability groups work with other features such as shadow redundancy and transport dumpster to provide a new, unified platform for high availability and site resilience. Exchange Store and Mailbox Database Functionality The following is a list of core store functionality that's included or has been changed in Exchange 2010: • Deprecated storage groups • Mailbox databases no longer connected to the server object • Improvements in Extensible Storage Engine (ESE) for high availability, performance, and database mobility • Flattened Outlook store schema • Enhanced reporting with public folders Permissions Functionality In Exchange 2010, Role Based Access Control (RBAC) replaces the permissions model used in Exchange 2007. Using RBAC, you can define extremely broad or extremely precise permissions models based on the roles of your administrators and users. For administrators and specialist users, management role groups define what these users can manage in the organization. Role groups associate role group members to a set of management roles that define what the members can do. By adding or removing users as members of role groups, and adding or removing role assignments to or from a role group, you can control what aspects of the organization the members can manage. For end users, management role assignment policies define what users can configure on their own mailbox. Assignment policies are applied to every mailbox either by default or manually, and enable you to control whether users can change their personal information, contact information, distribution group membership, and so on. Both role groups and role assignment policies are assigned management roles. Management roles control access to the cmdlets and parameters required to perform a task. For example, if a cmdlet exists on a management role, and that role is assigned to a role group, the members of that role group can then use that cmdlet. Transport and Routing Functionality The following is a list of new transport and routing functionality included in Exchange 2010: • Shadow redundancy • MailTips • Moderated transport • Federated delivery • Latency service level agreement (SLA) management • End-to-end message tracking • Incremental EdgeSync • Transport rules integration with AD RMS • Transport dumpster improvements • Transport database improvements Exchange Server 2010 Deployment Assistant Exchange Server 2010 introduces the Exchange Deployment Assistant, or ExDeploy, a new Web-based tool that can help you with your Exchange deployment. ExDeploy asks you a few questions about your current environment and then generates a custom checklist and procedures that help simplify your deployment. Administration Functionality in the Exchange Management Console The following is a list of the new core Exchange Management Console (EMC) features included in Exchange 2010. The core EMC refers to new functionality that affects how you use the EMC, and not how you use specific features: • Ability to add Exchange forests to the console tree • Customer Feedback start tab • Community and Resources • EMC command logging • Property dialog box command exposure • RBAC permissions aware for the EMC • Online Exchange Help 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 servers running Exchange 2010 across the network with only Windows Management Framework installed, which includes Windows PowerShell. For more information, see Overview of Exchange Management Shell. • RBAC integration The Shell works with RBAC to give you and your users access only to the cmdlets and parameters you and they are allowed to use. If your permissions don't allow you to configure a certain feature, you aren't given access to the cmdlets, parameters, or both, that manage that feature. For more information, see Understanding Role Based Access Control. • Administrator audit logging Actions that result in the modification of Exchange organization configuration and other object properties in the EMC, the Web management interface, and the Shell can now be logged for later review. For more information, see Overview of Administrator Audit Logging. • Improved multiple-valued property syntax Instead of running multiple commands to add and remove values from a single property, you can now add and remove values with a single command. For more information, see Understanding Multi-Valued Properties. Exchange Control Panel Administrators can use the Exchange Control Panel for Outlook Web App to manage some on-premises tasks. The following is a list of the administrative features available: • Text messaging integration • Voice messaging integration • Multiple mailbox search • Additional proxy addresses for mailboxes • Moderation and approval for distribution list submission In addition, users have self-service capabilities in that they can perform administrative tasks via the Exchange Control Panel. The ECP enables users to perform common tasks without having to call the help desk. This allows your users to be more productive and allows IT staff to deliver more, while reducing support costs. Mailbox and Recipient Functionality The following is a list of the new mailbox and recipient functionality that's included or has been changed in Exchange 2010: • Ability for users to share information, such as calendar free/busy information and contacts with users who reside in a different organization • Improved scheduling and configuring for resource mailbox calendar processing • Ability to move a mailbox while the end user is still accessing it • Additional parameters added to distribution group cmdlets to allow users to create and manage their own distribution groups in Outlook Web App and Exchange 2010 • Ability to appoint a moderator to regulate the flow of messages sent to a distribution group • Ability to manage folder-level permissions for all folders within a user's mailbox • Expanded bulk recipient management to allow you to bulk manage recipient properties • Ability to send mail to recipients from the EMC Exchange Web Services Managed API 1.0 The Microsoft Exchange Web Services (EWS) Managed API 1.0 provides a managed interface for developing client applications that use Exchange Web Services. Beginning with Exchange 2007 Service Pack 1 (SP1), the EWS Managed API simplifies the implementation of applications that communicate with Exchange. Built on the Exchange Web Services SOAP protocol and Autodiscover, the EWS Managed API provides a .NET interface to Exchange Web Services that's designed to be easy to learn, use, and maintain. Client Throttling Functionality to Manage System Performance Exchange 2010 uses client throttling policies to manage the performance of your Exchange organization. To do this, Exchange tracks the resources that each user consumes and enforces connection bandwidth limits as necessary. Some of the benefits of client throttling include making sure that: • Users aren't intentionally or unintentionally taxing the system. • Users of various connectivity methods are proportionally sharing resources. Anywhere Access Enhancements in Exchange 2010 helps users get more done by helping them to access all of their communications—e-mail, voice mail, instant messaging—from virtually any platform, Web-browser, or device through industry standard protocols. Managing the flow of information into and out of an individual’s inbox daily can create overload and affect productivity and profitability. In response to this challenge, Exchange 2010 adds new productivity features that can help users more easily organize and effectively prioritize their communications. Unified Messaging Features The following is a list of new Unified Messaging features included in Exchange 2010: • Call answering rules • Additional language support included in Outlook Voice Access • Enhancements to name lookup from caller ID • Voice mail preview • Message Waiting Indicator • Missed call and voice mail notifications using text messaging • Protected voice mail • Incoming fax support • Addressing to groups (personal distribution lists) support • Built-in Unified Messaging administrative roles Outlook Web App Features The following is a list of new features in Outlook Web App included in Exchange 2010: • Favorites in the navigation pane • Search folders • Message filtering • Ability to set categories in the message list • Options in the Web management interface for Outlook Web App • Side-by-side view for calendars • Multiple client language support • Ability to attach messages to messages • Expanded right-click capabilities • Integration with Office Communicator, including presence, chat, and a contact list • Conversation view • Ability to send and receive text messages from Outlook Web App • Outlook Web App mailbox policies Text Messaging Features The following is a list of new text messaging features included in Exchange 2010: • Missed call and voice mail notifications • Calendar and agenda updates • Text messages sent and received through Outlook Web App and Outlook 2010 • Text message synchronization with a mobile phone POP3 and IMAP4 Cross-Site Connectivity Support Cross-site POP3 and IMAP4 client connectivity is supported by default in Exchange 2010. For more information about POP3 and IMAP4 client connectivity features, see Understanding POP3 and IMAP4. Protection and Compliance Exchange 2010 delivers new, integrated e-mail archiving and retention functionality, including granular multi-mailbox search and immediate legal hold. Exchange 2010 helps you to better protect your company’s communications and e-mail through centrally managed information control capabilities. This includes the ability to intercept, moderate, encrypt and block e-mail more effectively. Together, this functionality provides you with a flexible range of protection and control options, whether you want to automatically enforce controls or empower users to implement their own data protection. Messaging Policy and Compliance Features Exchange 2010 compliance features make retention independent of users' mailbox management and filing habits, and ensure retention policies are applied continuously. The following is a list of new messaging and compliance features included in Exchange 2010: • Additional messaging records management (MRM) functionality to apply message retention policies • Personal Archive feature to provide users with online archive mailboxes and help eliminate PST files • Mailbox search features for cross-mailbox search with Advanced Query Syntax (AQS) support • Additional transport rules predicates and actions IRM-Protected E-Mail Functionality with Active Directory Rights Management Services The following is a list of new Information Rights Management (IRM)-protected e-mail functionality with Active Directory Rights Management Services (AD RMS) included in Exchange 2010: • Microsoft Outlook protection rules, to apply IRM-protection to messages in Outlook 2010 • Transport protection rules, to apply IRM-protection to messages based on rule conditions • Persistent protection of attachments in IRM-protected messages • Support for AD RMS templates • Support for IRM in Microsoft Office Outlook Web App • Transport decryption, to decrypt IRM-protected messages to apply messaging policies • Journal report decryption, to attach a decrypted copy of IRM-protected messages to journal reports • AD RMS protection for Unified Messaging voice mail messages Exchange Server 2010 Deployment Assistant Microsoft Exchange Server 2010 introduces the Exchange Deployment Assistant or ExDeploy, a new Web-based tool that can help you with your Exchange deployment. ExDeploy asks you a few questions about your current environment and then generates a custom checklist and procedures that help simplify your deployment. You can use ExDeploy for the following scenarios: • Upgrade from Exchange Server 2003 • Upgrade from Exchange 2007 • Upgrade from mixed Exchange 2003 and Exchange Server 2007 • New installation of Exchange 2010 New Administrative Functionality in the Exchange Management Console Feature Changes This section briefly describes the new features that have been added to the EMC. New Features in the 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: • New Federation Trust wizard Use this wizard to create a federation trust. A federation trust establishes a trust relationship between an Exchange organization and the Microsoft Federation Gateway. The trust is a prerequisite for enabling calendar free/busy sharing or federated delivery between two Exchange organizations, or allowing users to share their calendar and contacts with external recipients. For details, see Create a Federation Trust. • New Organization Relationship wizard Use this wizard to create a relationship with an external Exchange 2010 organization for the purpose of sharing free/busy information, securing delivery of cross-premises e-mail using federated delivery, and moving mailboxes between on-premises Exchange servers and Microsoft Office Outlook Web App. For details, see Create an Organization Relationship. • New Sharing Policy wizard Use this wizard to create a sharing policy to regulate how users inside your organization can share calendar and contact information with users outside the organization. For details, see Create a Sharing Policy. • New Outlook Web App Mailbox Policy wizard Use this wizard to create an Outlook Web App mailbox policy to apply a common set of policy settings, such as attachment settings. Outlook Web App mailbox policies are useful for applying and standardizing settings for specific groups of users. For details, see Create Outlook Web App Mailbox Policy. New Features in the Server Configuration Node You can no longer manage mailbox or public folder databases from the Server Configuration node. Now, they're managed from the Organization Configuration node. However, you can view mailbox database properties (from the work pane of Server Configuration > Mailbox). In addition, the following features have been added to the node: • Manage Diagnostic Logging Properties wizard Use this wizard to modify the diagnostic logging level for processes used by Exchange 2010. Modifying these levels can help you troubleshoot issues that may occur in your organization. For details, see Manage Diagnostic Logging Levels. • Exchange Certificates tab Use this tab to assign services to an Exchange certificate, remove or renew a certificate, or view the certificate's properties. For details, see the following topics: o Assign Services to a Certificate o Renew an Exchange Certificate o View Exchange Certificate Properties • New Exchange Certificate wizard Use this wizard to help you determine what type of certificates you need for the features in your organization to function correctly. For details, see Create a New Exchange Certificate. • Import Exchange Certificate wizard Use this wizard to help import a certificate with a valid private key to a specified Exchange server. For details, see Import an Exchange Certificate. New Features in the Recipient Configuration Node The following features have been added to the Recipient Configuration node: • Send Mail Click this button to send mail to a recipient from the EMC. Before you can send mail, you need to set up an e-mail account on the computer from which you are sending mail. • Resource scheduling The property pages for resource mailboxes now include tabs for configuring calendaring and scheduling. For details, see Configure User and Resource Mailbox Properties. • Archive mailboxes You can enable or disable archive mailboxes directly from the EMC. In addition, you can manage the archive settings for users from the property page of their mailbox. For details, see Managing Personal Archive. • Move requests If you want to move mailboxes, you can use the New Local Move Request or New Remote Move Request wizards. You can also keep track of move requests that are in progress by using the Move Requests node. For details, see Managing Move Requests. Core EMC Changes The following new functionality affects how you use the EMC, but not how you use specific features. Expand each of these new feature sections to learn more. Add Exchange Forests to the EMC Console Tree You can now add Exchange forests to the EMC. The first forest will always be named Microsoft Exchange On-Premises. This is the default forest for your organization. You can add additional forests by using the Add Exchange Forest wizard. For details, see View Forest Properties. Customer Experience Improvement Program The Customer Experience Improvement Program (CEIP) collects anonymous information about how you use Exchange and the problems that you encounter. Microsoft uses this information to improve the products and features you use most often and to help solve problems. Participation in the program is voluntary, and the end results are software improvements to better meet your needs. For more information about the CEIP, see Microsoft Customer Experience Program FAQ. For details about how to opt-in or opt-out of the program, see Opt-in or Opt-out of the Customer Experience Improvement Program. Organizational Health The Organizational Health report lets you increase productivity by giving you a quick view of your organization and its operating characteristics. The report provides an organizational summary. This includes health and licensing information, and also a summary of Exchange servers and recipients. This report is for information only. If errors occur while collecting the information, the report may not be accurate. Exchange doesn't automatically gather the organizational information. You must use the Collect Organizational Health Data wizard to view a summary of your organization's health. For details, see Collect Organizational Health Data. Customer Feedback The Customer Feedback tab is located in the result pane of the Microsoft Exchange On-Premises node. The tab is divided into two sections: • Customer Feedback Options This section allows you to run the Customer Experience Improvement Program wizard, which allows you to opt-in or out of the CEIP. For more information, see Opt-in or Opt-out of the Customer Experience Improvement Program. • Help and Feedback This section provides a link to the Exchange Server TechCenter and allows you to submit feedback or to report bugs directly to the Exchange team. Exchange Management Shell Command Log The Exchange Management Shell Command Log records the commands that you execute in the EMC. For example, if you view the list of recipients from the Mailbox node, the Get-Recipient cmdlet is executed, and the Exchange Management Shell Command Log records that action. The command log doesn't save the logging information. After you close the EMC, the log is erased. However, you can export the command log to tab-delimited or comma-delimited files. To view the command log, from the EMC toolbar, click View, and then click View Exchange Management Shell Command Log. For information about command logging, see Using the Exchange Management Shell Command Log to Track Tasks Performed in the EMC. Property Dialog Command Exposure Exposing the commands for actions executed in property pages allows you to see the Microsoft Windows PowerShell command and the parameters required to change object properties. To view the command, click the arrow icon located in the bottom left corner of the property page. To copy the command, select the command and press CTRL+C. The command viewer is made available only after you make a property change. Role Based Access Control in the EMC When you open the EMC, Exchange checks to see what Role Based Access Control (RBAC) permissions you have. You can only view or configure features and items for which you have the correct permissions. If an administrator has permission to view an object but not edit it, the field text will appear dimmed and a caution icon will display. For more information about RBAC, see Understanding Role Based Access Control. Exchange Help The Exchange Help files are no longer downloaded to Exchange. Instead, they're hosted on Microsoft TechNet. This ensures that you're always viewing the most up-to-date Help topics. Exchange 2010 contains two new cmdlets for managing Exchange Help: • Set-ExchangeAssistanceConfig Using this cmdlet, you can modify the URLs that the Exchange Help client uses to connect to the source of the Exchange 2010 documentation. By default, TechNet is used as the source. For details, see Set-ExchangeAssistanceConfig. • Get-ExchangeAssistanceConfig Using this cmdlet, you can view the configuration information for the URLs that the Exchange Help client uses to connect to the source of the Exchange 2010 documentation. For details, see Get-ExchangeAssistanceConfig. New Exchange Core Store Functionality Microsoft Exchange Server 2010 includes many improvements to the Exchange database architecture: • Public folder reporting has been enhanced. • Storage groups have been removed. • Mailbox databases aren't connected to the server object and are now peers to the server. Database management has been moved from the Server Configuration node to the Organization Configuration node in the Exchange Management Console (EMC). • Investment in store schema and Extensible Storage Engine (ESE) optimizations have reduced IOPS by 70 percent: o The store schema has been flattened to remove the dependency to the server object. o ESE has been enhanced with several new improvements for high availability, performance, and database mobility. • Store resilience and health have been improved by adding detecting, correcting, and alerting features, such as the following: o Mailbox quarantine on rogue mailboxes o Transport cutoff to databases with less than 1 gigabyte (GB) of space o Thread time-out detection and reporting • Core store functionality has received many changes to improve high availability features. High availability has been integrated into the core architecture of Exchange 2010 to enable organizations of all sizes and in all industry segments to economically deploy a messaging continuity service. For more information about the high availability changes in Exchange 2010, see Understanding High Availability and Site Resilience. Contents Enhanced Reporting for Public Folders Database Management Store Schema Changes New ESE Functionality Enhanced Reporting for Public Folders Public folder reporting has been enhanced to view user initiated changes to any item in the public folder. You can view this information by using the Get-PublicFolderStatistics cmdlet in the Exchange Management Shell. For more information, see Exchange Management Shell. 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 Server 2007, database management was performed in the Server Configuration node. Important: 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 (DAG). However, public folder databases can be hosted on Mailbox servers that are part of a DAG, although public folder databases won't be subject to log shipping or any other DAG features. Database Cmdlet Changes With the removal of storage groups, the storage group cmdlets were deleted and the database cmdlets now provide the functionality, as shown in the following table. Cmdlet Change New-StorageGroup This cmdlet has been deleted, and configuration parameters were moved to the New-MailboxDatabase and New-PublicFolderDatabase cmdlets. Remove-StorageGroup This cmdlet has been deleted, and configuration parameters were moved to the New-MailboxDatabase and New-PublicFolderDatabase cmdlets. Set-StorageGroup This cmdlet has been deleted, and configuration parameters were moved to the New-MailboxDatabase and New-PublicFolderDatabase cmdlets. Get-StorageGroup This cmdlet has been deleted, and configuration parameters were moved to the New-MailboxDatabase and New-PublicFolderDatabase cmdlets. Move-StorageGroupPath This cmdlet has been deleted, and configuration parameters were moved to the Move-DatabasePath cmdlet. New-MailboxDatabase New-PublicFolderDatabase These cmdlets have been extended with the parameters and functionality from the New-StorageGroup cmdlet. They also update the server object with a link to the new database and the database object with the hosting server name. Remove-MailboxDatabase Remove-PublicFolderDatabase These cmdlets have been extended with the parameters and functionality from the Remove-StorageGroup cmdlet. In addition, they also update the server object with the link to the new database and the database object with the hosting server name. Set-MailboxDatabase Set-PublicFolderDatabase These cmdlets have been extended with the parameters and functionality from the Set-StorageGroup cmdlet. When changing the host servers, they also update the server object with the link to the new database and the database object with the hosting server name. Get-MailboxDatabase Get-PublicFolderDatabase These cmdlets have been extended with the parameters and functionality from the Get-StorageGroup cmdlet. The Status parameter is extended to return the status information currently returned by the Get-StorageGroupCopyStatus cmdlet. Move-DatabasePath This cmdlet has been extended with the parameters and functionality from the Move-StorageGroupPath cmdlet. In addition to the preceding cmdlet changes, the StorageGroupCopy cmdlets have been deleted. For more information, see New High Availability and Site Resilience Functionality. Store Schema Changes The store schema has been changed to remove the dependency of mailbox databases to the server object. In addition, the new schema has been improved to help reduce IOPS by refactoring the tables used to store information and increasing the temporal locality of reference. Refactoring the tables allows higher logical contiguity and locality of reference. These changes reduce the store's reliance on the secondary indexes maintained by ESE. As a result, the store is no longer sensitive to performance issues related to the secondary indexes. New ESE Functionality ESE has been improved in Exchange 2010 to achieve the following goals: • Larger I/O and sequential I/O to reduce IOPS • Optimization for commodity storage, which includes just a bunch of disks (JBOD) and serial ATA (SATA) • Database management reduction • Online defragmentation • Online Database Scanning Larger and Sequential I/O By increasing the size of the I/O and reducing the frequency of read/writes in Exchange 2010, ESE is able to increase performance. In addition, ESE can increase performance by making the data in the database more sequential, which increases the likelihood that related data is in the same vicinity in the B-tree. In Exchange, all data inside the database is stored in B-trees, and the B-trees are then divided into pages. In Exchange 2010 and earlier, the data stored in the B-trees isn't contiguous. In fact, previous versions of Exchange performed random read/writes to the database. This means that related data may not be in the same vicinity on the hard disk. Non-contiguous data requires more passes to read and write to the hard disk. Space Allocation Space allocation refers to the method ESE allocates space on the database. Database Long Values Compression A column or a record in ESE can't span pages in the data B-tree. However, there are values in the database that break the 32 kilobyte (KB) boundary of a page. These are referred to as long-values (LV). A table's long-value B-tree is used to store these large values. B-Tree Defragmentation The B-tree defragmentation process has been improved to reduce I/O operations by maintaining contiguous data in the B-tree. B-tree defragmentation is performed in-place (as opposed to creating a new B-tree and renaming the indexes and tables) with three new operations: • Page move A page move consists of moving all data from one page to a newly allocated page. • Partial left merge A partial left merge is the same as a right merge in Exchange 2007 or earlier, except that data is moved from the left page to the right page. • Full left merge A full left merge is the same as a full right merge in Exchange 2007 or earlier. Defragmentation has been changed from right merges to left merges to optimize performance. Data is read from or written to the hard disk from right to left. If the database is being defragmented in the same direction as the read/writes, defragmentation will conflict with the read/writes. In addition, space allocation allows the next page in an extent to be allocated, but not the previous page. Because a page move needs to allocate a new page, defragging the database from left to right is much more efficient. The Defragmentation Manager is a new event in ESE that monitors which B-trees require defragging and which B-trees have already been defragged. The Defragmentation Manager compiles a list of the B-trees in all mounted databases that should be defragged. As fragmented B-trees are discovered, they're registered with the Defragmentation Manager, and the Defragmentation Manager will process them. Page Size Increase to 32 KB All data inside the database is stored in B-trees, and the B-trees are divided into pages. The page size is the minimum size for reading and writing to the database; it's also the unit size used for database caching. Reading from the disk is slower than performing operations in memory; therefore, by increasing the page size to 32 KB, ESE reduces IOPS, which increases performance by caching the larger page size in memory. Async Vs. Sync Database Reads Sync Read I/O = Small/Random I/O Async Write I/O = Large/Sequential I/O Exchange 2010 Store/ESE have put a lot of work into moving away from synchronous database reads to asynchronous database reads to leverage the contiguous nature of the database. View creations and updates, Microsoft Outlook OST sync, Search result returns, content indexing crawls. Optimize for Commodity Storage Another of the goals of ESE in Exchange 2010 is to reduce the capital and operational costs of deploying Exchange. This can be done by reducing storage costs and optimizing for commodity storage using JBOD and SATA class hard disks. Coalesced I/O Disk subsystems are more efficient at handling fewer but larger I/O. In Exchange 2010 or earlier, the page size is the minimum read/write size and the minimum size for database caching. Coalescing I/Os refers to the process of combining database page operations into a single I/O operation, thereby producing fewer and bigger I/O operations. Increasing the average database I/O sizes has the following benefits: • Increased disk use efficiency Disks are more efficient at processing large I/Os. The more efficiently the disk is utilized, the more mailboxes can be hosted on that disk. • Increased cache warming rate Cache warming is a process that helps reduce the execution times by preloading the initial queries that were executed against a database the last time the database was started. After a server restart, failover, or switchover, the larger I/O allows ESE to increase the rate at which the cache is warmed. Database Maintenance One of the goals of ESE in Exchange 2010 is to reduce the cost of maintaining and managing a database. Database maintenance is comprised of several tasks that manage and keep the integrity of your mailbox database. Database maintenance is divided into two parts: • Store mailbox maintenance • ESE database maintenance In Exchange 2007, ESE database maintenance was disk intensive. In Exchange 2010, improvements have been made to increase performance. In Exchange 2010, on large or very heavy profile servers, the store mailbox maintenance task only lasted approximately 45 minutes, while ESE database maintenance usually took from six to eight hours per night to complete on large Exchange 2007 databases (2 GB quotas). In Exchange 2010, improvements have been made to support both large mailboxes as well as to support JBOD storage and storage without the use of RAID. Online Defragmentation In Exchange 2010, the architecture for online defragmentation was changed, and online defragmentation was moved out of the Mailbox database maintenance process, Online defragmentation now runs in the background 24×7. You don't need to configure any settings for this feature. Exchange monitors the database as it's being used and small changes are made over time to keep it defragged for space and contiguity. Online defragmentation is also throttled so it doesn't have a negative impact on client performance. Use the ESE performance counter set MSExchange Database ==> Defragmentation Tasks to see the tasks that are performed. To enable advanced ESE counters, see How to Enable Extended ESE Performance Counters. Online Database Scanning Online Database Scanning (also known as database check-summing) is another significant change. In Exchange 2007 Service Pack 1 (SP1), you had the option to use half of your online defragmentation time for this database scanning process (to ensure Exchange read every page from your database in a specific period of time to detect any corruptions). This I/O is 100 percent sequential (thus easy on the disk) and on most systems equated to a check-summing rate of about 5 megabytes (MB)/sec. The system is designed with the expectation that every database would be fully scanned once every three days. A warning event is fired if the databases weren't scanned. In Exchange 2010, there are now two modes to run Online Database Scanning on active database copies: • Run as the last task in the scheduled Mailbox Database Maintenance process. You can configure how long it runs by changing the Mailbox Database Maintenance schedule. This option works well for smaller databases that are less than 500 GB in size. • Run in the background 24×7, which is the default behavior. This option works well for larger databases, from 500 GB through 2 terabyte (TB), where you need more time to checksum the databases. Exchange scans the database no more than once per day and again will fire a warning alert if it can't finish scanning in a three day period. New High Availability and Site Resilience Functionality Microsoft Exchange Server 2010 reduces the cost and complexity of deploying an e-mail solution that provides the highest levels of server availability and site resilience. Building on the native replication capabilities introduced in Exchange Server 2007, the new high availability architecture in Exchange 2010 provides a simplified, unified framework for both high availability and disaster recovery. Exchange 2010 integrates high availability into the core architecture of Exchange, enabling customers of all sizes and in all segments to be able to economically deploy a messaging continuity service in their organization. Exchange 2007 decreased the costs of high availability and made site resilience much more economical by introducing new technologies such as local continuous replication (LCR), cluster continuous replication (CCR), and standby continuous replication (SCR). Still, some challenges remained: • Some administrators were intimidated by the complexity of Windows failover clustering. • Achieving a high level of uptime can require a high level of administrator intervention. • Each type of continuous replication was managed differently and separately. • Recovering from a failure of a single database on a large Mailbox server could result in a temporary disruption of service to all users on the Mailbox server. • Site resilience solutions were not seamless. • The transport dumpster feature of the Hub Transport server could only protect messages destined for mailboxes in an LCR or CCR environment. If a Hub Transport server fails while processing messages and can't be recovered, it could result in data loss. Exchange 2010 includes significant core changes that integrate high availability deep in its architecture, making it even less costly and easier to deploy and maintain than Exchange 2007 for all customers. Organizations can now deploy a fully redundant Exchange organization with just two servers, and benefit from database-level failovers. Customers benefit from automatic, database-level failover capabilities without having to become experts in Windows failover clustering. Moreover, you can add site resilience to your existing high availability deployments with less complexity. Exchange 2007 introduced many new architectural changes designed to make deploying high availability and site resilience solutions for Exchange faster and simpler. These improvements included an integrated Setup experience, optimized out-of-box configuration settings, and the ability to manage most aspects of the high availability solution using native Exchange management tools. Still, management of an Exchange 2007 high availability solution required administrators to master some clustering concepts, such as the concept of moving network identities and managing cluster resources. In addition, when troubleshooting issues related to a clustered mailbox server, administrators had to use Exchange tools and cluster tools to review and correlate logs and events from two different sources: one from Exchange and one from the cluster. Two other limiting aspects of the Exchange 2007 architecture have also been re-evaluated and re-engineered based on customer feedback: • Clustered Exchange 2007 servers require dedicated hardware. Only the Mailbox server role could be installed on a node in the cluster. This meant that a minimum of four Exchange servers were required to achieve full redundancy of the primary components of a deployment, that is, the core server roles (Mailbox, Hub Transport, and Client Access). • In Exchange 2007, failover of a clustered mailbox server occurs at the server level. As a result, if a single database failure occurred, the administrator had to fail over the entire clustered mailbox server to another node in the cluster (which resulted in brief downtime for all users on the server, and not just those users with a mailbox on the affected database), or leave the users on the failed database offline (potentially for hours) while restoring the database from backup. Mailbox Resiliency Exchange 2010 has been re-engineered around the concept of mailbox resiliency, 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. As a result of this and other database cache architectural changes, failover actions now complete much faster than in previous versions of Exchange. For example, failover of a clustered mailbox server in a CCR environment running Exchange 2007 with Service Pack 2 (SP2) completes in about two minutes. By comparison, failover of a mailbox database in an Exchange 2010 environment completes in 30 seconds or less (measured from the time when the failure is detected to when a database copy is mounted, assuming an available copy that's healthy and up to date with log replay). The combination of database-level failovers and significantly faster failover times dramatically improves an organization's overall uptime. The mailbox resiliency architecture built into Exchange 2010 provides new benefits for organizations and their messaging administrators: • Multiple server roles can coexist on servers that provide high availability. This enables small organizations to deploy a two-server configuration that provides redundancy of mailbox data and service, while also providing redundant Client Access and Hub Transport services. • An administrator no longer needs to build a failover cluster to achieve high availability. Failover clusters are now created by Exchange 2010 in a way that's 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 isn't a clustered application, and it uses only a small portion of the failover cluster components, namely, its heartbeat capabilities and the cluster database, 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 redeploy in a highly availability configuration. • Exchange 2010 provides a view of the event stream that coalesces and 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's easy to move databases when needed. Flexible Mailbox Protection Exchange 2010 includes several new features and core changes that, when deployed and configured correctly, can provide flexible mailbox protection that eliminates the need to make traditional backups of your data. Using the high availability features built into Exchange 2010 to minimize downtime and data loss in the event of a disaster can also reduce the total cost of ownership of the messaging system. By combining these features with other built-in features, such as Legal Hold, organizations can reduce or eliminate their dependency on traditional point-in-time backups and realize the cost savings of doing so. In addition to determining whether Exchange 2010 enables you to move away from traditional point-in-time backups, we also recommend that you evaluate the cost of your current backup infrastructure. Consider the cost of end-user downtime and data loss when attempting to recover from a disaster using your existing backup infrastructure. Also, include hardware, installation and license costs, as well as the management cost associated with recovering data and maintaining the backups. Depending on the requirements of your organization, it is quite likely that a pure Exchange 2010 environment with at least three mailbox database copies will provide lower total cost of ownership than one with backup. Changes to High Availability from Previous Versions of Exchange Exchange 2010 includes many changes to its core architecture. Exchange 2010 combines the key availability and resilience features of CCR and SCR into single high availability solution which handles both onsite data replication and offsite data replication. Mailbox servers can be defined as part of a database availability group (DAG) 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. Other new high availability concepts are introduced in Exchange 2010, such as database mobility and incremental deployment. The concepts of an organization without backups and RAID are also being introduced in Exchange 2010. To summarize, the key aspects to data and service availability for the Mailbox server role and mailbox databases are: • Exchange 2010 uses an enhanced version of the same continuous replication technology introduced in Exchange 2007. For more information, see "Changes to Continuous Replication from Exchange Server 2007" later in this topic. • Storage groups no longer exist in Exchange 2010. Instead, there are simply mailbox databases, mailbox database copies, and public folder databases. The primary management interfaces for Exchange databases has moved within the Exchange Management Console from the Mailbox node under Server Configuration to the Mailbox node under Organization Configuration. • Some Windows Failover Clustering technology is used by Exchange 2010, but it's now completely managed by Exchange. Administrators don't need to install, build, or configure any aspects of failover clustering when deploying highly available Mailbox servers. • Each Mailbox server can host as many as 100 databases, and each database can have as many as 16 copies. • In addition to the transport dumpster feature, a new Hub Transport server feature named shadow redundancy has been added. Shadow redundancy provides redundancy for messages for the entire time they're in transit. The solution involves a technique similar to the transport dumpster. With shadow redundancy, the deletion of a message from the transport database is delayed until the transport server verifies that all of the next hops for that message have completed delivery. If any of the next hops fail before reporting back successful delivery, the message is resubmitted for delivery to that next hop. For more information about shadow redundancy, see Understanding Shadow Redundancy. Incremental Deployment In previous versions of Exchange, service availability for the Mailbox server roles was achieved by deploying Exchange in a Windows failover cluster. To deploy Exchange in a cluster, you had to first build a failover cluster, and then install the Exchange program files. This process created a special Mailbox server called a clustered mailbox server (or Exchange Virtual Server in previous versions of Exchange). If you had already installed the Exchange program files on a non-clustered server and you decided you wanted a clustered mailbox server, you had to build a cluster using new hardware, or remove Exchange from the existing server, install failover clustering, and reinstall Exchange. Exchange 2010 introduces the concept of incremental deployment, which enables you to deploy service and data availability for all Mailbox servers and databases after Exchange is installed. Service and data redundancy is achieved by using new features in Exchange 2010 such as DAGs and database copies. Database Availability Groups A DAG is a set of up to 16 Mailbox servers that provide automatic database-level recovery from failures that affect individual databases. Any server in a DAG can host a copy of a mailbox database from any other server in the DAG. When a server is added to a DAG, it works with the other servers in the DAG to provide automatic recovery from failures that affect mailbox databases, such as a disk failure or server failure. Mailbox Database Copies The high availability and site resilience features first introduced in Exchange 2007 are used in Exchange 2010 to create and maintain database copies, thereby enabling you to achieve your availability goals in Exchange 2010. Exchange 2010 also introduces the new concept of database mobility, which is Exchange-managed database-level failovers. Database mobility disconnects databases from servers, adds support for up to 16 copies of a single database, and provides a native experience for adding database copies to a database. In Exchange 2007, a feature called database portability also enabled you to move a mailbox database between servers. A key distinction between database portability and database mobility, however, is that with database mobility, all copies of a database have the same GUID. Other key characteristics of database mobility are: • Because storage groups have been removed from Exchange 2010, continuous replication now operates at the database level. In Exchange 2010, transaction logs are replicated to one or more Mailbox servers and replayed into a copy of a mailbox database that's stored on those servers. • A failover is an automatic activation process that can occur at either the database level or at the server level. A switchover is a manual activation process that you can perform at the database, server, or data center (site) level. • Database names for Exchange 2010 must be unique within the Exchange organization. • When a mailbox database has been configured with one or more database copies, the full path for all database copies must be identical on all Mailbox servers that host a copy. • Any mailbox database copy (the active or any passive copy) can be backed up using an Exchange-aware Volume Shadow Copy Service (VSS)-based backup application. 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's been further evolved to support new high availability features such as database copies, database mobility, and DAGs. Some of these new architectural changes are briefly described as follows: • 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 that are replicated to one or more other locations and replayed into one or more copies of a mailbox database. • Because the log replay functionality that was performed by the Microsoft Exchange Replication service in Exchange 2007 has been moved into the Exchange 2010 Information Store service (store.exe), the performance hit associated with failovers and switchovers (because a new database cache was put into use) no longer exists. When a failover or switchover occurs, the activated database has a warm cache that's ready for use. • 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. • Log shipping no longer uses a pull model, where the passive copy pulls closed log files from the active copy. Instead, the active copy pushes the log files to each configured passive copy. • Seeding is no longer restricted to using only the active copy of the database. Passive copies of mailbox databases can now be specified as sources for database copy seeding and reseeding. • 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 couldn't 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 management, divergence, the use of the auto database mount dial, and the use of public and private networks. Changes to Routing Behavior When Hub Transport and Mailbox are Co-Located in a DAG When the Hub Transport server is co-located with a Mailbox server that is a member of a DAG, there are changes in routing behavior to ensure that the resiliency features in both server roles will provide the necessary protection for messages sent and received by users on that server. The Hub Transport server role was modified so that it now attempts to re-route a message for a local Mailbox server to another Hub Transport server in same site if the Hub Transport server is also a DAG member and it has a copy of the mailbox database mounted locally. This extra hop was added in order to put the message in transport dumpster on a different Hub Transport server. For example, EX1 hosts the Hub Transport and Mailbox role and is a member of a DAG. When a message arrives in transport for EX1 that is destined for a recipient whose mailbox is also on EX1, transport will re-route the message to another Hub Transport server in the site (for example, EX2), and that server will deliver the message to the mailbox on EX1. There is a second similar behavior change with respect to the Microsoft Exchange Mail Submission service. This service was modified so that it would prefer to not submit messages to a local Hub Transport role when the Mailbox and Hub Transport server is a member of a DAG. In this scenario, the behavior of transport is to load balance submission requests across other Hub Transport servers in same Active Directory site, and fall back to local Hub Transport server if there are no other available Hub Transport servers in the same site. End-to-End Availability Exchange 2010 also includes many features designed to increase end-to-end availability of the system. These features include: • Transport resilience • Online move mailbox • Flexible mailbox protection • Incremental resync • Page patching • Third Party Replication API Transport Resilience Exchange 2007 introduced the transport dumpster feature of the Hub Transport server. The transport dumpster maintains a queue of messages that were delivered to recipients whose mailbox was in a CCR (and in Exchange 2007 SP1, in an LCR) environment. This feature was designed to help protect against data loss by providing an administrator with the option to have a clustered mailbox server automatically come online on another node with a limited amount of data loss. This is referred to as a lossy failover. When a lossy failover occurred, the system automatically re-delivered the recent e-mail messages sent to users on the failed clustered mailbox server, by using the transport dumpster where the e-mail messages were still stored. Although this solution helped to minimize the amount of data lost in a lossy failover, the solution only protected from data loss within a site, and it didn't provide protection for messages in transit. Exchange 2010 introduces core architectural changes that address both issues. Because DAGs can be stretched across Active Directory sites, it's possible for an individual mailbox database to move between Active Directory sites. Because of this design change, the transport dumpster re-delivery request upon a lossy database failover is now issued to Hub Transport servers in both the database's original and new Active Directory sites. One other significant change to the transport dumpster is that it now receives feedback from the replication pipeline. When messages in the transport dumpster have been replicated to all mailbox database copies, they're removed from the transport dumpster. This ensures that only non-replicated data is held in the transport dumpster. In addition to the transport dumpster feature, a new Hub Transport server feature named shadow redundancy has been added. Shadow redundancy provides redundancy for messages for the entire time they're in transit. The solution involves a technique similar to the transport dumpster. With shadow redundancy, the deletion of a message from the transport database is delayed until the transport server verifies that all of the next hops for that message have completed delivery. If any of the next hops fail before reporting back successful delivery, the message is resubmitted for delivery to that next hop. For more information about shadow redundancy, see Understanding Shadow Redundancy. Online Move Mailbox Exchange 2010 includes a new feature that enables you to move mailboxes asynchronously. In Exchange 2007, when you used the Move-Mailbox cmdlet to move a mailbox, the cmdlet logged into both the source database and the target database and moved the content from one mailbox to the other mailbox. There were several disadvantages to having the cmdlets perform the move operation: • Mailbox moves typically took hours to complete, and during the move, users weren't able to access their mailbox. • If the command window used to run Move-Mailbox cmdlet was closed, the move was terminated and had to be restarted from the beginning. • The computer used to perform the move participated in the data transfer. If an administrator ran the cmdlets from their workstation, the mailbox data would flow from the source server to the administrator's workstation and then to the target server. The new move request cmdlets in Exchange 2010 can be used to perform asynchronous moves. Unlike Exchange 2007, the cmdlets don't perform the actual move. The move is performed by the Microsoft Exchange Mailbox Replication Service, a new service that runs on the Client Access server. The New-MoveRequest cmdlet sends requests to the Mailbox Replication Service. For more information about online move mailbox, see Understanding Move Requests. Flexible Mailbox Protection There are several changes to the core architecture of Exchange 2010 that have a direct effect on how you protect your mailbox databases and the mailboxes they contain. 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 100 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. The ability to have multiple copies of a database hosted on multiple servers, means that if you have a sufficient number of database copies, you can use these copies as your backups. For more information on this strategy, see Understanding Backup, Restore and Disaster Recovery. Incremental Resync Exchange 2007 introduced the concepts of lost log resilience (LLR) and incremental reseed. LLR is an internal component of ESE that enables you to recover Exchange mailbox databases even if one or more of the most recently generated transaction log files have been lost or damaged. LLR enables a mailbox database to mount even when recently generated log files are unavailable. LLR works by delaying writes to the database until the specified number of log generations have been created. LLR delays recent updates to the database file for a short time. The length of time that writes are delayed depends on how quickly logs are being generated. LLR is hard-coded to one log file for all Exchange 2010 mailbox databases. Incremental reseed provided the ability to correct divergences in the transaction log stream between a source and target storage group, by relying on the delayed replay capabilities of LLR. Incremental reseed didn't provide a means to correct divergences in the passive copy of a database after divergent logs had been replayed, which forced the need for a complete reseed. In Exchange 2010, incremental resync is the new name for the feature that automatically corrects divergences in database copies under the following conditions: • 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 Page Patching The ability to correct additional causes of divergence is provided by a new ESE mechanism known as page patching. When divergence between an active database and a copy of that database is detected, incremental resync performs the following tasks: • It searches historically in the log file stream to locate the point of divergence. • It locates the changed database pages on the diverged copy. • It reads the changed pages from the active copy and then copies the necessary log files from the active copy. • It applies the database page changes to the diverged copy. • It runs recovery on the diverged copy and replays the necessary log files into the database copy. Third Party Replication API Exchange 2010 also includes a new Third Party Replication API that enables organizations to use third-party synchronous replication solutions instead of the built-in continuous replication feature. For information about partner products for Exchange 2010, see http://www.microsoft.com/exchange/2010/partners/default.mspx. If you're a partner seeking information on the Third Party Replication API, please contact your Microsoft representative. Cut Features from Exchange Server 2007 The following features in Exchange 2007 and Exchange 2007 SP1 no longer exist in Exchange 2010. Their replacements are noted in the table. Feature Replacement Cluster continuous replication (CCR) Database availability groups and mailbox database copies Standby continuous replication (SCR) Database availability groups and mailbox database copies Local continuous replication (LCR) Database availability groups and mailbox database copies Single copy clusters (SCC) Database availability groups and mailbox database copies; built-in third-party synchronous API available to replace third-party data replication used with SCC Clustered mailbox servers Database availability groups and mailbox database copies Storage groups Databases Recovery Storage Group Recovery database New Messaging Policy and Compliance Functionality Exchange Server 2010 has new messaging policy and compliance features which allow organizations to comply with regulations related to messaging retention, protection of personal information, and fulfill legal Discovery requests for messaging records. 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. You create retention policy tags to apply retention settings to default folders such as Inbox and Deleted Items, and a default policy tag for untagged items in a mailbox. You can also create personal tags which are applied by users to custom folders or individual items in a folder. Retention policies allow you to apply message retention settings without impacting the user's e-mail workflow. Users can tag messages based on retention requirements, and do not need to move messages to folders for retention. Messages in a folder can have different retention settings than the folder they reside in. For more details, see Understanding Retention Policies. . Multi-Mailbox Search Exchange 2010 Multi-Mailbox Search allows a user who is assigned the Discovery Management role to search mailbox content in specified mailboxes across the entire Exchange 2010 organization. The scope of the RBAC role assignment determines which mailboxes can be searched. Messages returned by the search are copied to a folder in the specified Discovery mailbox. Multi-Mailbox Search 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-related functions. Legal Hold In Exchange 2010, Multi-Mailbox Search allows a user who is assigned the Discovery Management role to search mailbox content to comply with discovery requests. However, users who own the mailbox or have permissions to access it can delete messages. Messages can also be removed from the mailbox by the Managed Folder Assistant when a retention policy or a managed folder mailbox policy is applied. In Exchange 2010, you can place mailboxes on Legal Hold to protect against intentional, policy-based or accidental deletion of messages from the mailbox. This allows deleted messages to be indexed by Exchange Search, and such messages are returned when the mailbox is searched using Multi-Mailbox Search. Any changes made to messages after a mailbox is placed on Legal Hold are also preserved as different versions of the message. For more details about Legal Hold, see Understanding Multi-Mailbox Search. New IRM-Protected E-mail Functionality with Active Directory Rights Management Services Protection of critical business information with high business value is an important aspect of information protection. Regulations in many countries, regions, and industries such as financial services and healthcare, require organizations to protection personal information collected from customers and employees. Most business communication occurs over e-mail, and a large number of users also use e-mail as a repository of information and documents. Exchange 2010 includes the following Information Rights Management (IRM): • Outlook Protection Rules to aply IRM-protection to messages in Outlook 2010 • Transport Protection Rules to apply IRM-protection to messages based on rule conditions • Persistent protection of attachments in IRM-protected messages. • Support for AD RMS rights policy templates. • Support for IRM in Outlook Web App. • Transport Decryption to allow decryption of IRM-protected messages on Hub Transport servers, to allow you to apply messaging policies. • Journal Report Decryption to attach a decrypted copy of IRM-protected messages to journal reports. • AD RMS protection of Unified Messaging voice mail messages. Personal Archive Personal archives allow you to provision an online archive mailbox for your users, and help you eliminate distributed, unmanaged messaging data in PST files. Users can access their archive mailbox using Outlook 2010 and Outlook Web App. Users can copy or move messages from their primary mailbox to their archive mailbox. Messages are also moved from the primary mailbox to the archive mailbox automatically using an archive policy. Additionally, you can create retention tags with the MoveToArchive action and link them to a retention policy. New Transport Rule Predicates and Actions Transport Rules inspect messages for conditions specified in the rule. Messages that meet the conditions, and none of the exceptions, get the specified actions applied to them. Exchange 2010 includes several new predicates and actions, providing additional flexibility in creating rules and additional options for actions that can be applied to messages. For more information, see Transport Rule Predicates and Transport Rule Actions. The New-TransportRule and Set-TransportRule cmdlets have been enhanced, allowing you to specify all predicates and actions in a single command. All predicates and actions are now available for use as parameters with these cmdlets. New Unified Messaging Functionality and Voice Mail Features New functionality and many new features have been added to Microsoft Exchange Server 2010 Unified Messaging (UM). This topic explains the new features for Unified Messaging and voice mail that are included in Exchange 2010. Contents  Call Answering Rules  Additional Language Support  Improvements to Name Lookup from a Caller ID  Voice Mail Preview  Message Waiting Indicator  Missed Call and Voice Mail Notifications Using SMS  Protected Voice Mail  Incoming Fax Support  Group Addressing Using Outlook Voice Access  Built-in Unified Messaging Administrative Roles Call Answering Rules In Exchange 2010, the Unified Messaging server role allows UM-enabled users to create and customize call answering rules to enhance the experience of people who call them. At the time a user becomes enabled for UM, no call answering rules exist. The Exchange 2010 voice mail is the default call answering behavior. However, users can create up to nine call answering rules. Call answering rules are similar to the Exchange Server 2007 UM auto attendants. There is usually a greeting, a menu prompt, and a list of options to choose from. The key difference between an auto attendant and a call answering rule that, when the call answering rule processes an incoming call, Unified Messaging already knows who the call is for. Using call answering rules, a caller can: • Leave a voice message for the UM-enabled user. • Transfer to an alternate contact of the UM-enabled user. • Transfer to the alternate contact's voice mail. • Transfer to other phone numbers that the UM-enabled user has configured. • Use the Find-Me feature or locate the UM-enabled user via a supervised transfer. Additional Language Support In Exchange 2007, each UM language pack included a Text-to-Speech (TTS) engine and the prerecorded prompts for a specified language. UM language packs for Exchange 2007 are offered in 16 different languages. However, not all the UM language packs contain support for Automatic Speech Recognition (ASR). For ASR, there was only one language—US English. For Exchange 2010, all available language packs contain the Text-to-Speech (TTS) engine and the prerecorded prompts for a specified language and ASR support. However, only some of the language packs contain support for Voice Mail Preview. The US English (en-US) language pack is included on the Exchange 2010 DVD and additional UM language packs can be downloaded from the Microsoft Download Center. • Client Language Support for Unified Messaging • Understanding Unified Messaging Languages Improvements to Name Lookup from a Caller ID In Exchange 2007 Unified Messaging, a voice message was created after a call was diverted to a Unified Messaging server because of a ring-no-answer or busy condition. After the call was answered, Exchange 2007 Unified Messaging tried to resolve the caller ID. It did this so that it could insert a name, rather than a number, into the sender information. In Exchange 2007, name lookups for voice mail messages were done using information about the caller who was in the same dial plan as the user being called. Name lookups were performed by using an Exchange Unified Messaging proxy address (EUM proxy address), using the personal contacts of the user receiving the call, or using the msRTCSIP-Line attribute in Active Directory if Service Pack 1 (SP1) for Exchange 2007 was installed and Exchange 2007 was integrated with Office Communications Server 2007. In Exchange 2010, the name lookup methods used in Exchange 2007 have been enhanced. Although Exchange 2010 includes methods that were used to resolve calling IDs in Exchange 2007, eight other Active Directory attributes have been added for resolving a caller ID to a name. You can use the following steps to look up a name from the calling party's information: 1. Use the caller's name if the caller is signed in to their mailbox from Outlook Voice Access or if they use a Unified Communications client such as Office Communicator 2007 or Office Communicator Phone Edition to place the call. The caller's identity is known because they've already been authenticated by Outlook Voice Access, Office Communicator 2007 or Office Communicator Phone Edition. 2. Use the EUM proxy addresses in Active Directory. If the proxy address contains an at sign (@), it's considered to be a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI). If the proxy address begins with a plus sign (+), it's considered to be an E.164 number. If neither of these symbols is present, the address is considered to be an extension within the same dial plan as the called party or an equivalent dial plan. 3. If the caller ID is a valid SIP URI, use Active Directory to resolve the SIP URI using the EUM proxy addresses. 4. If the caller ID is a valid E.164 number, use Active Directory to resolve the number using the calling party's name. For this to work correctly, you must manually configure the UMCallingLineIds parameter on the UM-enabled mailbox for each user. This is useful when you don't want to publish a telephone number, such as a personal cell phone number, in Active Directory, but still want to resolve the calling party's name by using this phone number. 5. Use Active Directory heuristic matching, if it is enabled, to resolve the number using the calling party's name. Active Directory heuristic matching must be enabled on the dial plan, and the user's account in Active Directory must contain information in at least one of the following Active Directory attributes: 1. TelephoneNumber 2. HomePhone 3. Mobile 4. FacsimileTelephoneNumber 5. OtherTelephone 6. OtherHomePhone 7. OtherMobile 8. OtherFacsimileTelephoneNumber 6. Use the personal Contacts of the called party to resolve the number using the calling party's name. 7. If the calling party's name is not resolved using one the methods described previously, the phone number is used in the voice mail message. Voice Mail Preview In Exchange 2010, the Unified Messaging server role uses ASR on newly created voice mail messages. When users receive voice messages, the messages contain both a recording and text that's been created from the voice recording. Users see the voice message text displayed in an e-mail message from within Outlook Web App, Outlook 2007, or Outlook 2010. Message Waiting Indicator Message Waiting Indicator is a feature found in most legacy voice mail systems and can refer to any mechanism that indicates the existence of a new message. In Exchange 2007, this functionality was provided by a third-party application, which indicated receipt of a new voice message by lighting the lamp on the desk phone. This feature has been added to Exchange 2010, and third-party software isn't needed. Enabling or disabling Message Waiting Indicator is done on the user's mailbox or on a UM mailbox policy. Missed Call and Voice Mail Notifications Using SMS When users are members of a hosted or consumer dial plan, and they configure their voice mail settings with their mobile phone number and configure call forwarding, they can receive notifications about missed calls and new voice messages on their cell phones in a text message via the Short Messaging Service (SMS). However, to receive these types of notifications, the users must first configure text messaging and also enable Notifications on their account. Protected Voice Mail Protected voice mail is Unified Messaging functionality that enables users to send private mail. This mail is protected by Microsoft Rights Management Services (RMS), and users are restricted from forwarding, copying, or extracting the voice file from e-mail. Protected Voice Mail increases the confidentiality of Unified Messaging, and lets users rely on Unified Messaging if they want to limit the audience for voice messages. This functionality is similar to the way private e-mail messages were handled in Exchange 2007. In Exchange 2010, it applies to voice mail messages as well. Incoming Fax Support Exchange 2007 provided built-in support for fax message creation through the Unified Messaging server role. A user with a UM-enabled mailbox could receive fax messages from calls placed to his or her phone number. There's no support in Exchange 2007 UM for inbound fax routing, or for outgoing fax. In Exchange 2010, direct support for fax has been removed from the Unified Messaging server role. Customers who require a fax solution that works with Exchange 2010 will need to deploy a fax partner solution. Fax partner solutions are available from several fax partners. The fax partner solutions are designed to be tightly integrated with Exchange 2010 and allow UM-enabled users to receive incoming fax messages. Group Addressing Using Outlook Voice Access In Exchange 2007, users could use either the telephone user interface (TUI) or voice user interface (VUI) in Outlook Voice Access to send e-mail and voice messages when they logged on to their mailbox. However, users could only send a single e-mail message to a single user in their personal Contacts, to multiple recipients from the directory by adding each recipient individually, or by adding the name of a distribution list from the global address list. In Exchange 2010, when a user signs in to their mailbox using Outlook Voice Access, they can also send e-mail and voice messages to users in a group stored in their personal Contacts. Built-in Unified Messaging Administrative Roles A set of roles for managing Unified Messaging and voice mail features have been defined within Exchange 2010. Administrative roles that included UM were available in Exchange 2000. The following UM-specific administrative roles have been added for Exchange 2010: • UM Mailboxes • UM Prompts • Unified Messaging New Mailbox and Recipient Functionality This topic lists the new functionality available for Mailbox server, mailboxes, and recipients in Exchange Server 2010. For information about the other mailbox features, see the following topics: • New Exchange Core Store Functionality • New High Availability and Site Resilience Functionality What would you like to do? • Calendaring • Calendar Repair • Resource Scheduling • Moving Mailboxes • Distribution Groups • Mailbox Folder Permission Management • Bulk Recipient Management in the EMC • Send Mail • Personal Archive Calendaring Users can share information such as calendar and contacts folders, or access free busy data with users who reside in a different organization. For more information, on free busy access to different organizations, see Managing Federated Sharing. Contacts sharing will first be available for e-mail users who are using Outlook 2010. For information about when Outlook 2010 will be available, visit the rMicrosoft Office Online Web site. Before you can share any information between organizations, a Federated Trust must be established. For more information, see Federation. The MailboxCalendarSettings commands have been removed. The functionality is replaced by the following cmdlets: • Get-MailboxCalendarConfiguration • Set-MailboxCalendarConfiguration • Get-CalendarProcessing • Set-CalendarProcessing Calendar Repair Assistant The Calendar Repair Assistant (CRA) is a configurable, time-based mailbox assistant that runs within the Microsoft Exchange Mailbox Assistants service on Exchange 2010 mailbox servers. CRA automatically detects and corrects inconsistencies that occur for single and recurring meeting items for mailboxes that are homed on that mailbox server so that recipients will not miss meetings or have unreliable meeting information. For more information about the Calendar Repair Assistant, see Understanding Calendar Repair. 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. These cmdlets are for use in moving Exchange 2010 mailboxes between Exchange 2010 databases. Use the Move-Mailbox cmdlet to move legacy Exchange mailboxes. For more information, see Understanding Move Requests or Managing Move Requests. Mailbox moves are now managed by the following cmdlets: • New-MoveRequest This cmdlet will begin the process to move a mailbox. You can test the readiness of a mailbox by running the command with the WhatIf parameter. • Get-MoveRequest This cmdlet will retrieve statistics regarding the status of an on-going mailbox move that was initiated using the New-MoveRequest command. • Remove-MoveRequest This cmdlet will cancel an on-going mailbox move that was initiated using the New-MoveRequest command. • New-MoveRequest • Get-MoveRequest • Remove-MoveRequest Distribution Groups Moderated Distribution Groups You can appoint a moderator to regulate the flow of messages sent to a distribution group. Anyone can send a message to the distribution group alias, but before the message is delivered to all participants a moderator must review and approve it. This helps prevent inappropriate or time-wasting e-mail blasts from being delivered to large audiences. For more information, see Understanding Moderated Transport. User-Created Distribution Groups New parameters have been added to the distribution group cmdlets to allow users to create and manage their own distribution groups in Outlook Web App and Outlook 2010 and new UI has been added to allow administrators to manage the distribution group ownership and how users can be added to the distribution group. To see the new UI, open a distribution group's property dialog box (right-click on the group) and the there are new changes on the Group Information tab and the Membership Approval tab. The ManagedBy parameter has been updated to indicate ownership of a distribution group and users specified in the ManagedBy parameter can modify the distribution group settings. The functionality for the ManagedBy parameter in the dynamic distribution groups cmdlets did not change. The following cmdlet changes have been made to support this feature: Cmdlet New Parameters New-DistributionGroup • MemberDepartRestriction • MemberJoinRestriction Remove-DistributionGroup BypassSecurityGroupManagerCheck Set-DistributionGroup BypassSecurityGroupManagerCheck MemberDepartRestriction MemberJoinRestriction Add-DistributionGroupMember BypassSecurityGroupManagerCheck Remove-DistributionGroupMember BypassSecurityGroupManagerCheck 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: • Add-MailboxFolderPermission • Get-MailboxFolderPermission • Remove-MailboxFolderPermission 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. In Exchange 2010, bulk recipient management has been expanded to allow you to include the following tasks: • Properties Select multiple recipients in the result pane and then click Properties in the action pane. Properties that you can't bulk edit are grayed-out. You can only bulk edit recipient properties when the same recipient types are selected. • Send Mail You can send mail to multiple recipients from the EMC. Select multiple recipients in the result pane, and then click Send Mail in the action pane. 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. You can send mail to the following recipient types: • User Mailboxes • Mail Contacts • Mail Users • Dynamic Distribution Groups • Distribution Groups You cannot send mail to resource mailboxes. Personal Archive Personal Archive is a specialized mailbox associated with a user’s primary mailbox. It appears alongside the primary mailbox folders in Outlook 2010 or Outlook Web App. 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” e-mail from .PST files into the personal archive for easier online access. E-mail items from the primary mailbox can also be offloaded to the personal archive automatically using retention polices, which reduces the mailbox size and improves application and network performance. In addition, users can search both their personal archive and primary mailbox using Outlook 2010 or Outlook Web App. New Transport Functionality The following is a list of new transport and routing functionality that has been included in Exchange 2010: • MailTips MailTips provide extra information that's displayed to senders while they're composing e-mail messages. They provide information about the messages such as details about the recipient and their availability, or reasons the message wouldn't be delivered. For example, if the person the message is addressed to is out of the office, senders will be informed about this while they're composing the message. To learn more about MailTips, see Understanding MailTips. • 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. To learn more about shadow redundancy, see rUnderstanding Shadow Redundancy. • 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. To learn more about moderated Transport, see Understanding Moderated Transport. • End-to-end message tracking Exchange 2010 Transport provides the users ability to track messages from submission to the final destination. There is a new message tracking tool that makes it easy for any user role, from end-user to administrator, to track messages. For more information, see Understanding Message Tracking. • Support for Disabling TLS for WAN Topologies In certain topologies where WAN Optimization Controller (WOC) devices are used, the TLS encryption of SMTP traffic may be undesirable. Exchange 2010 supports disabling TLS for Hub-to-Hub communications for these specific scenarios. For more information, see Disabling TLS Between Active Directory Sites to Support WAN Optimization. • Incremental EdgeSync In Exchange 2010, EdgeSync process has been changed to keep track of synchronized information and only synchronize the changes since the last replication cycle. This significantly reduces network traffic and greatly improves synchronization efficiency. For more information, see Understanding Edge Subscriptions. • New Transport Rule Predicates and Actions Transport Rules inspect messages for conditions specified in the rule. Messages that meet the conditions, and none of the exceptions, get the specified actions applied to them. Exchange 2010 includes several new predicates and actions, providing additional flexibility in creating rules and additional options for actions that can be applied to messages. For more information, see Transport Rule Predicates and Transport Rule Actions. • Improvements to Transport Rule Cmdlets The New-TransportRule and Set-TransportRule cmdlets have been enhanced, allowing you to specify all predicates and actions in a single command. All predicates and actions are now available for use as parameters with these cmdlets. For more information, see New-TransportRule and Set-TransportRule cmdlet reference topics. • 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. For more information, see Understanding Transport Protection Rules. • Distribution Group Expansion Improvements The handling of distribution group expansion has improved Exchange 2010. First of all, the amount of memory that is used for caching distribution group membership has been capped by a configurable limit. This change prevents the cache from consuming too much memory, and thereby impacting performance in large environments. Exchange 2010 also queries Active Directory in a more efficient manner when processing large distribution groups with delivery restrictions, improving the performance of message delivery to large distribution groups. • Message Throttling Improvements In Exchange 2010, you can configure a Receive connector to monitor the rate of message submissions by users, IP addresses, or both. If you configure a Receive connector to monitor the message submission rate for users, then it will ensure that a specific user doesn't exceed the message rate that it is allowed, regardless of the IP address the connections are coming from. The default client Receive connector created on the Hub Transport servers is configured this way. • Latency 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. Discontinued Features and De-Emphasized Functionality This topic discusses the components, features, or functionality that has been removed, discontinued, or replaced in the latest version of Exchange. Components or Features Replaced or Removed This topic contains the following sections: • Discontinued Features from Exchange 2007 to Exchange 2010 • Discontinued Features from Exchange 2003 to Exchange 2010 • Deemphasized Functionality from Exchange 2003 to Exchange 2010 Discontinued Features from Exchange 2007 to Exchange 2010 This section includes features that were discontinued between the releases of Exchange 2007 to Exchange 2010. Architecture features Feature Comments and mitigation Storage groups Use the new Database Copies functionality in Exchange 2010. See, Understanding Mailbox Database Copies. Extensible Storage Engine (ESE) streaming backup APIs Use Volume ShadowCopy Service (VSS)-based copies, such as Windows Server Backup and the VSS-plug included with Exchange 2010. See Understanding Backup, Restore and Disaster Recovery. Outlook Web App Features Feature Comments and mitigation Document Access Access to Sharepoint Document Libraries and Windows file shares via Outlook Web App is not available in this release. Web Parts Web parts are not supported in this release. User Selectable Outlook Web App themes. Users cannot change the theme in Outlook Web App. Reading pane at the bottom of the page. There is no option to display the reading pane at the bottom of the Outlook Web App window. Create new post in the mailbox. New posts can be created only in Public Folders. High Availability Features Feature Comments and mitigation Cluster Continuous Replication (CCR) Use database availability groups and mailbox database copies. See High Availability and Site Resilience. Local Continuous Replication (LCR) Use database availability groups and mailbox database copies. See High Availability and Site Resilience. Standby Continuous Replication (SCR) Use database availability groups and mailbox database copies. See High Availability and Site Resilience. Single Copy Cluster (SCC) Use database availability groups and mailbox database copies. See High Availability and Site Resilience. Setup /recoverCMS Use Setup /m:recoverServer. See Recover a Database Availability Group Member Server. Clustered mailbox servers Use database availability groups and mailbox database copies. See High Availability and Site Resilience. Recipient Related Features Feature Comments and mitigation Feature Comments and mitigation Exchange WebDAV Replace the WebDAV functionality with Exchange Web Services or EWS Managed API. Or maintain an Exchange 2007 server in the organization for mailboxes of the applications that use WebDAV. For more information, see Migrating from WebDAV. Discontinued Features from Exchange 2003 to Exchange 2010 Microsoft Exchange Server 2010 introduces new technologies that replace technologies that are included in earlier versions of Exchange. For more information about the API and Development tools changes, see Migrating from Older Technologies. This section includes features that were discontinued between the releases of Exchange 2003 to Exchange 2010. Architecture Features Feature Comments and mitigation Routing groups Exchange 2010 uses Active Directory site-based routing. Routing groups are no longer needed. Administrative groups Exchange 2010 uses the Exchange 2007 split permissions model that is based on Universal Security Groups (USGs). Intelligent Message Filter Exchange 2010 uses anti-spam agents in the Hub Transport and Edge Transport server roles. Link state routing Exchange 2010 uses Active Directory site-based routing. Link state routing is not used. Routing objects Exchange 2010 uses Active Directory site-based routing. Routing objects are no longer used. Network-attached storage Exchange 2010 supports Internet SCSI (iSCSI). Exchange Installable File System (ExIFS) Exchange Web Services or MAPI enable you to perform the necessary tasks. Event service Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Recovery storage group Use the recovery database. See Recovery Database. Recipient-Related Features Feature Comments and mitigation Exchange extensions in Active Directory Users and Computers Recipient management is included in the Exchange Management Console in Exchange 2010. Microsoft Exchange Server Mailbox Merge Wizard (ExMerge.exe) The Exchange Management Shell Export-Mailbox cmdlet or the Move Request cmdlets to perform the necessary mailbox tasks. Recipient Update Service (RUS) Use the Update-AddressList and Update-EmailAddressPolicy Exchange Management Shell cmdlets. To replace the full functionality of RUS, you can schedule these Exchange Management Shell commands by using the Task Scheduler. Public Folder Features Feature Comments and mitigation Non-MAPI top-level hierarchies in a public folder store Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Public folder access by using Network News Transfer Protocol (NNTP) Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Public folder access by using IMAP4 Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Protocol Features Feature Comments and mitigation NNTP Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. POP3 or IMAP4 graphical user interface (GUI) management Use Exchange Management Shell cmdlets or the Exchange Management Console. For more information, see Managing POP3 and IMAP4. X.400 Message Transfer Agent (MTA) Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. SMTP virtual server instances Use Exchange 2010 SMTP connectors. Connector Features Feature Comments and mitigation Microsoft Exchange Connector for Novell GroupWise and migration tools Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Microsoft Exchange Connector for Lotus Notes Use the appropriate tools for coexisting and migrating from Lotus Notes available at the Resources for Interoperability and Migration from Lotus Domino Web site. Tools and Management Features Feature Comments and mitigation Monitoring and status node Use a monitoring solution such as Microsoft Operations Manager. Message Tracking Center node and tracking mechanism Use the Exchange Server Mail Flow Analyzer. Mailbox Recovery Center Use the Exchange Server Disaster Recovery Analyzer. Mailbox Management Service Use Messaging Records Management or Retention policies. Clean Mailbox tool Use the export-mailbox Exchange Management Shell cmdlet. Migration Wizard Use the New-MoveRequest cmdlet Exchange Management Shell cmdlet or the Local Move Request and Remote Move Request wizards to move mailboxes from Exchange Server 2003 to Exchange 2010. For more information, see Understanding Move Requests. ExProfRe Use the Autodiscover service. For more information, see rUnderstanding the Autodiscover Service. Deemphasized Functionality from Exchange 2003 to Exchange 2010 There are legacy Exchange features that are now being deemphasized in Exchange 2010: • Proxy address generators - Use the Exchange Management Shell. • CDO 1.2.1 - This functionality is provided by the Exchange Web Services. • MAPI32 - This functionality is provided by the Exchange Web Services. • CDOEX (CDO 3.0) - This functionality is provided by the Exchange Web Services. • Exchange WebDAV extensions - This functionality is provided by the Exchange Web Services. • ExOLEDB - This functionality is provided by the Exchange Web Services. • Store events - This functionality is provided by the Notification Web service. • Exchange 2003 Virus Scanning Application Programming Interface (VSAPI) Discontinued Features and De-Emphasized Functionality This topic discusses the components, features, or functionality that has been removed, discontinued, or replaced in the latest version of Exchange. Components or Features Replaced or Removed This topic contains the following sections: • Discontinued Features from Exchange 2007 to Exchange 2010 • Discontinued Features from Exchange 2003 to Exchange 2010 • Deemphasized Functionality from Exchange 2003 to Exchange 2010 Discontinued Features from Exchange 2007 to Exchange 2010 This section includes features that were discontinued between the releases of Exchange 2007 to Exchange 2010. Architecture features Feature Comments and mitigation Storage groups Use the new Database Copies functionality in Exchange 2010. See, Understanding Mailbox Database Copies. Extensible Storage Engine (ESE) streaming backup APIs Use Volume ShadowCopy Service (VSS)-based copies, such as Windows Server Backup and the VSS-plug included with Exchange 2010. See Understanding Backup, Restore and Disaster Recovery. Outlook Web App Features Feature Comments and mitigation Document Access Access to Sharepoint Document Libraries and Windows file shares via Outlook Web App is not available in this release. Web Parts Web parts are not supported in this release. User Selectable Outlook Web App themes. Users cannot change the theme in Outlook Web App. Reading pane at the bottom of the page. There is no option to display the reading pane at the bottom of the Outlook Web App window. Create new post in the mailbox. New posts can be created only in Public Folders. High Availability Features Feature Comments and mitigation Cluster Continuous Replication (CCR) Use database availability groups and mailbox database copies. See High Availability and Site Resilience. Local Continuous Replication (LCR) Use database availability groups and mailbox database copies. See High Availability and Site Resilience. Standby Continuous Replication (SCR) Use database availability groups and mailbox database copies. See High Availability and Site Resilience. Single Copy Cluster (SCC) Use database availability groups and mailbox database copies. See High Availability and Site Resilience. Setup /recoverCMS Use Setup /m:recoverServer. See Recover a Database Availability Group Member Server. Clustered mailbox servers Use database availability groups and mailbox database copies. See rHigh Availability and Site Resilience. Recipient Related Features Feature Comments and mitigation Move-Mailbox Use Move Requests to move mailboxes. For more information, see Understanding Move Requests. Feature Comments and mitigation Exchange WebDAV Replace the WebDAV functionality with Exchange Web Services or EWS Managed API. Or maintain an Exchange 2007 server in the organization for mailboxes of the applications that use WebDAV. For more information, see Migrating from WebDAV. Discontinued Features from Exchange 2003 to Exchange 2010 Microsoft Exchange Server 2010 introduces new technologies that replace technologies that are included in earlier versions of Exchange. For more information about the API and Development tools changes, see Migrating from Older Technologies. This section includes features that were discontinued between the releases of Exchange 2003 to Exchange 2010. Architecture Features Feature Comments and mitigation Routing groups Exchange 2010 uses Active Directory site-based routing. Routing groups are no longer needed. Administrative groups Exchange 2010 uses the Exchange 2007 split permissions model that is based on Universal Security Groups (USGs). Intelligent Message Filter Exchange 2010 uses anti-spam agents in the Hub Transport and Edge Transport server roles. Link state routing Exchange 2010 uses Active Directory site-based routing. Link state routing is not used. Routing objects Exchange 2010 uses Active Directory site-based routing. Routing objects are no longer used. Network-attached storage Exchange 2010 supports Internet SCSI (iSCSI). Exchange Installable File System (ExIFS) Exchange Web Services or MAPI enable you to perform the necessary tasks. Event service Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Recovery storage group Use the recovery database. See Recovery Database. Recipient-Related Features Feature Comments and mitigation Exchange extensions in Active Directory Users and Computers Recipient management is included in the Exchange Management Console in Exchange 2010. Microsoft Exchange Server Mailbox Merge Wizard (ExMerge.exe) The Exchange Management Shell Export-Mailbox cmdlet or the Move Request cmdlets to perform the necessary mailbox tasks. Recipient Update Service (RUS) Use the Update-AddressList and Update-EmailAddressPolicy Exchange Management Shell cmdlets. To replace the full functionality of RUS, you can schedule these Exchange Management Shell commands by using the Task Scheduler. Public Folder Features Feature Comments and mitigation Non-MAPI top-level hierarchies in a public folder store Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Public folder access by using Network News Transfer Protocol (NNTP) Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Public folder access by using IMAP4 Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Protocol Features Feature Comments and mitigation NNTP Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. POP3 or IMAP4 graphical user interface (GUI) management Use Exchange Management Shell cmdlets or the Exchange Management Console. For more information, see Managing POP3 and IMAP4. X.400 Message Transfer Agent (MTA) Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. SMTP virtual server instances Use Exchange 2010 SMTP connectors. Connector Features Feature Comments and mitigation Microsoft Exchange Connector for Novell GroupWise and migration tools Retain a computer that is running Exchange 2003 in the Exchange 2010 organization if you need this functionality. Microsoft Exchange Connector for Lotus Notes Use the appropriate tools for coexisting and migrating from Lotus Notes available at the Resources for Interoperability and Migration from Lotus Domino Web site. Tools and Management Features Feature Comments and mitigation Monitoring and status node Use a monitoring solution such as Microsoft Operations Manager. Message Tracking Center node and tracking mechanism Use the Exchange Server Mail Flow Analyzer. Mailbox Recovery Center Use the Exchange Server Disaster Recovery Analyzer. Mailbox Management Service Use Messaging Records Management or Retention policies. Clean Mailbox tool Use the export-mailbox Exchange Management Shell cmdlet. Migration Wizard Use the New-MoveRequest cmdlet Exchange Management Shell cmdlet or the Local Move Request and Remote Move Request wizards to move mailboxes from Exchange Server 2003 to Exchange 2010. For more information, see Understanding Move Requests. ExProfRe Use the Autodiscover service. For more information, see Understanding the Autodiscover Service. Deemphasized Functionality from Exchange 2003 to Exchange 2010 There are legacy Exchange features that are now being deemphasized in Exchange 2010: • Proxy address generators - Use the Exchange Management Shell. • CDO 1.2.1 - This functionality is provided by the Exchange Web Services. • MAPI32 - This functionality is provided by the Exchange Web Services. • CDOEX (CDO 3.0) - This functionality is provided by the Exchange Web Services. • Exchange WebDAV extensions - This functionality is provided by the Exchange Web Services. • ExOLEDB - This functionality is provided by the Exchange Web Services. • Store events - This functionality is provided by the Notification Web service. • Exchange 2003 Virus Scanning Application Programming Interface (VSAPI) Overview of Exchange 2010 Server Roles Because organizations tend to group their management tasks around a core set of server roles, Exchange 2010 maps Exchange Server management to this same approach. System management in Exchange 2010 fundamentally shifts the administrative experience for deploying and managing servers to focus on server roles. A server role is a unit that logically groups the required features and components needed to perform a specific function in the messaging environment. The requirement of a server role is that it is a server that could be run as an atomic unit of scalability. A server role is composed of a group of features. Server roles, the primary unit of deployment, enable administrators to easily choose which features are installed on an Exchange server. Logically grouping features in server roles offers the following advantages: • Reduces attack surface on an Exchange server. • Allows you to install and configure an Exchange server the way you intend to use it. • Offers a simple installation and the ability to fully customize a server to support your business goals and needs. exExchange2010 includes the following server roles: • Mailbox Server This server hosts mailboxes and public folders. For more information about the Exchange 2010 Mailbox server role, see Overview of the Mailbox Server Role. • Client Access Server This is the server that hosts the client protocols, such as Post Office Protocol 3 (POP3), Internet Message Access Protocol 4 (IMAP4), Secure Hypertext Transfer Protocol (HTTPS), Outlook Anywhere, Availability service, and Autodiscover service. The Client Access Server also hosts Web services. For more information about the Exchange 2010 Client Access server role, see Client Access. • Unified Messaging Server This is the server that connects a Private Branch eXchange (PBX) system to Exchange 2010. For more information about the Exchange 2010 Unified Messaging server role, see Unified Messaging. • Hub Transport Server This is the mail routing server that routes mail within the Exchange organization. For more information about the Exchange 2010 Hub Transport server role, see Transport and Overview of the Hub Transport Server Role. • Edge Transport Server This is the mail routing server that typically sits at the perimeter of the topology and routes mail in to and out of the Exchange organization. For more information about the Exchange 2010 Edge Transport server role, see Transport and Overview of the Edge Transport Server Role. • Exchange 2010: Editions and Versions • Applies to: Exchange Server 2010 Topic Last Modified: 2009-11-11 • Microsoft Exchange Server 2010 is available in two server editions: Standard Edition and Enterprise Edition. Enterprise Edition can scale to 100 databases per server; Standard Edition is limited to 5 databases per server. These are licensing editions that are defined by a product key. When you enter a valid license product key, the supported edition for the server is established. • Product keys can be used for the same edition key swaps and upgrades only; they can't be used for downgrades. You can use a valid product key to move from the evaluation version (Trial Edition) to either Standard Edition or Enterprise Edition. You can also use a valid product key to move from Standard Edition to Enterprise Edition. You can also license the server again using the same edition product key. For example, if you had two Standard Edition servers with two keys, but you accidentally used the same key on both servers, you can change the key for one of them to the other key that you were issued. You can take these actions without having to reinstall or reconfigure anything. After you enter the product key and restart the Microsoft Exchange Information Store service, the edition corresponding to that product key will be reflected. • No loss of functionality will occur when the Trial Edition expires, so you can maintain lab, demo, training, and other non-production environments beyond 120 days without having to reinstall the Trial Edition of Exchange 2010. • As mentioned earlier, you can't use product keys to downgrade from Enterprise Edition to Standard Edition, nor can you use them to revert to the Trial Edition. These types of downgrades can only be done by uninstalling Exchange 2010, reinstalling Exchange 2010, and entering the correct product key. • Exchange Client Access Licensing • Exchange 2010 also comes in two client access license (CAL) editions, which are also called Standard Edition and Enterprise Edition. You can mix and match the server editions with the CAL editions. For example, you can use Enterprise Edition CALs against Standard Edition. Similarly, you can use Standard Edition CALs against Enterprise Edition. For more information, see Microsoft Exchange Server 2010 How to Buy.

microtix

Thursday, December 31, 2009

Innovation at Microsoft

The Microsoft Way

Wednesday, December 23, 2009

Windows Server 2008 R2 E Book

Introduction to Exchange 2010

Windows 7

Linux 101 Hacks

IPV6 Under the Hood

Tuesday, December 22, 2009

Windows 7 Tips and Tricks

1: Have you tried turning it off and on again?

2: Visit the Action Centre

3: Try Windows Update

4: Reinstall the Driver

5: Clean up Windows

6: Run the System File Checker

7: Reinstall the software

9: Search for a solution online

Windows 7 Tips & Tricks

Tuesday, December 1, 2009

Exchange 2010

Search 2.0

Search This Blog

Followers

Blog Archive

About Me