Exchange 2000 to 2007

[janaya]

I have an Exchange 2000 server that we are finally upgrading. We will upgrade the server hardware and software.

The current server runs our Active Directory, Domain Controller and Exchange 2000 and uses Server 2000. Will I be able to move all these services to the new Server 2003 server, and can I do all this offline and cutover into production when the new server is ready?

We are a small company and don't have a lot of servers so housing the applications on multiple servers helps us to reduce cost, as does having us do this transition in house.

I am a telecom guy by design and have never suggested to anyone that I am anything but a common users in the Networking world so any help would be appreciated.

Thanks

John

 

[baddos]

It would probably be better just to go to exchange 2010 since it's released now.

 

[58sniper]

Exchange 2010 requires Windows 2008 (preferably 2008 R2). And never put Exchange on a domain controller. Regardless of the version.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[PaulGillespie]

The procedure that you are suggesting can be very complex and difficult.You can get yourself ito a mess and the company will be looking to you to fix it.

If you are a small company (how many users?) it may be best to get new hardware and start from scratch. This would be the easiest way for you to do it without complications. You're also leaving your existing infrastructure intact should anything go wrong.

If you are runing multiple servers, maybe you should look into Hyper-V server virtualisation. Might save you money on buying all new hardware for your apps.

 

[joepc]

Consider imaging the server and performing this transition in a test environment before you actually do this.

This can be a complex procedure as PaulGillespie stated, and I would consider bringing in a Consultant.

 

[SimonDavis]

You're doing more than installing a new version of Exchange there. Nothing wrong with being the telecoms guy, but even in a small setup that's a pretty daunting task even for a reasonably experienced admin.

Throwing a curved ball in here, how big are your existing message stores? I did a similar upgrade a few years ago, and in the end I just did a new install of the new Exchange box, Created the users from new and copied the message stores to .pst files, then manually moved them to the exchange store later, using Outlook. It might sound unfeasible, but in fact it only took about 4 hours to move about 75,000 messages.

That really was a small setup though - there were 9 of us.

During the whole process I always kept the option of putting the old server back online at very short notice.

 

[charlie2908]

I would just migrate to 2007 and not 2010 for the minute, as I managed to download a corrupt version of 2010 from Microsoft and spent hours trying to fix it. In the end I rebuilt the box and settled with 2007.

 

[janaya]

Thanks so much for all the response, and please continue as this can only help me in the long run.

I wish we could afford to have this done by a fully qualified Network/IT Admin, but my boss is trying to stay ahead of the current economic environment by scaling back all types of operating expenses. Such is the life we live in.

I did think about building a complete new environment and then cutting it into service, rather than take down the old exchange server and I will most likely move in that direction.

We have already rebuilt the Spam/Virus Management Server, and to be honest, I think we did an alright job, as we are getting better reporting out of it now. We get email admin notices on Spam and Virus Quarantines that we were not getting before and we have not had to restart the system multiple times per week.

I think if we just move in "baby steps" we should be able to work up a complete upgrade to our Network Environment for about $3500.00 with new servers and desktops (At least new to us).

I mean, we have machines still running Windows 2000 with Office 2000 and loss of time because of software incompatibility is becoming unbearable.

Thanks for all your support here. As stated, I am not a Network Admin, nor to I ever try to pass myself off as one. I'm a phone guy, past 18 years, but with small business downsizing I have had to add a few more hats to my wardrobe to keep things going.

If I don't get a chanse to respond before next week, have a Merry Christmas, a Great Holiday Season and a Happy and Safe New Years.

John

 

[WANguy2k]

I recently migrated from 2003 to 2007. Here's what you need to do it. Make sure you follow it step-by-step. Good luck!

http://tinyurl.com/kjvx9s

 

[charlie2908]

WANguy2k
Sadly this will not help janaya right away. If you read janaya's original post you would see that his exchange server is a 2000 exchange. You cannot migrate for 2000 to 2007, you have to go to 2003 first and then up to 2007. That is why we are suggesting a fresh build and that the data be imported via .pst on each client.

 

[58sniper]

Virtualize a 2003 environment and move to it. Rip out the 2000 stuff, add the 2010 stuff, and move to that. Then rip out the 2003 stuff.

The user count isn't mentioned here, but .pst methods are rarely a good method.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[WANguy2k]

You're right, my bad. I went from 2003 to 2007, however I don't believe you need to go from 2000 to 2003 before going to 2007. Read on:

http://tinyurl.com/36nz6g

 

[58sniper]

But why go to an outdated version of the product? 2010 is MUCH more appealing. Lower storage costs, lower HA costs, lower TCO, higher ROI.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[Zelandakh]

I'd upgrade the 2000 to 2003 in place - next, next, next...

Then swing to 2007 using Neil's article referenced above. 2010 would be just as good, depending on how much you like going with new products that you've not seen.

2010 needs a hardware load balancer for multi server though and without a user count you can't tell if you need more than one box.

 

[janaya]

User count is low. We have only 10 actual users. As with any small business, some individuals like to keep emails that are 5 - 6 years old, but don't like to archive.

 

[PaulGillespie]

Any reason why you are not considering a small business server?