Active Directory Group Membership Recursively

A few days ago, I published an article on how to use the "Get-ActiveDirectoryGroupMember" function to get all the objects that are members of a group recursively. With this article, I'm going to show you how to use the "Get-ActiveDirectoryMembership" function in order to get all the groups that an object is a member of  recursively.

As always, my user account will be the test subject! When I get the groups that I am a member of, the list contains only the groups that I am a direct member.
PS C:\> $user = Get-ADUser cpolydorou

PS C:\> Get-ActiveDirectoryGroupMembership -Identity $user.DistinguishedName

Name                    DistinguishedName
----                    -----------------
Domain Admins           CN=Domain Admins,CN=Users,DC=LAB,DC=local
Enterprise Admins       CN=Enterprise Admins,CN=Users,DC=LAB,DC=local
NISAdmins               CN=NISAdmins,OU=Citrix,OU=Security Groups,OU=LAB,DC=LAB,DC=local
Organization Management CN=Organization Management,OU=Microsoft Exchange Security Groups,DC=LAB,DC=local
TestGroup3              CN=TestGroup3,OU=Test,OU=LAB,DC=LAB,DC=local

We notice a few more groups when adding the "-Recurse" parameter. Let's see why is that!
PS C:\> Get-ActiveDirectoryGroupMembership -Identity $user.DistinguishedName -Recurse

Name                                   DistinguishedName
----                                   -----------------
Administrators                         CN=Administrators,CN=Builtin,DC=LAB,DC=local
Denied RODC Password Replication Group CN=Denied RODC Password Replication Group,CN=Users,DC=LAB,DC=local
Domain Admins                          CN=Domain Admins,CN=Users,DC=LAB,DC=local
Enterprise Admins                      CN=Enterprise Admins,CN=Users,DC=LAB,DC=local
NISAdmins                              CN=NISAdmins,OU=Citrix,OU=Security Groups,OU=LAB,DC=LAB,DC=local
Organization Management                CN=Organization Management,OU=Microsoft Exchange Security Groups,DC=LAB,DC=local
SQL Server Administrators              CN=SQL Server Administrators,OU=SQL,OU=Security Groups,OU=LAB,DC=LAB,DC=local
TestGroup1                             CN=TestGroup1,OU=Test,OU=LAB,DC=LAB,DC=local
TestGroup2                             CN=TestGroup2,OU=Test,OU=LAB,DC=LAB,DC=local
TestGroup3                             CN=TestGroup3,OU=Test,OU=LAB,DC=LAB,DC=local

My account is a member of TestGroup1 and TestGroup2 because I'm a member of TestGroup3 and TestGroup3 is a member of TestGroup2 which in turn is a member of TestGroup1. Moreover, I'm a member of the SQL Server Administrators since the Domain Admins group is a member of this group.

And why is this helpful? By getting all the groups an object is a member of including nested groups, you are able to tell what permissions are granted to the object. Assuming of course that you assign and delegate permissions using security groups and not directly!

The "Get-ActiveDirectoryGroupMembership" function is available in my CPolydorou.ActiveDirectory module since version 1.5.1.

This module also contains the function "Test-ActiveDirectoryGroupMembership" which will query Active Directory and return whether or not an object is a member of a group, including nested groups.

Popular posts from this blog

Domain Controller Machine Password Reset

Image
On my lab environment, I've configured two Active Directory sites since most enterprises have offices in more that one places. My lab however is not running 24/7 and the domain controllers in the second site are rarely turned on in order to save resources. This leads to issues with the Active Directory replication such as the "The target principal name is incorrect" error when I execute:  repadmin /syncall /AdeP. To remedy the issue, we have to reset the machine password of the domain controller that has been offline. First off, we are going to stop and disable the Kerberos Key Distribution Center (kdc) service on the problematic domain controller, in our case DC4. There may be some tickets in the cache so we should also clear them using klist purge Now it's time to change the machine password of the domain controller using the command netdom resetpwd /s:dc3 /ud:lab\administrator /pd:* Replace the "lab\administrator" with an account on your
Keep reading

Configuring a Certificate on Exchange Receive Connector

Today's article is about configuring Exchange receive connectors with specific certificates. Out of the box, Exchange uses self signed certificates to provide TLS secured mail flow. This will definitely be an issue if you expose the SMTP protocol to client computers since they won't trust the certificate. In this article we are going to configure a certificate that was issued by a third part authority to the Client Frontend receive connector. We'll start with getting the thumbprint of the certificate using the Get-ExchangeCertificate cmdlet: [PS] C:\> Get-ExchangeCertificate Thumbprint                               Subject ----------                               ------- 241B864DC82C664FECBA18B8D54987AAFB65B4C2 CN=*.lab.com, ... D4D210886B34E690191A1F008C78FDD0E7325DD4 CN=Exchange2013A 960171662EB261162F9C8CBE12E0B75D6F06ABB0 CN=Microsoft Exchange Server Auth Certificate 2690324B827A9F2B75D59104F81CAAA57CDD627B CN=WMSvc-Exchange2013A [PS]
Keep reading

Running Multiple NGINX Ingress Controllers in AKS

Image
In some of the previous articles of this blog, we went through the process of installing NGINX as the Ingress Controller in AKS clusters. Either for applications that should be available directly from the public internet, or for applications that should only be accessed from networks considered internal. In the majority of the cases, however, and given that an AKS cluster is an environment that is designed to host multiple applications and provide economy at scale, additional ingress controllers may be required. In this post, we're going to go through the process of deploying an additional NGINX ingress controller that is going to be used for internal applications. The below diagram depicts the desired outcome: The Angular application is published via the public NGINX through the Azure Load Balancer that has been assigned a public IP. The .NET app is published by a different set of NGINX pods that are deployed in a different namespace and their ingress controller service is connect
Keep reading