Hello,
Did you login with the domain administrator of that respective domain?
Please ensure that you login with the domain administrator / enterprise administrator of the respective domain !
Regards,
Mitul aka v2min
Did you observe that after opening GPEDIT.msc or while updating and group policy??
As on the domain controller while opening gpedit.msc you would observe the same...
Thanks again for the reply. I see the issue after I've opened GPEdit.msc and navigated to: Local Computer Policy>Computer Configuration>Windows Settings>Security Settings>Account Policy>Password Policy>Minimum password length>Properties (Local Security Setting tab).
I inherited this server. Someone else set it up and I've found some unique changes in other areas (e.g. Terminal Services port changed from 3389). Is it possible that they have disabled the Domain Administrators permission to change the minimum password length? Again, remember I can change other settings in Password Policy.
Hi,
Before going further, sorry for the late response.
>>I see the issue after I've opened GPEdit.msc and navigated to: Local Computer Policy>Computer Configuration>Windows Settings>Security Settings>Account Policy>Password Policy>Minimum password length>Properties (Local Security Setting tab).
Based on the description, we can run command gpreuslt/h report.html with admin privileges to collect group policy result report to check what account policies have been applied in our domain. If the Minimum Password Length setting has been configured in domain GPO, then it's right and normal that we can't edit it via local GPO. In a domain, account policies should be controlled at domain level, and once configured, we can't edit them via local GPO.
Best regards,
Fran
Hi,
>> Is there a switch to run gpedit and get the Default Domain Policy?
Sorry, there is no such switch. However, Gpedit.msc is to open local group policy editor whereas GPMC.msc is to open the editing console for domain GPOs.
>>It in the Default Domain Policy I can change the minimum password length
This tells me that there is no issue regarding editing the policy setting.
Best regards,
Frank Shen