Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 601
  • Last Modified:

Exchange 2007 certificates

Hello,
   I am trying to configure exchange 2007 (one single standalone server) to use the Private CA I just set up on my windows 2008 box. I am new to Windows Active Directory Certificate Services and am not sure how to configure exchange to use the certificate server instead of the self-signing one. My goal is to set up outlook anywhere for a client who does not want to buy a provider-based cert. Any help is appreciated. Thanks.
0
Matt Coughlin
Asked:
Matt Coughlin
  • 7
  • 6
1 Solution
 
flaphead_comCommented:
so i do this .. you need to add the internal cert authority to the trust cert authorities on each client machine
0
 
Matt CoughlinAuthor Commented:
ok, I am new to internal certs... I need to add a cert from the CA to each machine needing Outlook anywhere?

How do I add certs to machines?
0
 
JaredJ1Commented:
Ok, if the new CA that you have built is a member of the domain you don't need to add certificates to new computers. Computers that are members of the domain will trust the new CA automatically.

What you will need to do is get Exchange to create a new certificate request, and then submit that request to the CA, download the certificate and install it on the Exchange server, and then tell Exchange to use it.

All of these steps can be found in this Technet chapter:

http://technet.microsoft.com/en-us/library/bb310795(EXCHG.80).aspx
0
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.

 
Matt CoughlinAuthor Commented:
If my internet domain is mail.domain.net (domain name provided by an external source) and my internal AD domain is mail.domain.local what should I put as the subject name in the request so that the client computer can access exchange from outside or inside the network?
0
 
JaredJ1Commented:
Internally your clients won't be using Outlook anywhere, they'll just be using MAPI so you need to set it to work for external access, so use 'mail.domain.net'
0
 
Matt CoughlinAuthor Commented:
hmm how would you set that up in outlook? When you choose to connect to an exchange server you would put in mail.domain.local.

then when you travel outside the network you need to change it to mail.domain.net?
0
 
JaredJ1Commented:
You shouldn't have to configure it in Outlook if you have Autodiscover working. Assuming that it's not working you would need to configure a profile as you would normally pointing to your internal server name. Then go into 'More Settings', Click the 'Connection' tab, then click 'Exchange Proxy Settings', then enter in the external name settings. See the screenshot....
Outlook Account Settings
0
 
Matt CoughlinAuthor Commented:
ok so here is the code I am typing in exchange shell

New-ExchangeCertificate -generaterequest -subjectname "dc=local,dc=domain,cn=mail.iconintl.local" -domainname mail.domain.net,mail.domain.local,autodiscover.domain.net,autodiscover.domain.local -PrivateKeyExportable $true -path c:\certrequest.txt
0
 
JaredJ1Commented:
Looks fine.
0
 
Matt CoughlinAuthor Commented:
ok I have the request file, how do I submit it to the Windows CA?
0
 
JaredJ1Commented:
1. Navigate to https://<Internal PKI CA>/certsrv
2. Choose Request a Certificate.
3. Choose Advanced Certificate Request.
4. Choose Submit a certificate request by using a base-64-encoded CMC or PKCS #10 file, or submit a renewal request by using a base-64-encoded PKCS #7 file.
5. Select Web server as the certificate template.
6. Copy the text from the cert request file and paste into the window.
7. Submit the request.
7. Click to download the certificate and save it as c:\cert.cer
8. Import the certificate file using the following command from the EMC:

Import-ExchangeCertificate -path C:\cert.cer

9. Check the new certificate is listed as expected using:

get-exchangecertificate | fl

This will give you the thumbprint of the new certificate which is needed in the next step.

10. Allow the cert to be used for IIS and SMTP with the following command:

Enable-ExchangeCertificate -Thumbprint <thumbprint> -Services "IIS,SMTP"

0
 
Matt CoughlinAuthor Commented:
Alright, everything seems to be working. I am just dealing with an issue with clients connecting externally. It keeps asking for the password and never accepts it. I am looking into it, but it seems to have something to do with the check box "Only Connect to Proxy Servers that have this principal name in the certificate."

(connected internally)
everything works as expected

(connected externally)
When I uncheck the box and restart outlook, it connects just fine to Exchange. Eventually outlook resets this setting and I will have to change it again.

any ideas?
0
 
JaredJ1Commented:
My apologies, I think I made an error when i looked at your certificate request. If you look at the certificate it probably states that it is issued to: mail.domain.local, it should be issued to mail.domain.net
Request a new certificate:

New-ExchangeCertificate -generaterequest -subjectname "dc=local,dc=domain,cn=mail.domain.net" -domainname mail.domain.net,mail.domain.local,autodiscover.domain.net,autodiscover.domain.local -PrivateKeyExportable $true -path c:\certrequest.txt

Once installed this should work.
0
 
Matt CoughlinAuthor Commented:
Oh that worked like a charm! Thanks so much!
0

Featured Post

Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

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