New Mailbox and Recipient Functionality in Exchange 2010 SP1
Applies to: Exchange Server 2010 SP1
Topic Last Modified: 2011-04-28
Microsoft Exchange Server 2010 Service Pack 1 (SP1) provides new functionality for Mailbox servers, mailboxes, and recipients. New functionality is available for the following:
Mailbox full access permission and Outlook Automapping
Group naming policies
Hierarchical address books
Mailbox folder permissions
Internet calendar publishing
Calendar Repair Assistant
Mailbox Assistants service troubleshooter
In Microsoft Office Outlook 2010 and Outlook 2007, Autodiscover automatically maps to any mailbox for which a user has full access permissions. After an administrator grants full access permission for a user to access another user's mailbox or if the user has full access permission to a shared mailbox, Autodiscover automatically loads all mailboxes for which the user has full access permissions. This behavior may cause performance issues when Outlook starts if the user has a large number of mailboxes to which they have full access. For example, in some organizations, Exchange administrators have full access to all users' mailboxes in their organization. If that is the case, Outlook attempts to open all mailboxes in the organization.
|Users can’t control or disable this behavior.|
A group naming policy is a template that you can apply to the name of distribution groups created in the organization. You can enforce the application of a prefix, a suffix, or both to distribution groups. You can also block specific words from being used in distribution group names.
For more information, see Create a Distribution Group Naming Policy.
Importing and exporting mailbox data has been improved so that you can import or export .pst files in an asynchronous process using the Microsoft Exchange Mailbox Replication service. The following cmdlets have been added in Exchange 2010 SP1 to support this feature:
For more information, see Understanding Mailbox Import and Export Requests.
New functionality in Exchange 2010 SP1 for move requests includes the following:
In the release to manufacturing (RTM) version of Exchange 2010, when a mailbox move completed, the mailbox on the source database was deleted and wasn't recoverable. If there was a Mailbox server failover on the target database, the mailbox move was interrupted, and data loss for the in-transit mailbox could occur.
Exchange 2010 SP1 now soft-deletes the mailbox on the source database, so you can recover the mailbox in the event of a Mailbox server failover or data loss. You can restore a soft-deleted mailbox by using the MailboxRestoreRequest cmdlets set.
These soft-deleted mailboxes are visible when running the Get-MailboxStatistics cmdlet against a database and are identifiable by the property DisconnectReason with a value of
SoftDeleted. The soft-deleted mailboxes will be retained in the source database until either the deleted mailbox retention period expires or the mailbox is purged by using the Remove-StoreMailbox cmdlet. If you're performing mailbox moves to reduce the amount of space being used in a database, you must also perform the additional step of purging the soft-deleted mailboxes. Soft-deleted mailboxes can't be reconnected.
Note: You can't view soft-deleted mailboxes by using the Get-MailboxStatistics cmdlet in Exchange versions earlier than Exchange 2010 SP1.
The MoveRequest cmdlet set has been updated to support moving archives to a separate database. For more information, see Understanding Move Requests.
You can now have a user's primary mailbox and archive mailbox on separate databases. For more information, see Understanding Personal Archives.
With hierarchical address book support, you can create and configure your address lists and offline address books (OABs) in a hierarchical view. For more information, see Understanding Hierarchical Address Books.
A new cmdlet has been added that you can use to modify the mailbox folder permissions. The Set-MailboxFolderPermission cmdlet updates folder-level permissions for all folders within a user's mailbox. The cmdlet differs from the Add-MailboxFolderPermission cmdlet in that it edits an existing permission entry.
In Exchange 2010 RTM, sharing user calendar information required a federation trust and an organization relationship or sharing policy with another federated organization. Exchange 2010 SP1 introduces Internet calendar publishing so that users in your Exchange organization can share their calendars with anyone that has access to the Internet, and not just with other recipients in other federated Exchange organizations. Highlights of Internet calendar publishing include:
Federation configuration isn't necessary for your Exchange organization.
Internet users don't need any type of authentication credentials to access user calendars (for example, Exchange or Windows Live).
Users can invite their friends, family members, or business partners to view their calendar information by providing a link to their published calendar.
Exchange administrators can control which users can publish their calendars and what can be shared, both organization-wide and on a per-user basis.
Internet users can access calendar information without having to use a specific mail client; only an Internet browser is necessary.
For more information about sharing policy and calendar publishing, see the following topics:
You can use the Test-CalendarConnectivity cmdlet to verify that Internet calendar sharing is enabled and working properly. The Calendar virtual directory is a subdirectory of the Exchange Outlook Web App virtual directory.
The Calendar Repair Assistant (CRA), which was introduced in Exchange 2010 RTM, is a mailbox assistant that runs within the Microsoft Exchange Mailbox Assistants service on servers running Exchange 2010 with the Mailbox server role installed. CRA automatically detects and corrects inconsistencies that occur for single and recurring meeting items for mailboxes homed on that Mailbox server so that recipients won't miss meeting announcements or have unreliable meeting information. In Exchange 2010 SP1, the Calendar Repair Assistant checks for and detects the following new scenarios:
The attendee's calendar is missing an occurrence or an exception of a meeting.
The attendee's start or end time doesn't match the organizer's start or end time, including time zone inconsistencies.
The attendee's meeting location is different from the organizer's meeting location.
The meeting organizer's calendar is missing an item.
The attendee's recurrence pattern of a meeting series is different from the organizer's recurrence pattern.
For more information, see Understanding Calendar Repair.
The Test-AssistantHealth cmdlet is a new cmdlet that can help you troubleshoot the health of the Microsoft Exchange Mailbox Assistants service (MSExchangeMailboxAssistants). Use the Test-AssistantHealth cmdlet to verify that the Mailbox Assistants service is healthy, to recover from health issues, and to report the status of the diagnosis or recovery action.