You have an Exchange Server 2013 organization.
You purchase a Microsoft Office 365 subscription and configure a hybrid deployment.
The network contains an SMTP relay server named smarthost.contoso.com. The server is configured
to use a certificate that has a subject name of smarthost.contoso.com.
All users have Microsoft Outlook 2013 installed on their client computer. Outlook 2013 is configured
to connect to mail.contoso.com.
All Exchange servers have a certificate that has a subject name of mail.contoso.com.
You discover that email messages sent from on-premises users are not delivered to Office 365
recipients. You discover that the Send connector for Office 365 uses a smart host of
smarthost.contoso.com.
You need to ensure that the on-premises users can send email messages to the Office 365 recipients.
Which two actions should you perform? (Each correct answer presents part of the solution. Choose
two.)
A.
Run the Hybrid Configuration Wizard again.
B.
Configure the Microsoft Exchange Online Protection (EOP) Send connector to use
smarthost.contoso.com
C.
Configure the centralized mail transport option.
D.
Remove the smart host from the Send connector.
E.
Assign a certificate that has a subject name of smarthost.contoso.com to the Send connector.
Explanation:
A: Creating and configuring a hybrid deployment with the Hybrid Configuration wizard is now a
single process in Microsoft Exchange Server 2013. First, the wizard creates the HybridConfiguration
object in your on-premises Active Directory. This Active Directory object stores the hybrid
configuration information for the hybrid deployment and is updated by the Hybrid Configuration
wizard. Next, the wizard gathers existing on-premises Exchange and Active Directory topology
configuration data, Office 365 tenant and Exchange Online configuration data, defines several
organization parameters and then runs an extensive sequence of configuration tasks in both the onpremises and Exchange Online organizations.
E:
Note:
* By default, Microsoft Exchange Server 2013 doesn’t allow you to send mail outside of your domain.
To send mail outside your domain, you need to create a Send connector.
* Use the Set-SendConnector cmdlet to modify a Send connector.
/ Parameters include TlsCertificateNameThe TlsCertificateName parameter specifies the X.509 certificate to use with TLS sessions and secure
mail. Valid input for this parameter is [I]Issuer[S]Subject. The Issuer value is found in the certificate’s
Issuer field, and the Subject value is found in the certificate’s Subject field. You can find these values
by running the Get-ExchangeCertificate cmdlet.