Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
Fine Grained Password Policy PSO
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
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
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.
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.
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.
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. 
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.
The fine grained password options have not changed since introduced. 2012 does not have any additional capabilities. Make sure you have the Advanced Features option enabled and are running as an Admin (ie 'Run As Administrator') as missing the Attribute Editor and Security tabs are good indicator that security is blocking some of the attributes from being visible. Or, the PSO wasn't setup properly.
But your screen shot is not of the PSO anyway.
But your screen shot is not of the PSO anyway.
I understand abilities are added with each revision. Attributes in the Fine-Grained-Password Policy must have been reduced for another reason.
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'.
Premium Content
You need an Expert Office subscription to comment.Start Free Trial