For the past few weeks, we've been taking a close look at deploying Windows NT with Windows 2000 in mind. For a link to the first part of this series, see the Resources section at the end of this article. By creating a model of your existing system and application environment, you can set up such a pilot program and test your Windows 2000 strategy. The existing system upon which your model is based must include servers, workstations, and application software. For workstations, you'll want to test the behavior of Windows 2000 deployment services such as Remote OS Installation and IntelliMirror for the types of machines and applications you run on your network.
Servers are more complex.
It's best to start by making a copy of your existing primary domain controller on a standalone machine and attempting to upgrade it to a Windows 2000 server with Active Directory. Next, take copies of domains from your network and try to merge them onto the same Windows 2000 server. Establishing your current domain structure under the new environment should test the limits of your server hardware. The new directory system is touted as being more scalable than its predecessor, but your domain structure may be so complex that it pushes the new system to its limit. If this is the case, consider remodeling your domain structure on paper and testing it against the new server.