Microsoft Exchange Server for Windows 2000: Planning, Design, and Implementation

Designs can be drawn up by a small team of skilled people. Deployments require the attention and involvement of many more trained individuals if they are to be successful. A number of important steps come into focus as we head towards an implementation. A pilot deployment helps to prove the design and training is needed to get everyone equipped to deal with the new challenges posed by Exchange 2000. Third-party products need to be identified, tested, and integrated into the new environment.
The final steps of a project are when you see the value of good design. Everything fits into place and works as a coordinated whole. If it doesn't, the design is wrong and needs to be fixed, and the real value of a solid pilot deployment is to identify the small problems that could go wrong in a big way if they were exposed to a full deployment.
Conducting a pilot is inevitably easier for some companies than others. The easiest pilots are those for companies that already have a well-designed Exchange organization up and running. Obviously, Exchange 2000 is the natural and evolutionary path for previous versions and some knowledge and infrastructure can be brought over to work with Exchange 2000. However, Exchange 2000 is very different than previous versions. It is a mistake to think that everything can be taken over seamlessly, as we discuss later in the section on training.
If you already have deployed Exchange 5.5, the length of...