Skip to main content

Find User Accounts That Have Not Been Used

It happens from time to time. You are asked to create an account by Human Resources and then the employee never shows up.  You would expect HR to tell that the account is no longer needed, right?  Worse yet, what if they forget to tell you that the employee was terminated? 

Yes, I’ve had to deal with these procedural issues before.  From a technology stand point, there is nothing wrong.  From a security aspect, everything is wrong.  There are two things that you can do to look for these potential problems.  The first is to look for accounts that have not been logged into.

Get-ADUser -filter * -Properties LastLogonDate |

Where LastLogonDate -eq $null

The LastLogonDate property became available to us with Windows Server 2003 SP1.  Essentially, if the value is $null, then the account has not yet been logged into.  You may want to pipe this to Disable-ADAccount.  This will stop an unused account from being used.

What about an employee that was terminated, and you were not told?  Again, this is a procedural issue that can have serious implications. The first week when I started a job as a Network Administrator, I bumped into a small problem.  I had heard through the grape vine that someone was terminated the week before I started.  While looking over the security logs, I found out that this person was accessing the system….from the inside.  It turns out that his account was not disabled and his key was not taken away.  He walked away with a lot of proprietary, confidential data.

Since his account was used, this next command will not help.  It will help find accounts that have not been used in a long time.

$Users = get-ADUser -filter * -Properties LastLogonDate 

 

ForEach ($U in (get-ADUser -filter * -Properties LastLogonDate))

{

    If ($U.LastLogonDate -ne $null)

    {

        If ((($U.LastLogonDate).Subtract($(Get-Date)) | Select -ExpandProperty Days) -le -60)

        {

            Write-output "$($U.Name) has not logged in since $($u.LastLogonDate)"

 

               

        }

    }

}

 

This will alert you to all accounts that have not be used in 60 days.  An alternative is to get rid of the write host line and replace it with:

$U | Disable-ADAccount

That will also shut down those accounts.

Comments

Popular posts from this blog

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 .

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.