Been working in an environment that's in the middle of a poorly planned migration from Exchange 2007 to 2013, however, when setting up a new Outlook profile on a internal client machine, I get an cert error for autodiscover.domain.com, m.domain.com and mobile.domain.com To resolve the cert error, I made a DNS entries for all three names and point it to the new 2013 server, however, I'm not sure where m.domain and mobile.domain.com is configured in the environment since they seem to use owa.domain.com for URLs.  A wildcard certificate is used in the environment which is why making the names in DNS resolve the cert error.

Any ideas what I can check to see why a connection to m.domain.com and mobile.domain.com is being attempted?

I would check the namespaces using PowerShell from the server such as Get-EcpVirtualDirectory, Get-OwaVirtualDirectory, etc.

Also one way that may be a little easier would be to open Outlook and click ok through the certificate prompts, and then go to your Outlook tray icon, hold CTRL and right-click the icon.  Choose Test-Email Autoconfiguration.  Uncheck 'Use Guesssmart' and 'Secure Guesssmart Authentication' and click test.  The XML tab should show you where those URLs are being used.

Lastly, check your 2007 server to see if the URLs are used for any services there.

Thanks,

Jason

Hi Truwarrior,

Thank you for your question.

In addition jesons advice, Please post error for us to troubleshoot.

When Exchange 2007 and Exchange 2013 are existed, if this is private certificate, we should import certificate to client. If this is public certificate, we should make sure we have configured the certificate on Exchange 2013.

In addition, we have used wildcard certificate, we neednt configure m.domain.com and mobile.domain.com in organization.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim