Summary

 <  Day Day Up  >  

Migrating to Exchange 2003 from a feature/function standpoint just makes sense. If you are in the mode of trying to decide between Exchange 2000 and Exchange 2003, go to Exchange 2003. HP was an early adopter of Exchange 2003, and it has been the most stable version of the product to date. There are loads of features, functions, and deployment scenarios that just can't be covered in a single chapter, so definitely do some research at the HP and Microsoft Web sites, and make use of the books mentioned early in the chapter. Remember too that any planning you've already done to move to Exchange 2000 will still be valid if you choose to move to Exchange 2003, with very few exceptions.

As with any migration and deployment, you really need to spend a lot of time in the planning phases of the project. I just can't say that enough! After the planning is complete, document and test your migration process before moving into your pilot and, after you've ironed everything out, full production. All of this is straightforward, so don't short-circuit the planning in an effort to speed things up. In the long run, you will cause more delay by having to deal with unknowns that would have otherwise been worked through. And, of course, if you aren't up to speed on the technology, bring in a professional, like HP, to help you get moving in the right direction.

 <  Day Day Up  >  


Windows Server 2003 on Proliants. Deployment Techniques and Management Tools for System Administrators
Windows Server 2003 on Proliants. Deployment Techniques and Management Tools for System Administrators
ISBN: B004C77T6A
EAN: N/A
Year: 2004
Pages: 214

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net