• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 399
  • Last Modified:

Exchange 2013 correct internal & external url using wild card SSL and correct auto discovery to correctly populate mobile devices

Hello, I'm trying to get a step by step instruction to modify my Exchange 2013 server to correct invalid internal url's to eliminate the .local so outlook will not report an error on the certificate name and also adjust autodiscovery to correctly automatically populate ios and android mobile device once email and password is entered.  I have added a wild card SSL *.filotec.com.

Server Name:        filo-exch00
Internal FQDN:     https://filo-exch00.filo-tec.local
External FQDN     https://exchange.filotec.com
SSL Certificate      *.filotec.com
Server Type:         Windows Server 2012 Std & Exchange 2013 Std CU6

Right now after I removed my old certificate and installed the new certificate, outlook gives me the red X when connecting (The name on the security certificate is invalid or does not match the name on the site).  would like to know what command lines to type in the EMC to correct this issue and eliminate the .local.
0
Edgardo Vazquez
Asked:
Edgardo Vazquez
  • 2
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
I have the URLs required here: http://semb.ee/hostnames2013

Simon.
0
 
Edgardo VazquezIT TechAuthor Commented:
Brilliant and easy, thank you for the link!  The only thing I would add is since it is a wild card SSL it was recommended to add the following.

Update your EXPR setting
Set-OutlookProvider EXPR -CertPrincipalName msstd:*.filotec.com

Update your EXCH setting
Set-OutlookProvider EXCH -CertPrincipalName msstd:*.filotec.com

Now for the very last part.  Is there a way to get IOS and Android mobile devices to self populate during AutoDiscovery?  Or must we always have it fail and enter server name, domain name manually?
0
 
Simon Butler (Sembee)ConsultantCommented:
Autodiscover is down the device, and that is very hit and miss.
I tell clients that they should presume Autodiscover for mobile devices will fail and have manual instructions ready.

I don't use wildcard certificates in any deployments I do, hence the lack of instructions for them. They are also not recommended with Exchange as you can get some odd results with some mobile devices.

Simon.
0
 
Edgardo VazquezIT TechAuthor Commented:
Thanks for your help..
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now