Friday, November 12, 2004
Part 1: Introduction to Active Directory
Active Directory: you can't buy it, you can't touch or hold it, and yet most Windows 2000-based networks rely on it to function properly. So what exactly is Active Directory? It's a simple question, but the answer becomes more complex the more you discuss it. In simplest terms, Active Directory is a service (or group of services) that runs on Windows 2000 servers. More specifically, you could say that Active Directory is a "directory service" for Windows 2000. This service is used to store and organize information about the network and the resources that are available on the network. More importantly, Active Directory can be used to control access to network resources.
Microsoft refers to Active Directory as the way to "provide a consistent way to name, describe, locate, access, manage, and secure information about resources" on a Windows 2000 network.
Directory services are not a new concept: Novell's NDS instantly comes to mind when thinking about directories, as well as DNS, and even Microsoft Exchange has had its own directory for years.
If you are familiar with Windows NT (3.x & 4.x) domains, you will be able to appreciate the features that Active Directory brings to a Windows network. Active Directory brings a hierarchical structure to the domain concept of earlier versions of NT. In comparison, it's like using a single pile of lose papers on your desk as a way of organizing your work (NT domains), compared to placing those loose papers in labeled hanging folders in a filing cabinet (Active Directory).
As much as Active Directory adds in functionality, organization and user experience, it also adds much more complexity in design, implementation and support. Planning was important when implementing an NT 4 domain; it is imperative when implementing Active Directory.
Over the next few features, we will begin looking at some of the benefits of using Active Directory, as well as some of the properties of Active Directory, best practices for implementing it, technologies that it depends on (e.g.: DNS), and technologies that depend on it (e.g.: Group Policy).
Microsoft refers to Active Directory as the way to "provide a consistent way to name, describe, locate, access, manage, and secure information about resources" on a Windows 2000 network.
Directory services are not a new concept: Novell's NDS instantly comes to mind when thinking about directories, as well as DNS, and even Microsoft Exchange has had its own directory for years.
If you are familiar with Windows NT (3.x & 4.x) domains, you will be able to appreciate the features that Active Directory brings to a Windows network. Active Directory brings a hierarchical structure to the domain concept of earlier versions of NT. In comparison, it's like using a single pile of lose papers on your desk as a way of organizing your work (NT domains), compared to placing those loose papers in labeled hanging folders in a filing cabinet (Active Directory).
As much as Active Directory adds in functionality, organization and user experience, it also adds much more complexity in design, implementation and support. Planning was important when implementing an NT 4 domain; it is imperative when implementing Active Directory.
Over the next few features, we will begin looking at some of the benefits of using Active Directory, as well as some of the properties of Active Directory, best practices for implementing it, technologies that it depends on (e.g.: DNS), and technologies that depend on it (e.g.: Group Policy).
# posted by e247net : 1:09 AM
