You have an Exchange Server 2010 organization.
All users connect to their mailbox by using Microsoft Outlook 2013 and Outlook Web App. All client
connections to Exchange Server use the name mail.contoso.com.
You deploy Exchange Server 2013 to the organization, you move all of the users to Exchange Server
2013, and then you decommission all of the Exchange Server 2010 servers.
The users report that when they open Outlook 2013, they receive a certificate warning message.
The users do not receive a certificate error message or a certificate warning message when they
open Outlook Web App.
You need to prevent the certificate warning message from occurring when the users open Outlook
2013.
Which cmdlet should you run?
A.
Set-ClientAccessServer
B.
New-ExchangeCertficiate
C.
New-ClientAccessArray
D.
Import-ExchangeCertificate
You need a certificate on CAS, which is used by Outlook and other clients, and a certificate on Mailbox server, which is used by CAS. While the client facing certificate must be from a certificate authority trusted by clients, the certificate on the Mailbox server can be a self-signed certificate. This is because CAS automatically trusts the self-signed certificate on the Mailbox server.
0
0
Outlook makes connections to the Exchange server over HTTPS and therefore must trust the SSL certificate that is configured on the server, otherwise it will display error messages to the end user.
To resolve the issue install a valid SSL certificate on the Exchange server from a trusted certificate authority.
0
0
A—This issue can be avoided if you review your Autodiscover configuration and make changes to the Autodiscover namespace configured on the server.
Set-ClientAccessServer AutoDiscoverServiceInternalUri parameter specifies the internal URL of the Autodiscover service.
0
0