Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2012-11-19

Use the New-HybridConfiguration cmdlet to set up a hybrid deployment between your on-premises Exchange organization and a Microsoft Office 365 for enterprises organization.

Syntax

New-HybridConfiguration [-ClientAccessServers <MultiValuedProperty>] [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-Domains <MultiValuedProperty>] [-ExternalIPAddresses <MultiValuedProperty>] [-Features <MultiValuedProperty>] [-OnPremisesSmartHost <SmtpDomain>] [-SecureMailCertificateThumbprint <String>] [-TransportServers <MultiValuedProperty>] [-WhatIf [<SwitchParameter>]]

Detailed Description

A hybrid deployment offers organizations the ability to extend the feature-rich experience and administrative control they have with their existing on-premises Microsoft Exchange organization to the cloud. A hybrid deployment provides the seamless look and feel of a single Exchange organization between an on-premises organization and a cloud-based organization.

For more information, see Understanding Hybrid Deployment.

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Hybrid configuration" entry in the Exchange and Shell Infrastructure Permissions topic.

Parameters

Parameter Required Type Description

ClientAccessServers

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The ClientAccessServers parameter specifies the Exchange Server 2010 SP2 servers with the Client Access server role installed that will be configured to support the hybrid deployment features. At least one Client Access server must be defined and be externally accessible from the Internet on ports 80 and 443. The servers will be configured to enable the following:

  • Mailbox Replication Service (MRS) Proxy   The MRS Proxy service configuration on the Client Access servers will be enabled.

  • Virtual Directories   The Client Access servers will host the default Web sites for the Exchange Web Services (EWS), offline address books, and ActiveSync services.

  • Outlook Anywhere   The Client Access servers will have Outlook Anywhere enabled.

Confirm

Optional

System.Management.Automation.SwitchParameter

The Confirm switch causes the command to pause processing and requires you to acknowledge what the command will do before processing continues. You don't have to specify a value with the Confirm switch.

DomainController

Optional

Microsoft.Exchange.Data.Fqdn

The DomainController parameter specifies the fully qualified domain name (FQDN) of the domain controller that retrieves data from Active Directory. 

Domains

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The Domains parameter specifies the domain namespaces that will be used in the hybrid deployment. These domains must be configured as accepted domains in either the on-premises Exchange organization or cloud-based service. The domains will be used in configuring the organization relationships and Send and Receive connectors used by the hybrid configuration.

ExternalIPAddresses

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The ExternalIPAddress parameter specifies the publicly accessible inbound IP address of the hybrid Hub Transport servers. The IP address must be Internet Protocol version 4 (IPv4) based only.

Features

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The Features parameter specifies the features that can enabled for the hybrid configuration. One or more of the following values separated by commas can be entered. When using the Hybrid Configuration Wizard, all features are enabled by default.

  • MailboxMove   Enables the Mailbox Replication Service Proxy.

  • OnlineArchive   Enables the Exchange Online archive for on-premises and cloud-based organization users.

  • FreeBusy   Enables free/busy calendar information to be shared between on-premises and cloud-based organization users.

  • MailTips   Enables MailTips information to be shared between on-premises and cloud-based organization users.

  • MessageTracking   Enables message tracking information to be shared between on-premises and cloud-based organization users.

  • OWARedirection   Enables automatic Outlook Web App redirection to either the on-premises or cloud-based organizations depending on where the user mailbox is located.

  • SecureMail    Enables secure message transport via Transport Layer Security between the on-premises and cloud-based organizations.

  • Centralized   Enables the coexistence server to handle all message transport between the on-premises and cloud-based organizations, including message delivering to the Internet for both organizations. If this value is $false, the on-premises coexistence server and cloud-based organization are responsible for their own Internet message delivery.

OnPremisesSmartHost

Optional

Microsoft.Exchange.Data.SmtpDomain

The OnPremisesSmartHost parameter specifies the FQDN of the on-premises Hub Transport server used for secure mail transport for messages sent between the on-premises and cloud-based organizations.

SecureMailCertificateThumbprint

Optional

System.String

The SecureMailCertificateThumbprint parameter specifies the thumbprint of the X.509 certificate to be used as the certificate for hybrid deployment secure message transport. This certificate cannot be self-signed, must be obtained from a trusted certificate authority (CA), and must be installed on all Hub Transport servers defined in the TransportServers parameter.

TransportServers

Optional

Microsoft.Exchange.Data.MultiValuedProperty

The TransportServers parameter specifies the Exchange Server 2010 SP2 servers with the Hub Transport server role installed that are configured to support the hybrid deployment features. At least one Hub Transport server must be defined and be externally accessible from the Internet for secure mail to be enabled between the on-premises and cloud-based organizations.

WhatIf

Optional

System.Management.Automation.SwitchParameter

The WhatIf switch instructs the command to simulate the actions that it would take on the object. By using the WhatIf switch, you can view what changes would occur without having to apply any of those changes. You don't have to specify a value with the WhatIf switch.

Input Types

To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn’t accept input data.

Return Types

To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types. If the Output Type field is blank, the cmdlet doesn’t return data.

Examples

EXAMPLE 1

This example creates the hybrid configuration Hybrid Configuration with the default hybrid configuration settings.

Copy Code 
New-HybridConfiguration