Skip to main content

Create a New Password Setting Object in Windows Server 2012

Password Setting Object (PSO) is another name for Fine Grain Password Policies.  These PSOs allowed us to set up a different password policy based on security group membership.  For example, an employee who is working on a multi billion dollar drug might need to have more characters in their password and more frequent password changes than someone who does not handle critical company data.  PSOs allow us to do that.

 

Up until now, PSOs were created with the ADSI Edit application or PowerShell.  Now, we can use the Active Directory Administrative Center.

  • Open the Active Directory Administrative Center.
  • Change to Tree View.
  • Expand System
  • Click Password Settings Container

image

  • Right Click Password Settings Container and then select New –> Password Settings.

image

image

Here you can see all the settings that go into a PSO.  A few items to point out.

Precedence In the case of a conflict in which a user is a member of more than one group with different PSOs assigned to each group, the one with the Precedence number that is lower will be the effective PSO
Direct Applies To If you do not any users or groups to the PSO it will not apply to anybody.
   

Another nice feature of the AD Administrative Center is that you can easily see the precedence values that have been used and which PSO is using them.

image

Comments

Unknown said…
Hi,

I know this post was a yr ago but just to check if some pre-requisite is necessary to ensure i can create PSOs from AD Administrative Center.

Must the domain functional level be raise to 2012 for this to work?

The following link only mention 3 method for this to work but it is for 2008 - http://technet.microsoft.com/en-us/library/cc754461(v=ws.10).aspx

Hope you can clarify. Thanks
Unknown said…
Domain functional level must be at least windows server. 2008

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.