Microsoft Exchange Server
Are you or anyone you know still running Exchange 2000? If so, you should
know that when you do finally get around to upgrading; Exchange 2010 and
Exchange 2000 cannot exist in the same Forest/Org. The oldest version of
Exchange that can co-exist with Exchange 2010 is Exchange 2003 SP2.
If you want to upgrade from Exchange 2000, you’ll have to upgrade in stages.
Because Exchange 2000 supports an in-place upgrade to Exchange 2003, this method
is going to be the easiest way to prepare for Exchange 2010. Exchange 2003
requires more resources than Exchange 2000, but for the purpose of a migration
project; it won’t be around for long anyway, so you might be able to upgrade
resources in place. Otherwise, you’ll have to allocate hardware for Exchange
2003 only to get rid of it when you go to Exchange 2010. If you are forced to
take this approach, I would recommend virtual hardware for Exchange 2003 as it
is now supported.
We can get into detailed guidance another time, but here are some scenarios
for upgrading to Exchange 2010 from an earlier version of Exchange. I am not
including Exchange 5.5 in this post because I hope nobody is still running it!
Also for the below guidance, I am assuming everything is running the latest
Exchange service pack and/or rollup.
| Current Platform* | Getting to Exchange 2010 |
| · Exchange 2000· On Win 2000
· With 2000 AD |
1. Do an in-place upgrade to Exchange 20032. Don’t bother upgrading the Operating System
3. Prepare for an AD 2003 upgrade (scenario 2) 4. Do an in-place upgrade of at least one domain controller to AD 2003 5. Migrate [UPDATE – NOTE THAT THIS REQUIRES ADDITIONAL CHANGES IN ACTIVE DIRECTORY. THE STEPS IN THIS ARTICLE ARE TO GET YOU TO EXCHANGE 2003 ONLY. THE HYPERLINK HERE INCLUDES THE REMAINING STEPS.] |
| · Exchange 2000· On Win 2003
· With 2000 AD |
· How did you get here? This is not a supported configuration! |
| · Exchange 2000· On Win 2000
· With 2003 AD |
1. Did you first prepare for mangled attributes? If not, examine scenario 3.2. Do an in-place upgrade to Exchange 2003
3. Migrate [UPDATE – NOTE THAT THIS REQUIRES ADDITIONAL CHANGES IN ACTIVE DIRECTORY. THE STEPS IN THIS ARTICLE ARE TO GET YOU TO EXCHANGE 2003 ONLY. THE HYPERLINK HERE INCLUDES THE REMAINING STEPS.] |
| · Exchange 2000· On Win 2003
· With 2003 AD |
· How did you get here? This is not a supported configuration! |
*When I list an AD version, I am also assuming /forestprep has not yet been run for a future version of AD.
The Microsoft Transporter Suite is a free tool that can be used to migrate IMAP, POP and Domino email content into an Exchange 2007 environment. I’ve been working with the Transporter Suite on a few projects over the past year, and am pleased to see it is now finally a multi-threading application (for POP/IMAP only)! This should resolve a lot of the performance issues I (and others) have been having.
More info here:
|
Release month/year |
Updates |
|
February 2009 |
· Added support for multi-threading of POP/IMAP migrations. · Improved stability of the POP/IMAP migration tool. · Improved support for different POP/IMAP Administrator authentication models (support for proxy authentication). · Improved support for IMAP forward/reply flags. · Added support for additional POP/IMAP servers. |
|
June 2008 |
· Improved handling of in-line images in migrated messages. · Improved handling of unread messages in migrations from University of Washington IMAP server implementations. · Fixed an issue whereby attachments could get misnamed. · General enhancements for the Transporter user interface. |
The tool also has several updates for Domino:
|
Release month/year |
Updates |
|
February 2009 |
· Removed the Transporter Application Analysis node · Added support for Windows Server 2008 and Domino R8 · Improved migration of recurring meetings and updated recurring meetings · Improved stability of Free/Busy service · Improved support for multidomain Active Directory topologies · Improved support for moving Domino Groups · Improved support for moving anniversaries |
|
June 2008 |
· Improved migration of meeting messages from Lotus Notes · Fixed an issue whereby user attributes for contacts in Active Directory may be lost after contacts are migrated from Lotus Notes · Better handling of proxy addresses to avoid spurious duplicate address warnings |
Download the tools here.
1. Use this link to generate the cmdlet structure for your PowerShell command. This will output the CSR https://www.digicert.com/easy-csr/exchange2007.htm
2. Send the CSR to a trusted provider.
a. Entrust is my favorite but GoDaddy is the cheapest. Other UCC vendors include DigiCert and Comodo.
b. More detail here: http://support.microsoft.com/kb/929395
c. You’ll notice VeriSign isn’t on this list. They DO offer UCC but only if you spend thousands in their managed PKI program…
3. While Windows Mobile support all of these vendors, understand that the iPhone and Palm may not.
a. Palm doesn’t support UCC at all, but you can get around that by using a UCC / SAN cert anyway, and just putting the OWA/ActiveSync FQDN as the primary name in the certificate. It just can’t read the alternate fields.
4. Once you get the certificate back, rename it to a .cer file
5. Open PowerShell again and type: Import-ExchangeCertificate c:\filename.cer
6. Type Get-ExchangeCertficate to see your new cert at the top of the list. Copy the thumbprint to the clipboard.
7. Then type: Enable-ExchangeCertificate –Thumbprint xxx –services iis, smtp, pop, imap, um
a. Don’t list all the services unless the role is actually installed on the box itself
b. If you intend to use the same cert on multiple servers, understand that may break your agreement with the Certificate Authority, and you have to import the key pair on the 2nd server before step 6 works.
Misc:
Mike Crowley's Whiteboard 