Commonly Used The Special Identity Groups

By Author: Jasmine
Total Articles: 286
Comment this article

Guidelines for group nesting include the following:
Minimize levels of CompTIA A+ Practical Application nesting Tracking permissions and troubleshooting becomes more complex with multiple levels of nesting. One level of nesting is the
most effective to use.
Document group membership to keep track of permissions assignments Providing documentation of group membership can eliminate the redundant assignment of user accounts to groups and reduce the likelihood of accidental group assignments.

Members include all users who log on without supplying a user name and password.
Members include all users whose identities were authenticated when they logged on. This group does not include the Guest account even if the account has a password.
Members include all users who are logged on to the system through a dial-up connection.
Members include all domain controllers in a forest of CompTIA A+ Essentials domains. Controllers
Supports directory replication functions. The only member should be a domain user ...
... account used to log on to the Replicator services of the domain controller. Do not add the accounts of actual users to this group.
Where can you create groups?
With the necessary permissions, you can create groups in any domain in the forest, in an OU, or in a container you have created specifically for groups.
2.What is deleted when you delete a group?
When you delete a group, you delete only the group and remove the permissions and rights that are associated with it. Deleting a group does not delete the user accounts that are members of the group.
3.What Active Directory components can be members of groups?Members of groups can include user accounts, contacts, other groups, and computers.
4.In what domain functional level is changing the group scope allowed? What scope changes are permitted in this domain functional level?
You can change the scope of domains with the domain functional level set to Windows 2000 native or Windows Server 2003. The following scope changes are permitted:
Global to universal, as long as the group is not a member of another group having global scope
Domain local to universal, as long as the group being converted does not have another group with a domain local scope as its member
Universal to global, as long as the Network+ certification group being converted does not have another universal group as its member Universal to domain local