How to move an SSL certificate between Exchange servers

In order to use Secure Sockets Layer (SSL) for secure communications between servers, a certificate provided by a valid certificate authority is required.

If you're creating a new instance of an Exchange server and want to use SSL on that new server as well, you'll need to move an existing SSL certificate to it.

One possible scenario involves promoting a back-end Exchange server to a front-end Exchange server -- the back-end server would need to have the front-end server's certificate loaded onto it.

The exact process for transferring a certificate isn't difficult, but there are complications that can arise due to the nature of SSL certification and server naming.

First, let's go over the process itself:

1. Go to the server with the SSL certificate and open the Internet Information Services Manager.
2. Expand the tree of Web sites to expose the Default Web site. Right-click on it and select Properties.
3. On the Directory Security tab, click on Server Certificate, and export the certificate to .PFX format.
4. AFTER putting the new server into place, copy the .PFX-formatted certificate file to the target server.
5. On the target server, go through the same actions: Open IIS Manager -> Default Web Site -> Properties -> Directory Security -> Server Certificate.
6. This time, select "Import a certificate from a .PFX file," and provide the file you exported.

SSL should now be enabled on that computer.

When moving a certificate from machine to another in this fashion, the most important thing to keep in mind is that the name of the server -- i.e., th...

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Exchange Server Administration Tips Remove Exchange 2003 objects from AD to install Exchange 2010 Don'ts for optimal Exchange 2007 mailbox server efficiency Is your Exchange 2007 hub transport server healthy? Avoid Outlook 2007 performance issues during repairs Developing an Exchange 2007 server role DR plan How DSAccess service improves Exchange Server 2007 reliability An introduction to the Exchange Remote Connectivity Analyzer tool Monitor Exchange 2007 with disk- and RPC-related counters DPM 2007 replica inconsistencies in Exchange databases Track Exchange 2007 mailbox server health using database counters Exchange Security Tips How to install Forefront Security for Exchange Server Is full email encryption the solution to Exchange security? Lock down direct file access and protect OWA users Controlling spam in Exchange 2007 at the edge transport server level When to use a self-signed certificate with Exchange Server 2007 Obtaining and verifying SSL certificates in Exchange Server How file-level antivirus software can harm your Exchange Server Understanding Exchange Server 2007 SP1 mobile security settings Which ActiveSync authentication method is best for your mobile device? Why you should secure Exchange 2007 using administrative policies User Authentication for Microsoft Outlook and OWA Lock down direct file access and protect OWA users Obtaining and verifying SSL certificates in Exchange Server Top 5 Outlook Web Access (OWA) tips of 2008 Manage user rights and access to Outlook Web Access (OWA) mailboxes Create a secure Microsoft Outlook Web Access (OWA) redirect page Why does a security alert pop up when accessing Outlook Web Access? OWA won't load after applying Exchange 2007 SP1 security patch Minimize remote and mobile Outlook Web Access (OWA) security risks How to improve Outlook Web Access (OWA) security Alleviate Outlook Web Access (OWA) email attachment security issues

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary Vouch by Reference (VBR)  (SearchExchange.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

e external fully-qualified domain name -- should be exactly the same for both servers.

If the certificate is tied to a specific machine name (the certificate's properties will tell you what the machine name is), and if it's using the server's internal BE name, then you'll need to make sure that any external DNS pointers are updated to indicate the new server.

Otherwise, people from the outside will never be able to access the newly certified server through SSL. Instead, they'll be redirected to the old machine. For external services that depend on SSL, like OWA, this is doubly important.

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter.

MEMBER FEEDBACK TO THIS TIP

What if the internal domain name of the back-end server is different from the public domain name of the front-end server?
—Jim H.

******************************************

If the servers do not have the same name, then I strongly suspect you cannot move the SSL certificate. You will probably need to generate a new SSL certificate for the back-end server, one with the proper name.

The best approach is to keep the SSL certificate on the front-end server and use RPC over HTTP (not HTTPS) to access the back-end server per Microsoft's article "How to configure the back-end server to act as a target for the RPC proxy server. "

The other approach is to generate a new SSL certificate specifically for the back-end server. Although -- from what I've read -- it's best to keep the SSL certificate on the front-end server, use RPC over HTTP to talk to the back-end server, and encrypt all traffic between the front-end and back-end servers using IPsec.

Exchange Server security expert Richard Luckett has another perspective on this issue via a slightly different topic: Securing a front-end certificate server.

I hope this helps!
—Serdar Yegulalp, tip author

Do you have comments on this tip? Let us know.

Related information from SearchExchange.com:

Please let others know how useful this tip is via the rating scale below. Do you have a useful Exchange Server or Microsoft Outlook tip, timesaver or workaround to share? Submit it to SearchExchange.com. If we publish it, we'll send you a nifty thank you gift.

Rate this Tip To rate tips, you must be a member of SearchExchange.com. Register now to start rating these tips. Log in if you are already a member. DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.