Solved

Exchange Certs after Oct 2015

Posted on 2013-11-20
10
386 Views
Last Modified: 2013-11-25
Okay, I seem to be running into this a bit lately, but nobody seems to be able to answer this.  When setting up an Exchange server 2007/2010 I used to get a UCC certificate that has the following names in them:
exchange.company.local
autodiscover.company.com
mail.company.com

These three entries would get me up an running in a single server Exchange setup.  But, now if I request a certificate that is past Oct 2015, I'm being told I can't have the exchange.company.local included.  

So how do I get my internal users to connect with Outlook, if I don't have a certificate with the internal name on it?
0
Comment
Question by:Computech
10 Comments
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 39664693
For smaller deployments, Exchange does not, never has, and most importantly (for security reasons) SHOULD not have certificates with .local in them. You set your URLs to a public FQDN via powershell and you deploy split DNS if necessary

for very large deployments, you can have internal CAS servers with private FQDN certificates issued by your internal CA but you'd want to prevent any and all public traffic to those CAS servers to prevent any MITM attacks.

so, in short, refer to the exchange deployment guides and pick your URLs accordingly so you can get a legit public cert.
0
 
LVL 9

Expert Comment

by:Mahesh Sharma
ID: 39665429
Have you deployed this certificate on all exchange servers or on your public facing security device.

If exchange servers are using only self signed certs then you can go for internal CA certs
Other thing you may try is to create a CName record for .local pointing to some certificate name
0
 

Author Comment

by:Computech
ID: 39666528
Well, what I have been doing may not be best practice, but it got the job done!  Anyways, so I still don't see a solution here.

Exchange 2010 doesn't support having 2 certificates on a single service, so I can't have an internal cert and a public cert installed, to cover both internal users and external users.

I cannot change my internal domain on my AD to match, or to something real.

How does everyone do this?  I can't be the only guy to run into this?
0
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 39666553
As I said, you don't need to use your internal domain name at all. Simply set your various directories (you can do this in the GUI or PowerShell) to use a public FQDN. Those URLs will be what exchange gives to outlook clients (even internal ones) so those are the only names you need on the cert.

And if you want internal clients to hit an internal IP instead of looping out and back in through a router, you can additionally set up split DNS. Does that make more sense?
0
 

Author Comment

by:Computech
ID: 39666879
I think so!?  Let me repeat it back to make sure I'm understanding correctly.

So, I should go into my virtual directories and change the internal URLs to the same thing externally.  Then, go and create a new zone in my DNS for my external domain so I can internally resolve my URLs.

Is this the recommended way to do this?  I don't mind doing this, but I just want to make sure I'm not going to run into anymore issues with these certificates, by doing this.
0
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 39667091
Yep
0
 

Author Comment

by:Computech
ID: 39667660
Okay, so I tried what you suggested and I'm still getting a certificate error saying, because its still looking at the internal name.  Anything else that I need to change?  We've opened and closed Outlook a few times to see if it was something that needed to be propagated, but no joy.
0
 
LVL 57

Expert Comment

by:Cliff Galiher
ID: 39667750
Make sure you'd updated all URLs, including OA, offline address books, EWS, and auto discover. Outlook's connectivity tests are also helpful in troubleshooting
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
ID: 39668397
There are quite a few bits that need to be changed. I have recorded them all, including a script to change them for you in one go here: http://semb.ee/hostnames

The one most people miss is the Autodiscover URI on set-clientaccessserver

Simon.
0
 

Author Closing Comment

by:Computech
ID: 39676234
Once I followed the prescribed steps, the error in Outlook went away.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

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

Suggested Solutions

Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
how to add IIS SMTP to handle application/Scanner relays into office 365.

828 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