Skip to main content

Associate Managers to Their Subordinates

Today on PowerShell.org, I found an IT Pro who needed to find a way to associate a manger not only with their immediate subordinates, but also the subordinates of their subordinates.  Here is what I came up with. 

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

74

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

92

93

94

95

96

97

98

99

100

Function Get-SubordinateData

{

Param (

    [Microsoft.ActiveDirectory.Management.ADUser[]]

    $UserList

 

)

 

 

    Function New-ManagerData

    {

        $Obj = New-Object -TypeName PSObject -Property @{

            "UserName" = $Null

            "DistinguishedName" = $Null

            "DirectReports" = @()

            "DRNames" = @()

            "Manager" = $Null

        }

        $obj.PSObject.TypeNames.Insert(0,'ManagerSubordinateData')

        Write-Output $Obj

   

    }

   

    Function New-DRName

    {

    Param ($Name)

        $Obj = New-Object -TypeName PSObject -Property @{

            "Name" = $Name

        }

        Write-Output $Obj

    }

 

 

 

    # Create a dynamic array to hold all of the objects to

    # be sent to the pipeline.

    $UserArray = @()

 

    # Do the initial population of the ManagerSubordinateData

    # Objects

    ForEach ($U in $UserList)

    {

        $Obj = New-ManagerData

        $Obj.UserName = $U.Name

        $Obj.DistinguishedName = $U.DistinguishedName

        $Obj.Manager = $U.Manager

   

        $UserArray += $Obj

   

    }

   

    # Cycle through all of the user objects passed to this function

    # and add subordinate data to the managers.

    For ($X = 0; $X -lt $UserList.count; $X++)

    {

        # If a User Object has a manager, process it.

        If ($UserList[$X].Manager)

        {

   

            # Get the Distinguished Name of the user's manager.

            $UserManager = $UserArray |

                Where-Object DistinguishedName -eq $UserList[$X].Manager

   

            # Assign that manager the Distinguished name and the Name of

            # the subordinate in the ManagerSubordinateData object.

            $UserArray | Where DistinguishedName -eq $UserManager.DistinguishedName |

                ForEach-Object {

                    $_.DirectReports += New-DRName -Name "$($UserList[$X].DistinguishedName)"

                    $_.DRNames += New-DRName -Name "$($UserList[$X].Name)"

                }

        }

    }

       

    # Write the data to the pipeline.

    Write-output $UserArray

 

<#

.SYNOPSIS

Returns all the subordinates of a manager.

 

.DESCRIPTION

Uses Active Directory to associate managers to their subordinates.

 

.PARAMETER UserList

A list of Active Directory User Objects to process for manager/subordinate

relationships.  You must include the extended property of "Manager".

The Get-ADUser cmdlet will not include this propertyt by default.  See

the Example section.

 

.EXAMPLE

Get-SubordinateData -UserList (Get-ADUser -filter * -Properties Manager)

Returns object that associate a mangers Dinstinguish Name with there

Distinguished Names pf their subordinates.

 

NOTES

Requires access to the Active Directory Module.

 

 

#>

}   

 

 

 

 

Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the