Thanks to guys from Telnetport25 I was able to finish my SSL certificate migration for my new Windows Server 2008 virtual machine running a Exchange 2007 SP1 installation.
My work log:
- Logon on the old Windows Server 2003 hosting the OWA front-end role
- Start MMC and add the Certificate Snap-In; choose the Computer Account.
- Go to Personal/Certificates and locate the SSL certificate assigned to IIS for SSL encryption. Right click ; All Tasks and choose export. Choose the appropriate options like the certificate path; assign password and save the PFX file to "My Documents"
- Copy the PFX file to your Windows Server 2008 Client Access Server
- Logon on the Windows Server 2008 and add the Certificate Snap-In to a new MMC console for the Computer Account
- Go to Personal/Certificates; right click; All Tasks and choose Import.
- Locate the PFX file; enter the password and make sure you check "Mark this key as exportable" to enable future migrations of the SSL certificate.
- Place the certificate in the Personal Store
- Open the certificate and go to Details tab. Locate the Thumprint field and select Value with mouse; press CRTL-C to copy the data.

- Paste the value in Notepad and replace the "SPACE’ with CRTL-H. In the Find what field press space on the keyboard and click Replace All
- Copy the Thumbprint
- Start the Exchange Management Shell and run the Enable-ExchangeCertificate cmdlet
- Type IIS as Services and paste the copied data from Notepad to Thumbprint
- Start Exchange Management Console and go to Server Configuration / Client Access / Select the server and open owa from Outlook Web Access tab
- Type External URL of the SSL certificate and DNS. E.g. https://webmail.domain.tlk
- Click OK and you are finished to test the configuration.
- Start IE and test your OWA role. Review your NAT and Firewall rules also.
Related links:
2007,
2008,
certificate,
exchange,
export,
import,
migrate,
move,
outlook web access,
owa,
server,
ssl,
Windows
You have a Windows File Server and you want to migrate the windows shares. What options do you have to complete this job? A) recreate them or B) migrate them from ServerA to ServerB. Sometimes option A is the only one you have but in most cases you want to keep those Windows Shares available as they were before and using some kind of script would be nice. Microsoft published a KB125996 article based on following procedures and my option B:
- Reinstall Windows over an existing installation (a clean install, not an upgrade).
- Move all of your data drives from one server to another.
- Install Windows to another folder or drive on a computer that already has Windows installed.
I am performing a clean installation of a application server which has several file shares associated for application functionality. I don’t want to recreate them manually and I am using the next steps to complete this task.
a) Verify the shares you want to migrate and the drive letter location is the same on both servers.

b) Export the Shares key from HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares
reg export HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Shares LanmanServer.reg

c) Make sure the user and group still exist in the domain! When migrating from DomainA to Domain B make sure you recreate all users and groups. Copy LanmanServer.reg to ServerB and import the registry file.
reg import LanmanServer.reg
net stop server & net start server

Reboot the file server and verify the share with “net share” command; also check the System Eventlog for any warnings or errors.