Active Directory Primer
- Evolution of Directory Services
- Active Directory Development
- Active Directory Structure
- Active Directory Components
- Domain Trusts
- Organizational Units
- Groups in an Active Directory Environment
- Active Directory Replication
- DNS in Active Directory
- Active Directory Security
- Active Directory Changes in Windows .NET Server 2003
- Best Practices
Chapter 4: Active Directory Primer
In This Chapter
Evolution of Directory Services
Active Directory Development
Active Directory Structure
Active Directory Components
Groups in an Active Directory Environment
Active Directory Replication
DNS in Active Directory
Active Directory Security
Active Directory Changes in Windows .NET Server 2003
The heart and soul of the Windows .NET Server 2003 network infrastructure resides in Active Directory, Microsoft's directory services implementation. Active Directory was devised to fill the directory services void in the Windows world and to serve as a platform for future integration of Microsoft technologies. A full understanding of the structure of Active Directory is vital to the understanding of the Windows .NET Server 2003 environment as a whole.
In addition to the overall operating system enhancements, Windows .NET Server 2003 expands upon the capabilities of Active Directory, adding the ability to rename domains, improvements in administrative tools, compression optimizations, and other long-awaited enhancements to the capabilities of the Active Directory environment.
This chapter describes an overview of directory services in general and specifically focuses on the overall development of Active Directory as an enterprise directory service. In addition, the basic components and functionality of Active Directory in Windows .NET Server 2003 are summarized.
Evolution of Directory Services
Directory services have existed in one form or another since the early days of computing to provide basic lookup and authentication functionality for enterprise network implementations. A directory service provides detailed information about a user or object in a network, much in the same way that a phonebook is used to look up a telephone number for a provided name. For example, a user object in a directory service can store the phone number, e-mail address, department name, and as many other attributes as an administrator desires.
Directory services are commonly referred to as the white pages of a network. They provide user and object definition and administration. Early electronic directories were developed soon after the invention of the digital computer and were used for user authentication and to control access to resources. With the growth of the Internet and the increase in the use of computers for collaboration, the use of directories expanded to include basic contact information about users. Examples of early directories included MVS PROFS (IBM), Grapevine's Registration Database, and WHOIS.
Application-specific directory services soon arose to address the specific addressing and contact-lookup needs of each product. These directories were accessible only via proprietary access methods and were limited in scope. Applications utilizing these types of directories were programs such as Novell GroupWise Directory, Lotus Notes, and the Unix sendmail /etc/aliases file.
The further development of large-scale enterprise directory services was spearheaded by Novell with the release of Novell Directory Services (NDS) in the early 1990s. It was adopted by NetWare organizations and eventually was expanded to include support for mixed NetWare/NT environments. The flat, nongranular structure of NT domains and the lack of synchronization and collaboration between the two environments led many organizations to adopt NDS as a directory service implementation. It was these specific deficiencies in NT that Microsoft addressed with the introduction of Active Directory.
The development of the Lightweight Directory Access Protocol (LDAP) corresponded with the growth of the Internet and a need for greater collaboration and standardization. This nonproprietary method of accessing and modifying directory information that fully utilized TCP/IP was determined to be robust and functional, and new directory services implementations were written to utilize this protocol. Active Directory itself was specifically designed to conform to the LDAP standard.
Original Microsoft Directory Systems
Exchange 5.5 ran its own directory service as part of its e-mail environment. In fact, Active Directory took many of its key design components from the original Exchange directory service. For example, the Active Directory database uses the same Jet database format as Exchange 5.5, and the same types of utilities are necessary to run maintenance on the Active Directory database.
Several other Microsoft applications ran their own directory services, namely Internet Information Server and Site Server. However, each directory service was separate from the others, and integration was not very tight between the different implementations.
Key Features of Active Directory
Five key components are central to Active Directory's functionality. As compatibility with Internet standards has become required for new directory services, the existing implementations have adjusted and focused on these areas:
TCP/IP CompatibilityUnlike some of the original proprietary protocols such as IPX/SPX and NetBEUI, TCP/IP was designed to be cross-platform. The subsequent adoption of TCP/IP as an Internet standard for computer communications has propelled it to the forefront of the protocol world and essentially made it a requirement for enterprise operating systems. Active Directory and Windows .NET Server 2003 utilize the TCP/IP protocol stack as their primary method of communications.
Lightweight Directory Access Protocol SupportThe Lightweight Directory Access Protocol has emerged as the standard Internet directory protocol and is used to update and query data within the directory. Active Directory directly supports LDAP.
Domain Name System (DNS) SupportDNS was created out of a need to translate simplified names that can be understood by humans (such as http://www.microsoft.com) into an IP address that is understood by a computer (such as 188.8.131.52). The Active Directory structure supports and effectively requires DNS to function properly.
Security SupportInternet standards-based security support is vital to the smooth functioning of an environment that is essentially connected to millions of computers around the world. Lack of strong security is an invitation to be hacked, and Windows .NET Server 2003 and Active Directory have taken security to greater levels. Support for IPSec, Kerberos, Certificate Authorities, and Secure Sockets Layer (SSL) encryption is built into Windows .NET Server 2003 and Active Directory. In addition, there has been a recent major push at Microsoft to further secure all aspects of its software to prevent embarrassing security meltdowns such as those caused by the Code Red and Nimbda viruses.
Ease of AdministrationAlthough often overlooked in powerful directory services implementations, the ease in which the environment is administered and configured directly affects the overall costs associated with its use. Active Directory and Windows .NET Server 2003 are specifically designed for ease of use to lessen the learning curve associated with the use of a new environment. In addition, Windows .NET Server 2003 includes numerous administrative improvements over Windows 2000, in the form of additional command-line tools for scripting, "headless" management capabilities, software restriction policies, and an enhanced GUI based on Windows XP.