Skip to main content

Removing a Local Users from the Local Administrators Group

By

Happy Monday all!

I’m finally getting around to posting some code from my last PowerShell class in Phoenix.  As always, I invited my class to bring an idea with them that they would like to try on Friday.  The idea that one of my PowerShell Rock Stars brought in reminded me of a problem that I had many years ago. 

You see, when the company that I worked for acquired another business, my job was to go in and join their IT systems into our domain.  Not a big deal with only about 30 clients.  This company had no dedicated IT support prior to our take over so I was going to be the first IT staffer the former employees meet when we hired them back.  All went well the first morning.  It was after lunch that I spotted a problem.

Before they all returned, I removed all the video games from the clients. Right after lunch, I was walking through the cubes and was watching people play video games.  Kind of bold considering it was their first day at work after being re-hired.  That evening, I discovered how they got those games back on.  They all had local administrator accounts.  Obviously, I missed something.

The question that I helped to answer in class was “How do I remove all local users from the local Administrators groups on my clients?”  I knew we could do it using the same method that we used to connect to Active Directory in PowerShell V1, ADSI. (Active Directory Services Integration).  ADSI can connect to a number of directory services besides Microsoft’s Active Directory.  In this case, a local security database. 

This is not my usual cmdlet type code that I like to dish out.  You can see a $ComputerName variable.  Just feed it the name of the client that you need remove accounts from the local Administrators group.  I’ll leave the error handling up to you.  I tested this code out on Windows 10 Client.  PowerShell remoting is required.

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

$ComputerName = "CL1"

 

Invoke-Command -ComputerName $ComputerName -ScriptBlock {

   

    # Object to be created for each user removed from the

    # local Administrators group.

    Function New-OutputObject

    {

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

            UserNameRemoved = $Null

        }

        Write-Output $Obj

    }

   

    # Connect to the local security database.

    $adsi = [ADSI]"WinNT://$env:COMPUTERNAME"

   

    # Grab all local user objects and place them in a custom object

    $users = $adsi.Children | where {$_.SchemaClassName -eq 'user'} | Foreach-Object {

        New-Object -TypeName PSCustomObject -Property @{

            UserName = $_.Name -join ''

            Groups = ($_.Groups() | Foreach-Object {$_.GetType().

                InvokeMember("Name", 'GetProperty', $null, $_,$null)}) -join ','

            SID = New-Object System.Security.Principal.SecurityIdentifier($_.ObjectSid[0],0)

        }

    }

 

    # Get the local Adminsitrators group object.

    $Group = $ADSI.Children.Find('Administrators','group')

   

    # Get the clients name.

    $client = $env:COMPUTERNAME

 

    ForEach ($User in $Users)

    {

 

 

        if (($User.Groups).split(",") -contains "users" -and

           ($User.Groups).split(",") -contains "Administrators")

        {

          

           # Get a new copy of the output object and populate it.

           $Obj = New-OutputObject

           $Obj.UserNameRemoved = $User.UserName

          

           # Invoke the local groups REMOVE method

           $Group.Remove(("WinNT://$Client/$($User.UserName)"))

          

           # Send the object to the pipeline.

           Write-Output $Obj

        }

        Else

        {

                    }

 

    }

} # END: Invoke-Command

 

Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more