Resetting Self-Signed Certs in Exchange 2007/SBS 2008

Good Day Experts,

I have a fairly challenging issue here that im hoping you guys will be able to help with.

Platform:

-      Windows 2008 SBS
-      Exchange 2007
-      Self-Signed Certificates

I have taken over management of this particular server from a previous IT and it seems to be a great mess!

The issue I’m having is around Certs, Active Sync (for iPhones) and RPC.

The server seems to have valid self-signed certificates installed but only for remote.domain.com. OWA works ok if you bypass the Cert error, installing it into Trusted Root Container doesn’t seem to work, I guess the Certificate is for remote.domain.com and not mail.domain.com.

They will need Hosts for the following:

-      Vpn.domain.com (for VPN)
-      Mail.domain.com (for OWA)
-      Remote.domain.com (For Autodiscover)

How do I go about removing these certs and installing new ones (Self-Signed for the moment). Im fairly new to Exchange 2007 so a noddy guide would be GREAT :)

Let me know any info you may need to help further.
LVL 1
dt3itsteamAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

shauncroucherCommented:
You should hav 1 certificate attached to IIS, with Subject Alternative names.

See: http://blog.sembee.co.uk/archive/2008/05/30/78.aspx

You will need at least

commonname.domain.com
autodiscover.domain.com
server.local
server

Shaun
0
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
You need a SAN or UC certificate.  I recommend GoDaddy  or www.domainsforexchange.net

http://blog.sembee.co.uk/archive/2008/05/30/78.aspx

One of the most important aspects of a successful Exchange messaging deployment is how you configure your SSL certificates for securing client communication to your Exchange infrastructure. This is because all communication between Outlook clients and the Autodiscover service  endpoint, in addition to communication between the Outlook client and Exchange services, occurs over an SSL channel. For this communication to occur without failing, you must have a valid SSL certificate installed. For  a certificate to be considered valid, it must meet the following criteria:

- The client can follow the certificate chain up to the trusted root.
- The name matches the URL that the client is trying to communicate with.
- The certificate is current and has not expired.

Remember,  the cert request needs to be generated by Exchange using PowerShell.
 http://technet.microsoft.com/en-us/library/aa998327.aspx

When you get the response back from the CA, use the import-certificate command to process  and enable it for SMTP, IIS, etc.
http://technet.microsoft.com/en-us/library/bb124424.aspx







0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Satya PathakLead Technical ConsultantCommented:
Suppose we want to create a UCC self-signed certificate. We will require the following names:

#NETBIOS name of Exchange: EX-2k7 (example)
#Internal FQDN: EX-2k7.abc.local (example)
#External FQDN (Public name): webmail.abc.com (example) (use nslookup/ping to verify the external FQDN)
#Autodiscover name: autodiscover.abc.com (example)
#SubjectName: cn=webmail.abc.com (example)

In EMS, run the following command to generate the new self-signed certificate:

New-ExchangeCertificate -FriendlyName "SelfSigned Cert" -SubjectName "cn=webmail.abc.com" -DomainName EX-2k7,EX-k7.abc.local,webmail.abc.com,autodiscover.abc.com -PrivateKeyExportable $True

Next enable the certificate with Enable-ExchangeCertificate cmdlet. Enable atleast IIS and SMTP.

Enable-ExchangeCertificate -Thumbprint xxxxxxxxxxxxxxx -Services POP,IMAP,SMTP,IIS

Next verify certificate has been installed using EMS/IIS Manager or both. (Sometimes you may have to remove the certificate and then install/enable certificate again).

Some important points:

1. If you are creating a self-signed certificate, it is always better to create one that has all the subject alternative names specified above. This will prevent any certificate security warnings related to name mismatch. If you are creating single-name self-signed certificate, you would have to modify internal URIs of multiple virtual directories as explained in KB940726. The other benefit of multiple SANs is avoiding event 12014 and similar events.

2. Autodiscover for non-domain joined machines will work only after record is created in external DNS

3. You will have to install the certificate in the trusted root on client machines else you will receive a certificate warning. On Vista machines, you will have to run IE with elevated privileges to be able to install the certificate when you open OWA.

4. You can use group policy to install the certificate in trusted root (applicable only to domain joined machines). Copy to file the self-signed certificate (ideally in .p7b format) and then edit the default domain policy and import the certificate into "Computer Settings\Windows Settings\Security Settings\Public Key Policies\Trusted Root Certification Authorities". No user intervention is required once you do this. (Users would have to install the certificate themselves on non-domain joined machines).

5. SBS2008 Information: When you install SBS 2008, setup Internet Address wizard uses self-issued certificate by default. You will find it is "Issued to" "external FQDN" of the server and "Issued by" would be "Internal FQDN-CA" (SBS setup configures CA by default). When the wizard generates the self-signed certificate, it also generates a Certificate distribution package. The package (Install Certificate Package.zip) is located under one of the default shares named Public (C:\Users\Public). Another point to remember about SBS2008 is that the default certificate is single-name certificate and if you create a new one with multiple subject alternative names using the procedure above, you will receive a warning while enabling SMTP on the certificate. This warning can be ignored. You can verify availability of STARTTLS verb using Telnet.

6. In Exchange 2007 SP2, validity of self-signed certificate has been increased to 5 years (earlier it was one year)

7. You can use Fix My Network Wizard in the SBS 2008 Console to renew self-signed certificate
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

dt3itsteamAuthor Commented:
Right, i have bought a UCC SSL certificate from GoDaddy.

Ive imported and enabled it and when i browse to https://mail.domain.com/owa it works perfectly.

Working with 3rd party Certs is about 200% easier, so i thank you for all your suggestions!

SatyaPathak: that information will be invaluable to me for another couple of servers so i will hang on to that! Thanks very much!

The issue im now having is Active Sync for iphone syncing. When i check the URL ActiveSync is using in EMC

Internal URL:https://remote.domain.com/Microsoft-Server-ActiveSync
External URL:https://remote.domain.com/Microsoft-Server-ActiveSync

Outlok anywhere is enabled and set to mail.domain.com (basic authentication set)

Do i need to change the URL for Active SYnc, and if so how? Surely its not just changing that External URL field, that just seems way to simple!
0
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
It is that simple... you need to change the URI in exchange with ActiveSync properties or get a new cert that includes remote.domain.com
0
dt3itsteamAuthor Commented:
mmm strange!

my cert does include remote.domain.com.

Still doesnt work tho!
0
Shreedhar EtteCommented:
Hi,

Go to https://www.testexchangeconnectivity.com/ and perform a ActiveSync test and post result.

---------
Shree
0
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Should work..
0
dt3itsteamAuthor Commented:
Hi all,

Turns out that i had to reset all the authentication types on the virtual directories to Basic Authentication, they were all mixed up for some reason.

All working ok now!
0
dt3itsteamAuthor Commented:
Easiest way to end result
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.