Skip to main content

When did members of a group last change their passwords?

Normally your password policies would effectively keep users changing their passwords in an acceptable period of time.  Should you need to know how long it has been since members of a group has change their password, try out this code.  You feed the cmdlet a comma separated list of security groups in your Active Directory environment. It will return when each member of the group last changed their password and how many days ago that change was. 
You need access to the ActiveDirectory module for this code to work.

Function Get-GroupPasswordDate
{
[cmdletbinding(HelpURI = "http://get-help-jason-yoder.blogspot.com/2012/12/get-grouppassworddate.html")]
Param (
    $Group
)
   
# Import the required cmdlets from the ActiveDirectory module.
    Import-Module ActiveDirectory -Cmdlet Get-ADGroupMember, Get-ADUser

# Cycle through each group sent to the cmdlet.
    ForEach ($Item in $Group)
    {
        Try
        {
            Get-ADGroupMember -Identity $Item -ErrorAction Stop |
             Get-ADUser -Properties PasswordLastSet |
             Select-Object -Property @{Label="Group";Expression={$Item}},
             Name, PasswordLastSet,
             @{Label="NumOfDays";Expression={((Get-Date).`
             Subtract($_.PasswordLastSet)).Days}}
        }
        Catch
        {

        }
    }
<#
.SYNOPSIS
Returns password age information for a list of security groups.

.DESCRIPTION
Returns each user in a Security group and when they last changed their passwords.

.PARAMETER Group
Comma separate list of security groups who's members you need to evaluate for their password age.  Any invalid groups will be ignored.

.EXAMPLE
Get-GroupPasswordDate -Group "IT", "IT Managers", "Domain Admins"

Group         Name               PasswordLastSet       NumOfDays
-----         ----               ---------------       ---------
IT            Amr Zaki           6/6/2012 6:05:26 PM         188
IT            Ayca Yuksel        6/6/2012 6:05:26 PM         188
IT            Steve Winfield     6/6/2012 6:05:26 PM         188
IT            Maira Wenzel       6/6/2012 6:05:26 PM         188
IT            Qiang Wang         6/6/2012 6:05:26 PM         188
IT            Anne Wallace       6/6/2012 6:05:26 PM         188


#>
}




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.