Microsoft will be releasing Exchange 2010 SP2 in the second half of this year. There are about 500 bugfixes currently planned to be fixed in this SP. Nice fact Exchange contains 20 million lines of code in C, C# and other languages. It’ll also requires a schema update.
The following new features and capabilities will be included:
- Outlook Web App (OWA) Mini:
A browse-only version of OWA designed for low bandwidth and resolution devices. Based on the existing Exchange 2010 SP1 OWA infrastructure, this feature provides a simple text based interface to navigate the user’s mailbox and access to the global address list from a plurality of mobile devices.
- Hybrid Configuration wizard
Organizations can choose to deploy a hybrid scenario where some mailboxes are on-premises and some are in Exchange Online with Microsoft Office 365. Hybrid deployments may be needed for migrations taking place over weeks, months or indefinite timeframes. This wizard helps simplify the configuration of Exchange sharing features, like: calendar and free/busy sharing, secure mailflow, mailbox moves, as well as online archive.
- Address Book Policies (also known as Global Address List, or GAL, Segmentation):
Allows organizations to segment their address books into smaller scoped subsets of users providing a more refined user experience than the previous manual configuration approach. We also blogged about this new feature recently in GAL Segmentation, Exchange Server 2010 and Address Book Policies.
- Cross-Site Silent Redirection for Outlook Web App:
Enables silent redirection when the client-access server (CAS) must redirect an OWA request to CAS infrastructure located in another Active Directory site. Silent redirection can also provide a single sign-on experience when Forms-Based Authentication is used.
- Customer Requested Fixes:
Exchange 2010 SP2 also will include “customer requested fixes,” which means update rollups released prior to Service Pack 2 will also be contained within SP2.
In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema.
[Source: Exchange Team Blog]