Universal groups add more data to the global catalog.
Always, because it has no restrictions when the domain functional level is •Windows 2000 native or Windows Server 2003: You can convert universal groups to domain local groups or to global groups
Global catalog...The global catalog provides quick object access to universal groups and UPNs within an AD forest.
AGUDLP A - Add users to G - Global groups based on job functions. Add global groups to U - Universal groups for forestwide use. Add universal groups to DL - Domain Local groups that are matched to a particular resource. Assign P - Permissions to the domain local group.
Use Universal distribution groups in a multiple-domain environment. The membership of universal distribution groups is replicated to each global catalog server in each domain
Group scopes determine where in the Active Directory forest a group is accessible and what objects can be placed into the group. Windows Server 2003 includes three group scopes: global, domain local, and universal.
Global groups dude. this is what my book says "global groups can contain user accounts, computer accounts, and/ or other global groups ONLY from within the same domain as the global group. domain local groups can contain user accounts, computer accounts, global groups, and universal groups from ANY domain, IN ADDITION to other domain local groups from the same domain. u take ur pick.....
The group scope that can contain global groups from multiple domains is the universal group. Universal groups are designed to aggregate users and groups from multiple domains within a forest, allowing for more flexible permissions and resource access across different domains. They can include global groups from any domain within the same Active Directory forest, making them useful for organizations with complex structures.
Universal groups can be used anywhere in the same Windows forest. They are only available in a Native-mode enterprise. Universal groups may be an easier approach for some administrators because there are no intrinsic limitations on their use. Users can be directly assigned to Universal groups, they can be nested, and they can be used directly with access-control lists to denote access permissions in any domain in the enterprise. Universal groups are stored in the global catalog (GC); this means that all changes made to these groups engender replication to all global catalog servers in the entire enterprise. Changes to universal groups must therefore be made only after a careful examination of the benefits of universal groups as compared to the cost of the increased global catalog replication load. If an organization has but a single, well-connected LAN, no performance degradation should be experienced, while widely dispersed sites might experience a significant impact. Typically, organizations using WANs should use Universal groups only for relatively static groups in which memberships change rarely
Global groups dude. this is what my book says "global groups can contain user accounts, computer accounts, and/ or other global groups ONLY from within the same domain as the global group. domain local groups can contain user accounts, computer accounts, global groups, and universal groups from ANY domain, IN ADDITION to other domain local groups from the same domain. u take ur pick.....
universal groups are not present in the win2000 mixed mode the forest level needs to be win2003 for it to work. Universal groups can be used anywhere in the same Windows forest. They are only available in a Native-mode enterprise. Universal groups may be an easier approach for some administrators because there are no intrinsic limitations on their use. Users can be directly assigned to Universal groups, they can be nested, and they can be used directly with access-control lists to denote access permissions in any domain in the enterprise. Universal groups are stored in the global catalog (GC); this means that all changes made to these groups engender replication to all global catalog servers in the entire enterprise. Changes to universal groups must therefore be made only after a careful examination of the benefits of universal groups as compared to the cost of the increased global catalog replication load. If an organization has but a single, well-connected LAN, no performance degradation should be experienced, while widely dispersed sites might experience a significant impact. Typically, organizations using WANs should use Universal groups only for relatively static groups in which memberships change rarely
global to universal,universal of global, global to domain local