Please follow the data and description Active Directory In gen.pdf
- 1. Please follow the data and description : Active Directory : In general the Active Directory is abbrevated as AD and is a directory service that Microsoft developed for Windows domain networks. It is included in most of the available Windows Server operating systems as a set of processes and services. Considerations for designing a Active Directory : Before moving on directly to the planning ang implementation of the Active Directory we just need to get some major factors and their considerations into account so as to handle them perfectly. When we are designing the Active Directory network, it is important to use the four divisions (forests, domains, organizational units, and sites) to their maximum potential. Some of the important factors/considerations are described below : a) Active Directory elements : When designing an Active Directory, we need to be completely clear of what each element or part actually means and how it fits into the overall design. b) Active Directory forest : In general, the forest, in terms of Active Directory, basically means every domain, organizational unit, and any other object stored within its database. The forest is the absolute top level of the Active Directory infrastructure. We can have more than one forest in a company, which actually represent the high level security boundaries, and can therefore improve security between different business units or companies belonging to a single organization. The point behind the forest is that we have all our domains and domain tree within the organization itself contained within it. It is designed so that we can have a transitive links between all of the trees within one forest. c) Active Directory tree : A tree with reference to the Active Directory basically refers to a domain and all of its objects that merge into a single DNS name. d) Organizational Units and the Leaf Objects : In an Active Directory, Organizational Units abbrevated as OUs, which are also called as the Containers, and the Leaf Objects, which are of non-containing objects such as computer accounts and user accounts, are directly related. We can access the OUs and other objects through the Microsoft Management Console (MMC) or through the Users and Computers tool in the Administrative Tools. e) Active Directory Sites : The Sites and Services of the MMC is a utility that a lot of Windows administrators, particularly in smaller organizations, completely overlook. This part of Active Directory, however, is one of
- 2. the most crucial parts to understand and implement correctly. These Sites give us a very unique and well-designed approach to separate specific locations within the Active Directory. As the principle of an Active Directory domain is global-meaning that it is meant to be the same anywhere-it could present a problem for users who move from office to office, or for offices with network connections that are slow. Active Directory sites allow one to specify the IP address spaces or subnets used within your organization and, therefore, bring the structure of the network into Active Directory f) Group Policy Objects : These are a set of defined rules for settings about the user environment or the operating environment for a particular PC. They are treated as standalone objects because they can be linked to different OUs present in the Active Directory. This gives the user the flexibility of creating one set of rules and applying it to different OUs in different OU structures, making settings deployment much easier and administratively quick. g) Domain Planning : This could be considered as one of the first things that we need to plan for a network is the domain structure itself. It has to do with the major role of administrative control. As a general rule, we need to keep the number of domains to a minimum number whenever possible. If we really need department level divisions on the network that reflects the organization of the current business, then one needs to opt for the Organizational Units (OU) instead. As these are much more flexible and easier overall to manage than domains. So this makes the considerations to be accounted and makes sure of the factors that arouse and needs to be handled so as to maintain a perfect Active Directory in the Microsoft for a large branched Company/Organization. Hope this is helpful. Solution Please follow the data and description : Active Directory : In general the Active Directory is abbrevated as AD and is a directory service that Microsoft developed for Windows domain networks. It is included in most of the available Windows Server operating systems as a set of processes and services. Considerations for designing a Active Directory : Before moving on directly to the planning ang implementation of the Active Directory we just need to get some major factors and their considerations into account so as to handle them perfectly. When we are designing the Active Directory network, it is important to use the four
- 3. divisions (forests, domains, organizational units, and sites) to their maximum potential. Some of the important factors/considerations are described below : a) Active Directory elements : When designing an Active Directory, we need to be completely clear of what each element or part actually means and how it fits into the overall design. b) Active Directory forest : In general, the forest, in terms of Active Directory, basically means every domain, organizational unit, and any other object stored within its database. The forest is the absolute top level of the Active Directory infrastructure. We can have more than one forest in a company, which actually represent the high level security boundaries, and can therefore improve security between different business units or companies belonging to a single organization. The point behind the forest is that we have all our domains and domain tree within the organization itself contained within it. It is designed so that we can have a transitive links between all of the trees within one forest. c) Active Directory tree : A tree with reference to the Active Directory basically refers to a domain and all of its objects that merge into a single DNS name. d) Organizational Units and the Leaf Objects : In an Active Directory, Organizational Units abbrevated as OUs, which are also called as the Containers, and the Leaf Objects, which are of non-containing objects such as computer accounts and user accounts, are directly related. We can access the OUs and other objects through the Microsoft Management Console (MMC) or through the Users and Computers tool in the Administrative Tools. e) Active Directory Sites : The Sites and Services of the MMC is a utility that a lot of Windows administrators, particularly in smaller organizations, completely overlook. This part of Active Directory, however, is one of the most crucial parts to understand and implement correctly. These Sites give us a very unique and well-designed approach to separate specific locations within the Active Directory. As the principle of an Active Directory domain is global-meaning that it is meant to be the same anywhere-it could present a problem for users who move from office to office, or for offices with network connections that are slow. Active Directory sites allow one to specify the IP address spaces or subnets used within your organization and, therefore, bring the structure of the network into Active Directory f) Group Policy Objects : These are a set of defined rules for settings about the user environment or the operating environment for a particular PC. They are treated as standalone objects because they can be
- 4. linked to different OUs present in the Active Directory. This gives the user the flexibility of creating one set of rules and applying it to different OUs in different OU structures, making settings deployment much easier and administratively quick. g) Domain Planning : This could be considered as one of the first things that we need to plan for a network is the domain structure itself. It has to do with the major role of administrative control. As a general rule, we need to keep the number of domains to a minimum number whenever possible. If we really need department level divisions on the network that reflects the organization of the current business, then one needs to opt for the Organizational Units (OU) instead. As these are much more flexible and easier overall to manage than domains. So this makes the considerations to be accounted and makes sure of the factors that arouse and needs to be handled so as to maintain a perfect Active Directory in the Microsoft for a large branched Company/Organization. Hope this is helpful.