Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
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
350 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:Edgardo Vazquez
  • 2
  • 2
4 Comments
 
LVL 63

Accepted Solution

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

Simon.
0
 

Author Comment

by:Edgardo Vazquez
ID: 40321890
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)
ID: 40322799
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:Edgardo Vazquez
ID: 40322949
Thanks for your help..
0

Featured Post

Complete VMware vSphere® ESX(i) & Hyper-V Backup

Capture your entire system, including the host, with patented disk imaging integrated with VMware VADP / Microsoft VSS and RCT. RTOs is as low as 15 seconds with Acronis Active Restore™. You can enjoy unlimited P2V/V2V migrations from any source (even from a different hypervisor)

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
Read this checklist to learn more about the 15 things you should never include in an email signature.
In this video we show how to create an email address policy in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Mail Flow…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

789 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