Avatar of csg-unit
csg-unit
Flag for United States of America asked on

Fine Grained Password Policy PSO

Long listShort list
Hi. I ran this same command at two different customers to create a fine grained Password policy.  in ADSIEDIT, We see differing quantities of available attributes.  One of those attributes that exists at Customer A, is missing at Customer B's site is the "AppliesTo" attribute, which is needed.    does anyone know why they differ?

Both running 2012 R2 Domain controllers.  I tried to generate forestlevel but says "Referral was returned from the server"

New-ADFineGrainedPasswordPolicy -Name "FineGrainedPSO" -Precedence 500 -ComplexityEnabled $true -Description "Fine-Grained Password Policy"-DisplayName "Fine-Grained Password Policy" -LockoutDuration "0.12:00:00" -LockoutObservationWindow "0.00:15:00" -LockoutThreshold 7 -MaxPasswordAge "155.00:00:00" -MinPasswordAge "2.00:00:00" -MinPasswordLength 8 -PasswordHistoryCount 5 -ReversibleEncryptionEnabled $false

Open in new window

Windows Server 2012Active Directory

Avatar of undefined
Last Comment
csg-unit

8/22/2022 - Mon
Cliff Galiher

Differences can be attributed to the schema level of the domain and forest.  Adprep changes these, and I have seen environments where a higher level DC was introduced then pulled back for whatever reason.  But schema changes are permanent, so the schema level can be higher than the highest level DC still in the environment.

Another thing to look at is the functional levels of the domain.  You can have 2012 R2 DCs and still have the functional levels at 2003, for example. The functional level must be lower than the *oldest* DC OS in the environment.  Many people retire old DCs but then don't raise the functional level.
Kevin Stanush

Try looking at the password policy object using the Administrative Center or a 3rd party app like Hyena.  ADSIEdit is not a friendly way to deal with PSOs.
csg-unit

ASKER
OK, I had a feeling that was important.  note the short list is 2012 and long list is 2008 R2 level.  is there something else I should look for?  2008 R2 level seems to have more abilities.  Customer A forest - Long List of AttributesCustomer B forest - Short List of Attributes
Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!
Walt Forbes
Cliff Galiher

Newer adds more abilities. I can't think of any that we're taken away from 2008 R2, to 2012 R2. So not sure why you think 2008R2 has more features.
ASKER CERTIFIED SOLUTION
Kevin Stanush

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
csg-unit

ASKER
I understand abilities are added with each revision.  Attributes in the Fine-Grained-Password Policy must have been reduced for another reason.
Kevin Stanush

Look to see if you have the msDS-xxx attributes, as these are where the PSO settings are stored.  Like I said, nothing has changed.  If you are not going to use a GUI to manage the PSO, look at the objectclass attribute.  In your original screenshot, you have shown all of the attributes defined for the object's parent, so most are <not set>, you need to scroll down to see the ones that are 'missing'.
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
csg-unit

ASKER
Indeed you are correct. Logging in as the built-in administrator vs member of administrators group changed the quantity of visible attributes on Customer B's site to the appearance of Customer A.  Thank you