Ad Dbs Case

739 Words2 Pages

The most obvious and common use case for AD DS is to provide authentication for users on the network. Authentication is the process by which a system verifies that the user is who he claims to be, for example, by typing in a username and password. When a user sits down and signs in to the computer, that computer verifies the credentials entered against AD DS and receives a token in exchange. As the user tries to perform actions or access resources on the network, the AD DS token indicates what permissions and restrictions the user has. Objects are the specific items being catalogued in AD DS. Common objects found in a directory are users, computers, printers, folders, and even files. These objects are grouped into containers, usually organizational units, which in turn are grouped into higher order containers themselves. An object is made up of a collection of attributes which are key-value pairs of information. An example of an attribute key would be "Given Name," and every object in the directory would have a different value for that attribute. AD DS is dynamic and extensible, which means that not all objects share the same attributes, and as an administrator we can …show more content…

Any object in the directory that has children objects is known as a container. Forests, trees, and domains are all specialized types of containers, although not usually referred to as such. More common objects like users and computers can also have child objects and consequently can also be containers, although that's not typically how they're used. Containers are used to provide structure and separation to the objects in a directory. A company may have thousands of user objects in its directory, but it wouldn't be very useful to have them all lumped into one list. Containers can break them up by geographic region, organizational type, or even physical location within a

Open Document