Skip to main content

security and distribution groups?, Local- Global- Universal Groups

 In Microsoft Active Directory, what are security and distribution groups?


In Microsoft Active Directory, when you create a new group, you must select a group type. The two group types, security and distribution, are described below:
  • Security: Security groups allow you to manage user and computer access to shared resources. You can also control who receives group policy settings. This simplifies administration by allowing you to set permissions once on multiple computers, then to change the membership of the group as your needs change. The change in group membership automatically takes effect everywhere. You can also use these groups as email distribution lists.
  • Distribution: Distribution groups are intended to be used solely as email distribution lists. These lists are for use with email applications such as Microsoft Exchange or Outlook. You can add and remove contacts from the list so that they will or will not receive email sent to the distribution group. You can't use distribution groups to assign permissions on any objects, and you can't use them to filter group policy settings.

-----------------------------------------------------------------------------------------------------------------

Groups

Distribution Groups -- Used for email. Useful for programs such as MS Exchange.

Security Groups - Used to secure file/folders, printers, etc.

Local - Stored on the local SAM ( Local Computers )
Domain Local - Stored on Domain Controllers.
Global Groups - Gives you a greater group scope.
Universal - Gives you an even broader group scope.

Windows 2000 Mixed can contain:

Domain Local -- At the same time they can contain Accounts ( Any user/computer account ), and global groups. Access to the same domain.
Global groups - They can contain Accounts ( user/computer accounts ). Access to Any domain
Universal - N/A not applicable at this DFL. Access to any domain

Windows 2000 Native or Windows 2003 DFL can contain:

Domain Local - Accounts ( users/computers ), Domain local Groups ( same domain ) , global groups, and universal groups.

Global Groups - Accounts ( users/computers from the same domain ), Global groups ( same domain )

Universal Groups - Accounts ( users/computers ), Global Groups, and Universal Groups.


Group Conversion

Domain Local - You can convert it to Universal ( A Domain Local group must already contain a Domain Local group in order for the conversion to take place )
Global Group - You can convert it to Universal ( A Global group must already contain a Global group in order for the conversion to take place )
Universal Group - You can convert it to either Domain Local, or Global Group.

Group Nesting

Same Domain

Start By adding Users to Global Groups. At the same global groups can be nested within Domain Local Groups, and Univerisal groups.

Global Groups can also be nested within Global Groups in the same domain.

Cross-Domain Group nesting

Global Groups can be nested within Domain Local groups, or within another Universal Group in the other domain.

Global Groups cannot be nested across domains. You cannot take a Global Group from proprofs.local, and nest it within another global group in proprofs.com.

You cannot take a user/computer account from one domain, and nest it within a global group in another domain.

Global Groups can be used to grant access to files/folders ( NTFS Permissions) in the same domain, and in a different domain as well.

Domain Local groups can accept anything, except for Domain Local groups from another domain. It accepts user accounts from the same domain, and a different domain as well. A global/universal group from the same domain/different domain can also be nested within a Domain Local group.

Resources - Domain Local Groups can only access resources on the domain on which it resides. For example a domain Local group Named HelpDesk on the proprofs.local domain can only access resources on that domain, and not on proprofs.com

Universal Groups - Accept user/computer accounts from the same domain, and a different domain as well. A global group can also be nested within a Universal Group ( from the same/different domain(s) )

Note: You cannot take a Domain Local Group, and nest it within a Universal Group ( from the same/different domain(s) )

A Universal Group can be nested within another Universal Group in the same domain, and in different domains as well. They can also be nested within Domain Local Groups in the same domain, and in different domains as well. Universal Groups can never be a member of Universal Groups.

Resources - It can be used to access resources ( NTFS Permissions ) on the same domain, and in different domains as well.

One benefit of Universal Groups is that they list its members on the Global Catalog. Whenever a change was made to a Universal Group, it updates the membership of all its members in the Global Catalog, causing a lot of unnecessary traffic between GCs ( windows 2000 )

Windows 2003 solves the aforementioned problem by updating the membership of only the affected member. In other words, it does not replicate all the accounts in the Universal group, only the one you made changes to. ( Note: This new feature is only available if the Domain Functional Level ( DFL ) is on Windows 2003 )


================================================== ===


Good Luck! 

Comments

Popular posts from this blog

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.

Device expanded/shrank messages are reported in the VMkernel log for VMFS-5

    Symptoms A VMFS-5 datastore is no longer visible in vSphere 5 datastores view. A VMFS-5 datastore is no longer mounted in the vSphere 5 datastores view. In the  /var/log/vmkernel.log  file, you see an entry similar to: .. cpu1:44722)WARNING: LVM: 2884: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device shrank (actual size 18424453 blocks, stored size 18424507 blocks) A VMFS-5 datastore is mounted in the vSphere 5 datastores view, but in the  /var/log/vmkernel.log  file you see an entry similar to: .. cpu0:44828)LVM: 2891: [naa.6006048c7bc7febbf4db26ae0c3263cb:1] Device expanded (actual size 18424506 blocks, stored size 18422953 blocks)   Purpose This article provides steps to correct the VMFS-5 partition table entry using  partedUtil . For more information see  Using the partedUtil command line utility on ESX and ESXi (1036609) .   Cause The device size discrepancy is caused by an incorrect ending sector for the VMFS-5 partition on the ...