Exchange 2000 to Exchange 2007 Transition

We plan to upgrade from Exchange 2000 to Exchange 2007.  We currently have 2 Win2k3 domain controllers, but my Exchange 2000 server is on a Win2k server.  My domain of course is Win2k mixed.  There are about 60 users.

We heavily use calendaring and public folders.  We also have a Blackberry Professional Server v4.1.4.3.

Could someone give me some ideas as to what I need to look for in going forward with this transition?  I believe we will put it on a new Win2k3 server unless it is better to have it on Win2k8.  Are there any gotchas on calendaring, public folders or Blackberry that I need to be aware of?

Any comments or suggestions would be very helpful.



Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

I've migrated from Exchange 2003 to Exchange 2007, but not from 2000.  It appears that the migration is the same, though.  First, I would recommend going with Windows 2k8 since you have to use a 64-bit OS anyway.  Might as well go ahead and get the latest OS since you don't really save any compatability issues considering you are doing a 64-bit OS.  As far as the migration is concerned, make sure you are very careful to prepare the domain properly beforehand.  I had a failed installation the first time, so I carefully documented the steps the second time to make sure I knew exactly what to do in the future.  I emailed these to a friend for his migration and he was able to get Exchange 2007 installed without error.

Here goes:

Add the administrator account to Schema Admins and Enterprise Admins. Logged off and back on.  Installed IIS and PowerShell and reboot.
Log into Windows Powershell by right-clicking on the shortcut, then run as Administrator.
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
ServerManagerCmd -i RSAT-ADDS

Run from the Exchange media /PrepareAD /PrepareLegacyExchangePermissions (should be handled by the prepareAD, but run it anyway just to be safe) /PrepareSchema (should be handled by the prepareAD, but run it anyway, just to be safe) /PrepareAllDomains  

Once these are completed, you should be ready to do the install.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Rajith EnchiparambilOffice 365 & Exchange ArchitectCommented:
1. It is better to have it on Windows 2008, as 2003 is very old now, considering the fact that 2008 R2 is on its way.

2. You need to introduce an exchange 2007 server into the existing network, but will need to change it to Windows 2000 native mode, which can have 2000 exchange servers

3. Follow the article series. It's for 2003, but most of it still applies for 2000. It will give you a good picture.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.