TABLE OF CONTENTS | 6.1 | Plan a strategy for placing global catalog servers. |
| 6.1.1 | Evaluate network traffic considerations when placing global catalog servers. |
| 6.1.2 | Evaluate the need to enable universal group caching. |
| 6.2 | Implement an Active Directory service forest and domain structure. |
| 6.2.1 | Create the forest root domain. |
| 6.2.2 | Create a child domain. |
| 6.2.3 | Create and configure application data partitions. |
| 6.2.4 | Install and configure an Active Directory domain controller. |
| 6.2.5 | Set an Active Directory forest and domain functional level based on requirements. |
| 6.2.6 | Establish trust relationships. Types of trust relation-ships include external trusts, shortcut trusts, and cross-forest trusts. |
It can be said with little disagreement that Active Directory was the most significant change between Windows NT 4.0 and Windows 2000. Active Directory gave administrators the flexibility to configure their network to best fit their environment. Domain structures became much more understandable and flexible, and the task of managing users, groups, policies, and resources became less overwhelming.
As wonderful a tool as Active Directory appeared to be, it did not come without its own set of issues. Failing to properly plan an Active Directory structure prior to implementation became a nightmare for many administrators who were used to simple implementation processes for older operating systems such as Windows NT 4.0. There were also questions revolving around the best migration path from Windows NT 4.0 to Windows 2000 Active Directory: Do you upgrade? Do you rebuild your domain from scratch? What are the pros...
