UCC, SSL certificates

I have a 2010 exchange server that is acting as a mail server.  All of our users are getting certificate errors.  We are looking to purchase a SANS UCC certificate and would like any suggestions on a good place to buy one.  Also want it to be as easy possible, to just install it and have it work.

Would we need an SSL certificate if users are accessing the site via the web.? https://mail.domain.com/owa

Example of what I was thinking to have on the cert.
1. mail.example.com
2. autodiscover.example.com
3. webmail.example.com
4. exchange1.example.local
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.

where to buy ? Godaddy.com digicert.com .... all are good all will work

if you web access is mail.domain.com then

Subject should be mail.domain.com
SAN autodiscover.domain.com,exchange1.domain.local
Glen KnightCommented:
You need to use the certificate wizard in the Exchange 2010 management console to request the certificate, when you have done that you will be provided with a file.  Open the file and copy and paste the contents into the website you plan to purchase the certificate from.

As for where to buy them from, if you check my profile by clicking on my name you will see a website listed there.
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-2k10 (example)
#Internal FQDN: EX-2k10.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-2k10,EX-k10.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. You can use Fix My Network Wizard in the SBS 2008 Console to renew self-signed certificate.


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
there is no need to use powershel to generate SCR in exchange 2010 it can be done from the GUI
Glen KnightCommented:
I am interested to know which parts if the post you have accepted resolved this issue for you?

Since the post is talking about self signed certificates and at the end of the post even mentions SBS2008.

It is clearly another generic post that is posted for any SSL related question and not a direct response to your question.
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

From novice to tech pro — start learning today.