Here is the scenario , we are doing migration from Exchange 2003 to Exchange 2010. We have existing certificate called mail.abc.org and we wish to move this over to Exchange 2010.
I think this will be much common thing in these type of migrations. I found out supper easy is not to kill yourself to try to share the existing cert and the URL being used to access the webmail. For instance if you are using webmail.abc.com
|webmail.abc.com =Valid Cert = Exchange-2003 Server|
And as soon as you moved first user on Exchange 2010 , accessing Existing URL wont work for the user on Exchange 2010. Here is what I have done couple times to get around this type of issues and make migration pretty seamless to end users.
I purchased new cert and called it owa.abc.com
|owa.abc.com=New Valid Cert=Exchange 2010|
I configured this cert on the E210 server and told costumer everyone who gets migrated on E210 will use this link to access their webmail. This made my job supper easy and at the end of the migration I export the cert from E03 imported into E210 and done with migration.
- STEP 1: Export Certificate and Private Key from the IIS 6.0 server
Create an MMC Snap-in for Managing Certificates:
1. Start > run > MMC
- Go into the Console Tab > File > Add/Remove Snap-in
- Click on Add > Click on Certificates and click on Add
- Choose Computer Account
- Choose Local Computer
- Close the Add Standalone Snap-in window.
- Click on OK at the Add/Remove Snap-in window
- Open Certificates Console Tree
- Go to Personal
- Right click Certificates
- Choose ALL TASKS
- Select Import to start the Certificate Import Wizard
- Click Browse
- Locate the .pfx file
- Click Open
After this is completed rest of the work is supper easy go to EMC and drill down to server configuration , you will see the certificate there , just assign services to this certificate to finish the work