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

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

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.