Solved

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

Posted on 2014-09-13
4
337 Views
Last Modified: 2014-09-15
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
Comment
Question by:edgardovz
  • 2
  • 2
4 Comments
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
Comment Utility
I have the URLs required here: http://semb.ee/hostnames2013

Simon.
0
 

Author Comment

by:edgardovz
Comment Utility
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
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
Comment Utility
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
 

Author Comment

by:edgardovz
Comment Utility
Thanks for your help..
0

Featured Post

Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

Join & Write a Comment

Utilizing an array to gracefully append to a list of EmailAddresses
Resolve DNS query failed errors for Exchange
Familiarize people with the process of utilizing SQL Server stored procedures from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Micr…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now