Comments on: Export an Exchange Server 2010 Certificate to Exchange 2003 http://exchangeserverpro.com/export-an-exchange-server-2010-certificate-to-exchange-2003 Microsoft Exchange Server News - Tips - Tutorials Fri, 10 Feb 2012 02:36:56 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Jason Benway http://exchangeserverpro.com/export-an-exchange-server-2010-certificate-to-exchange-2003#comment-4944 Jason Benway Fri, 05 Aug 2011 22:50:05 +0000 http://exchangeserverpro.com/?p=1377#comment-4944 Thanks for the reply!! We created and imported the cert today. I just haven't flipped the DNS yet. Thanks for the reply!! We created and imported the cert today. I just haven’t flipped the DNS yet.

]]> By: Paul Cunningham http://exchangeserverpro.com/export-an-exchange-server-2010-certificate-to-exchange-2003#comment-4941 Paul Cunningham Fri, 05 Aug 2011 22:35:24 +0000 http://exchangeserverpro.com/?p=1377#comment-4941 Hi Jason, import it anywhere that will be accepting SSL connections for the name(s) in the cert. The 2003 FE will be accepting SSL connections to the legacy name, so yes, import the cert there. Hi Jason, import it anywhere that will be accepting SSL connections for the name(s) in the cert. The 2003 FE will be accepting SSL connections to the legacy name, so yes, import the cert there.

]]> By: Jason Benway http://exchangeserverpro.com/export-an-exchange-server-2010-certificate-to-exchange-2003#comment-4927 Jason Benway Wed, 03 Aug 2011 20:54:31 +0000 http://exchangeserverpro.com/?p=1377#comment-4927 Very nice post, if I have a front end server for OWA 2003, do I need to import it on that server as well? thanks,jb Very nice post, if I have a front end server for OWA 2003, do I need to import it on that server as well?

thanks,jb

]]> By: George V http://exchangeserverpro.com/export-an-exchange-server-2010-certificate-to-exchange-2003#comment-4866 George V Fri, 22 Jul 2011 03:58:08 +0000 http://exchangeserverpro.com/?p=1377#comment-4866 Thanks for this, can't believe this is not explained anywhere on MS Technet. One additional step if you already have a certificate on the Exchange 2003 server - is to run the Cert wizard in IIS and Replace the existing cert with the new imported one. Thanks for this, can’t believe this is not explained anywhere on MS Technet.

One additional step if you already have a certificate on the Exchange 2003 server – is to run the Cert wizard in IIS and Replace the existing cert with the new imported one.

]]> By: Alan Temperly http://exchangeserverpro.com/export-an-exchange-server-2010-certificate-to-exchange-2003#comment-4313 Alan Temperly Mon, 04 Apr 2011 18:19:57 +0000 http://exchangeserverpro.com/?p=1377#comment-4313 OK so when I create the SAN cert on Exchange 2010 For OWA: Intranet = serverexchange2010.domain.com Internet = mail.domain.com Legacy: Intranet = legacy.serverexchange2003.domain.com Internet - legacy.mail.domain.com So legacy.serverexchange2003.domain.com will point to the owa link on exchange 2003 server instead of exchange 2010? OK so when I create the SAN cert on Exchange 2010

For OWA:
Intranet = serverexchange2010.domain.com
Internet = mail.domain.com

Legacy:
Intranet = legacy.serverexchange2003.domain.com
Internet – legacy.mail.domain.com

So legacy.serverexchange2003.domain.com will point to the owa link on exchange 2003 server instead of exchange 2010?

]]> By: Paul Cunningham http://exchangeserverpro.com/export-an-exchange-server-2010-certificate-to-exchange-2003#comment-4311 Paul Cunningham Mon, 04 Apr 2011 10:58:31 +0000 http://exchangeserverpro.com/?p=1377#comment-4311 Alan, Exchange 2010 works best with SAN certificates. Trying to use a single name SSL certificate with Exchange 2010 is frankly a nightmare. You only need to export the SAN certificate to the Exchange 2003 server if you plan to run in co-existence for a period of time. The point of doing this is so that the Exchange 2003 server has a valid certificate installed with the legacy namespace as one of the subject alternate names. OWA and RPC should continue to work as long as the SAN certificate includes whatever name your users use to connect to those services. The legacy name needs to be resolvable both internally and externally. Alan, Exchange 2010 works best with SAN certificates. Trying to use a single name SSL certificate with Exchange 2010 is frankly a nightmare.

You only need to export the SAN certificate to the Exchange 2003 server if you plan to run in co-existence for a period of time. The point of doing this is so that the Exchange 2003 server has a valid certificate installed with the legacy namespace as one of the subject alternate names.

OWA and RPC should continue to work as long as the SAN certificate includes whatever name your users use to connect to those services.

The legacy name needs to be resolvable both internally and externally.

]]> By: Alan Temperly http://exchangeserverpro.com/export-an-exchange-server-2010-certificate-to-exchange-2003#comment-4294 Alan Temperly Wed, 30 Mar 2011 16:59:19 +0000 http://exchangeserverpro.com/?p=1377#comment-4294 I currently have a exchange 2003 with standard SSL with Certificate Authority. Do I need to remove this Standard SSL and create a SAN SSL on the Exchange 2010 server and them export the exchange 2010 cert. to exchange 2003 server? If I remove the standard SSL what happens to my OWA and RPC withun HTTPS connections? When I export SAN SSL to exchange 2003 for co-existence can I only add the legacy name in my internal DNS zone? I currently have a exchange 2003 with standard SSL with Certificate Authority. Do I need to remove this Standard SSL and create a SAN SSL on the Exchange 2010 server and them export the exchange 2010 cert. to exchange 2003 server?

If I remove the standard SSL what happens to my OWA and RPC withun HTTPS connections?

When I export SAN SSL to exchange 2003 for co-existence can I only add the legacy name in my internal DNS zone?

]]>