At this point in the analysis, your focus will be on the existing network operating system implementation. Some of the things you must determine at this point include:
Identifying the Existing Domain ModelA domain model determines how users and resources are currently organized. Determining the existing domain model will assist you in determining whether the current model can simply be upgraded or if a restructure of the existing model is required. If you're moving from Windows NT 4.0 to Windows Server 2003, there's a good chance that the existing domain model will change far more than if you're moving from Windows Server 2000 to Windows Server 2003. Windows NT 4.0 DomainsThere are four different domain models that you might come across in a Windows NT 4.0 environment:
The domain model currently in use will affect the Active Directory design. For example, Active Directory eliminates the need to create resource domains because organization units can be created instead, thus reducing the number of domains required. So, if an organization currently employs two master domains and three resource domains, the resource domains may be eliminated in the Active Directory design and configured as organizational units instead. By eliminating the resource domains, you reduce the number of domains from five to two. Windows Server 2000 DomainsBecause the Active Directory structure is the same between Windows Server 2003 and Windows Server 2000, there might be little restructuring involved when it comes to deploying Windows Server 2003 Active Directory as long as the present infrastructure meets all the current requirements. However, you still must assess the domain structure so that it can be incorporated into the new design. Identifying the Number and Location of Domain Controllers on the NetworkThose responsible for assessing the various aspects of the existing network infrastructure must also determine the number and location of domain controllers on the network. Because domain controllers are required for the logon process, they perform an important role on the network and you want to ensure domain controller availability for users. At this point, you want to determine how many domain controllers currently exist within the infrastructure. Doing so will assist in determining whether additional domain controllers are required to support the new Active Directory infrastructure. The placement of domain controllers must also be analyzed: Look at the physical network and determine where domain controllers currently exist. For example, if there are a number of branch offices, determine whether domain controllers currently exist in each of the locations. For performance purposes, the new Active Directory design might call for the addition of a new domain controller in various locations. Or you might also determine that it would be more appropriate to move a particular domain controller. In any case, many of these decisions cannot be made without first determining where domain controllers currently exist on the network. Identifying the Configuration Details of All Servers on the NetworkIf you're upgrading existing servers to Windows Server 2003, you need to document the current configuration of the servers. The servers will be configured in a way that meets the requirements of an organization. Part of the analysis process is to determine the configuration details and how they will be affected by upgrading to Windows Server 2003 (or even just by co-existing on a Windows Server 2003 based network). |