Hey,

Our public domain is domainname.com.  Our internal AD domain is corp.domainname.com.

We currently have a single, multi-role Exchange 2010 server.  Outlook clients reports the server as being servername.corp.domainname.com in Account Settings > Server Settings.

We gearing up for the SSL change from 1 November this year where internal names are no longer allowed on a certificate, and I'm not sure how best to proceed.

We have these 2 on our current SAN certificate:

servername
servername.corp.domainname.com

As well as all the 'public' facing Exchange stuff:

autodiscover.domainname.com
mail.domainname.com
webmail.domainname.com (OWA)
mobile.domainname.com (ActiveSync)

My initial thought is to have Outlook clients connect to mail.domainname.com as that's already on the certificate, instead of the internal FQDN.

But I'm not sure how to do that and if it has any repercussions elsewhere?

Thanks

• Edited by Lanky Doodle 17 hours 21 minutes ago

Can you also run Get-OutlookAnywhere | fl server, hostname and Get-Mailboxdatabase | fl name, *rpc* ?

Also, Get-ClientAccessServerArray