Applies to: Exchange Server 2010 SP1
Topic Last Modified: 2012-07-23
After you complete the configuration steps for a hybrid deployment, you should complete the post-installation tasks to enable any additional needed functionality.
|This topic is meant to be read as part of the Microsoft Exchange Server 2007 and Office 365 Hybrid Deployment checklist. Information or procedures in this topic may depend on prerequisites configured in topics earlier in the checklist. To view the checklist, see Checklist - Exchange 2007 and Office 365 Hybrid Deployment|
Configure Permissions in the Cloud-based Organization
By default, the administrative account that you specified when the cloud-based service was created is granted administrator permissions to the cloud-based organization. This account can configure all aspects of the cloud-based organization and manage recipients located in the organization. You can add additional administrators as needed.
End users are also granted permissions when their mailboxes are moved to or created in the cloud-based organization. By default, they can configure things like their own contact information, distribution group membership, e-mail subscriptions, telephone number, and so on. You can configure the default role assignment policy or create new role assignment policies.
Administrative and end user permissions that are configured in the on-premises organization aren't transferred to the cloud-based organization. You must re-create your permissions in the cloud-based organization.
Learn more at: Understanding Hybrid Deployment Permissions
Configure Additional Remote Domains
The Deployment Assistant has shown you how to configure transport between your on-premises organization and the cloud-based organization. If you have configured remote domains between your organization and other organizations to customize settings such as the type of encoding to use, whether non-delivery reports are enabled, the character set to use, and so on, you should re-create similar custom remote domains in your cloud-based organization.
Learn more at: Understanding Remote Domains
Configure Unified Messaging
Unified Messaging is supported in a hybrid deployment between your on-premises and cloud-based organizations. Your on-premises telephony solution must be able to communicate with the cloud-based organization. Because of this requirement, you may need to purchase additional hardware and software.
If you want to move mailboxes from your on-premises organization to the cloud-based organization, and those mailboxes are configured for Unified Messaging, you should configure Unified Messaging for hybrid deployment prior to moving those mailboxes. If you move mailboxes before you configure Unified Messaging for hybrid deployment, those mailboxes will no longer have access to Unified Messaging functionality.
Learn more at: Plan for UM Coexistence
Configure Information Rights Management
Information Rights Management (IRM) enables users to apply Active Directory Rights Management Services (AD RMS) templates to messages that they send. AD RMS templates can help prevent information leakage by allowing users to control who can open a rights-protected message, and what they can do with that message after it's been opened.
IRM in a hybrid deployment requires planning, manual configuration of the cloud-based organization, and an understanding of how clients use AD RMS servers depending on whether their mailbox is in the on-premises or cloud-based organization.
Learn more at: Understanding IRM in an Exchange 2007 Hybrid Deployment
Configure Outlook Web App Mailbox Policies
Outlook Web App mailbox policies enable you to manage access to features in Outlook Web App. For example, you can control whether users can open the Calendar or other folders in their Inbox, customize their theme, use the spell checker, access file attachments, and more.
By default, every mailbox in the cloud-based organization is assigned to the default Outlook Web App mailbox policy. The default policy allows access to all features of Outlook Web App. You can configure the default Outlook Web App mailbox policy or create additional policies and assign them to mailboxes.
Outlook Web App mailbox policies that you've defined in your on-premises organization aren't transferred to the cloud-based organization. You must re-create your Outlook Web App mailbox policies in the cloud-based organization.
Learn more at: Understanding Outlook Web App Mailbox Policies
Configure Exchange ActiveSync Mailbox Policies
Exchange ActiveSync mailbox policies enable you to apply a common set of policy or security settings to a user or group of users. These policies are applied to the mobile devices that are connected to a user's mailbox. For example, you can control whether users can use the camera on a mobile device, whether a password is required, the maximum calendar age, and so on.
By default, every mailbox in the cloud-based organization is assigned to a default Exchange ActiveSync mailbox policy. The default policy doesn't place any restrictions on mobile devices connected to cloud-based mailboxes and doesn't require that passwords be used on the device. You can configure the default Exchange ActiveSync mailbox policy or create additional policies and assign them to mailboxes.
Exchange ActiveSync mailbox policies that you've defined in your on-premises organization aren't transferred to the cloud-based organization. You must re-create your Exchange ActiveSync mailbox policies in the cloud-based organization.
Learn more at: Understanding Exchange ActiveSync Mailbox Policies
Users running Outlook 2007 or Outlook 2010 who connect using Outlook Anywhere will be automatically reconfigured to connect to the cloud-based organization when their mailbox is moved.
Users who connect a mobile device to their mailbox may be required to manually reconfigure their device, depending on the version of Exchange ActiveSync the device uses. If the device doesn't reconfigure itself automatically, the user can re-create the Exchange ActiveSync association or change their POP or IMAP settings.
Learn more at: Set Up Your E-Mail Account on Your Mobile Phone
If your users use an e-mail client other than Outlook 2007 or Outlook 2010, they must use POP or IMAP if their mailbox is moved to the cloud-based organization.
|Pre-Outlook 2007 clients are not supported by the Microsoft Office 365 service or by on-premises organizations configured for hybrid deployment. Pre-Outlook 2007 clients that connect directly to the Office 365 service, and clients that connect to on-premises Exchange servers that coexist with Office 365, must be upgraded to a supported version.|
Learn more at: E-mail Setup