Creating a Deployment Roadmap
Creating a Deployment Roadmap |
|
Because Windows 2000 Server is a multipurpose network operating system that is designed with distinct — but integrated — features that can be deployed incrementally, there are numerous technology dependencies that you must consider as you plan your deployment. The following examples illustrate some of these technology dependencies.
Your Active Directory structure and Domain Name System (DNS), along with your infrastructure plans for Windows Internet Name Service (WINS), Dynamic Host Configuration Protocol (DHCP), network protocols, files, printing, streaming media, and other bandwidth-intensive applications, must be designed to accommodate business requirements and IT capabilities. If your business needs dictate numerous subsidiaries, and roaming or remote access users, then you need to consider organizational units, Group Policy, security, and IntelliMirror technologies. If you want to offer secure intranet or extranet capabilities, then IP Security (IPSec), and PKI are important components to design.
If you will deploy Windows 2000 Professional as your primary operating system for desktops and laptops, then you might want to consider installation options, MultiLanguage capabilities, security, Active Directory, and other change and configuration management technologies. Finally, if you are in a heterogeneous environment that includes network operating systems other than Windows NT or Windows 2000, you will need to consider interoperability and coexistence options.
You might be planning to deploy Active Directory in a geographically dispersed environment where centralized IT management is difficult because of low-speed WAN links, and there is great potential for compromising a stable and secure connection. Yet, you also might have a business requirement for a stable, secure, and common e-mail and collaboration system across different operating companies, including geographically remote sites. You need to consider the relationships between Active Directory and Exchange Server 5.5 directory service, with Group Policy, IPSec, and virtual private networks (VPNs). Plan to use the Active Directory Connector (ADC) to keep your data synchronized with your Exchange directory.
You must also consider DNS design, especially if you have multiple organizations, subsidiary operating units each with its own Internet domain name, domain and tree structures, security requirements, and different network operating system or IT standards. DNS design is especially important if groups other than the Windows 2000 team are responsible for the DNS namespace, as with many UNIX-centric IT organizations.
If you require a common e-mail standard and a common directory, but your organization does not use Exchange Server 5.5, then you might need to implement Exchange Server 5.5 prior to deploying Windows 2000 so you can synchronize with Active Directory using ADC. Alternately, you could scale back this goal until you have completed your Windows 2000 deployment and then deploy the next version of Exchange.
Another example might take place in a user location with limited support but excellent connectivity where local client installation was maintained manually in the past. Using Remote OS Installation and IntelliMirror technologies, you now have an opportunity for remote installation and troubleshooting without needing on-site support.
You will find more information on technology dependencies in each of the technical planning chapters in this book. Remember, each feature that you want to deploy needs to have its own design so that it can be formally tested in both lab and pilot environments.