Each week, you\'ll have to post on at least three separate days to the Discussio

Question

Each week, you'll have to post on at least three separate days to the Discussion. Each post should be of a high quality. Your first post should be made by Wednesday. By Sunday, 11:59 PM (Mountain), make high-quality posts on three separate days in the Discussion.

This week’s discussion focuses on the concept Active Directory and how it is used to centrally create and manage resources in a domain. Active Directory is a giant database listing all objects in a domain. Common objects are organizational units (OUs), user accounts, computer objects and groups. In this discussion forum we will focus on managing Active Directory objects. Please respond to all of the following prompts after completing this week’s reading assignments:

Susan is studying for her Microsoft Server certification exam and has some questions about Active Directory Domain Services.

How would you describe Active Directory Domain Services?
How do you think an administrator benefits from implementing Active Directory Domain Services?
When and what tasks can you delegate administrative control of an OU?

Explanation / Answer

Active Directory Domain Services (AD DS) stores directory knowledge and manages communication between users and domains, as well as user logon processes, authentication, and directory searches. A full of life Directory domain controller could be a server that's running AD DS. Active Directory Domain Services (AD DS) could be a server role in Active Directory that permits admins to manage and store info regarding resources from a network, in addition as application knowledge, in very distributed information. A server running Active Directory Domain Services (AD DS) is termed a site controller. It authenticates and authorizes all users and computers in a very Windows domain kind network—assigning and implementing security policies for all computers and putting in or change software system. A Windows domain could be a variety of a network within which all user accounts, computers, printers and alternative security principals, area unit registered with a central information placed on one or additional clusters of central computers referred to as domain controllers. Authentication takes place on domain controllers. The first reason to make structure units is to distribute body tasks across the organization by authorization body management to alternative directors. Delegation is very necessary once a decentralized body model is developed. Delegation of administration is that the method of centrifugal the responsibility for managing structure units from a central administrator to alternative directors. The flexibility to ascertain access to individual structure units is a vital security feature in Active Directory. Users will management access to all-time low level of a corporation while not having to make several active directory domains. A Windows domain could be a variety of a network within which all user accounts, computers, printers and alternative security principals, area unit registered with a central information placed on one or additional clusters of central computers referred to as domain controllers. Authentication takes place on domain controllers. Everyone United Nations agency uses computers among a site receives a singular user account which will then be assigned access to resources among the domain. Beginning with Windows 2000, Active Directory is that the Windows element answerable of maintaining that central information. The thought of Windows domain is in distinction therewith of a workgroup within which every pc maintains its own information of security principals. Authority delegated at the positioning level can probably span domains or conversely, might not embody targets within the domain. Authority delegated at the domain level can have an effect on all objects within the domain. Authority delegated at the structure unit level will have an effect on that object and every one of its kid objects or simply the article itself. You can use structure units (OUs) to delegate the administration of objects, like users or computers, among the OU to a delegated individual or cluster. To delegate administration by victimization associate degree OU, place the individual or cluster to that you're authorization body rights into a gaggle, place the set of objects to be controlled into associate degree OU, and so delegate body tasks for the OU thereto cluster. Active Directory Domain Services (AD DS) allows you to manage the executive tasks which will be delegated at a awfully elaborate level. As an example, you'll assign one cluster to possess full management of all objects in associate degree OU; assign another cluster the rights solely to make, delete, and manage user accounts within the OU; and so assign a 3rd cluster the correct solely to reset user account passwords. You’ll build these permissions monogenic in order that they apply to any OUs that area unit placed in sub trees of the initial OU. Default OUs and containers area unit created throughout the installation of AD DS and area unit controlled by service directors. It’s best if service directors still management these containers. If you would like to delegate management over objects within the directory, produce further OUs and place the objects in these OUs. Delegate management over these OUs to the acceptable knowledge directors. This makes it potential to delegate management over objects within the directory while not ever-changing the default management given to the service directors. The forest owner determines the extent of authority that's delegated to associate degree OU owner. This may vary from the flexibility to make and manipulate objects within the OU to solely being allowed to manage one attribute of one form of object within the OU. Granting a user the flexibility to make associate degree object within the OU implicitly grants that user the flexibility to control any attribute of any object that the user creates. Additionally, if the article that's created could be a instrumentation, the user implicitly has the flexibility to make and manipulate any objects that area unit placed within the instrumentation. the first reason to make structure units is to distribute body tasks across the organization by authorization body management to alternative directors. Delegation is very necessary once a decentralized body model is developed. Delegation of administration is that the method of centrifugal the responsibility for managing structure units from a central administrator to alternative directors. The flexibility to ascertain access to individual structure units is a vital security feature in Active Directory. Users will management access to all-time low level of a corporation while not having to make several active directory domains. Authority delegated at the positioning level can probably span domains or conversely, might not embody targets within the domain. Authority delegated at the domain level can have an effect on all objects within the domain. Authority delegated at the structure unit level will have an effect on that object and every one of its kid objects or simply the article itself.

Related Questions

Navigate

• Browse (All)
• Browse E
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.