List the PSO associated with a user account with PowerShell

PSO’s (Password Setting Objects) is another name for Fine Grain Password Policy. A PSO allows an organization to have different password policies based on a security group. That means that unlike in an Windows 2003 domain where all password meet the same rules, in a 2008 domain you can have multiple rules for your passwords.

The code below allows you two obtain a list of all user accounts that have a PSO assigned to and that PSO is. It is designed to be used as a function or dot sourced into PowerShell.

<#
.SYNOPSIS
   Returns a list of user names and there PSO.
.DESCRIPTION
   Returns a list of user names and the Resultant
     PSO that is currently in effect on that user.

.EXAMPLE
   Get-PSOUsers
    
     Returns a list to the pipeline of the username and the
     PSO currently in effect on the user account.
.EXAMPLE
   Get-PSOUsers | Sort-Object PSO
    
     Returns a list of users with assigned PSO's, sorted
     by the PSO.
    
     Name                                    PSO
    ----                                    ---
    John Yokim                              CN=IT PSO,CN=Password Settings C...
    Ofer Daliot                             CN=IT PSO,CN=Password Settings C...
    Dave Barnett                            CN=IT PSO,CN=Password Settings C...
    Neville Burdan                          CN=IT PSO,CN=Password Settings C...
#>

function Get-PSOUsers
{
Import-Module ActiveDirectory -Cmdlet Get-ADUser

# Get a list of user accounts and also pull the # attribute msDs-ResultantPSO.  Also, rename the # msDs-ResultantPSO so it can be processed.
$UserList = Get-AdUser -filter * -property msDS-ResultantPSO | Select name, @{Name="ResultantPSO";Expression={$_."msDS-ResultantPSO"}}

# Create the object to hold the output of this function.
$UserObj = @()

# Loop through each user object and filter # out those do not have a value in the # msDs-ResultantPSO field.
foreach ($User in $UserList)
{


    if ($User.ResultantPSO -Like "*Password*")
    {
        # If there is a value in the msDS-ResultantPSO
        # than add it to the output.
        $UObj = New-Object PSObject
        $UObj | Add-Member NoteProperty -Name Name -Value $User.Name
        $UObj | Add-Member NoteProperty -Name PSO -Value $User.ResultantPSO
        $UserObj += $UObj
    }


}

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 .

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?

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

Backup and Restore AD LDS with DSDBUTIL.exe

Active Directory Lightweight Directory Services allow you to create a directory service that allows applications to have access to user accounts, groups, and authentication similar to Active Directory Domain Services. The big advantage here is that the schema of the directory service will not be bound by the rules of an Active Directory database. Exchange 2007/2010, for example, use an instance of AD LDS on the Edge Transport Server to provide for user authentication from the internet. Because your Active Directory database is not exposed to the internet, this is more secure. Applications will handle most of the dirty work should they require AD LDS. You may want to make sure the database is being backed up and also have a restore plan in place. Should the database become corrupt, the application that uses that database will fail. This document will walk you through backing up and restoring an instance of AD LDS using the dsdbutil.exe command. Fi...

Jason Yoder, MCT

Search This Blog