Get the name of a Server using the SID

In class we received audit logs that contained only a SID. Since we were interested in getting the name of the client associated with that SID, we turned to PowerShell for the answer.

The SID actually contains two parts. A unique code for the domain and then the Relative Identifier (RID) for the the client. This RID is the last portion of the SID and is unique in the network. Below is an example.

S-1-5-21-3400766600-4132462866-2336755051-1149

The RID is the numbers 1149. This is what we need to search for in Active Directory. For a client, use this PowerShell command.

Get-ADComputer –Filter * –Properties | Where-Object {$_.SID –like “*1149”} | Select-Object –Property Name, SID

The Get-ADComputer cmdlet will retrieve all computer objects in Active Directory. The –Properties parameter will add the SID to the default set of attributes that are returned from the Get-ADComputer cmdlet.

The Where-Object cmdlet will filter all the computer objects for one with a SID that ends in 1149.

The Select-Object cmdlet will remove all attributes from the output except the name and the SID.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

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 .

Where did a User’s Account Get Locked Out?

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...

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.

Jason Yoder, MCT

Search This Blog