• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Install fails

Z

zoltar

Guest
Clean Win2003 with IIS.

Install fails: Unable to reconfigure compinent Plesk: The password does not meet the policy requirements. Check the minimum password length, complexity and history requirements.

What are the requirements?

Thanks,
Z.
 
You set the requirements in a group policy, so check your "account policy" :)
 
Clean W2003 install comes with a restricted password policy and I assumed that PLESK would install on a 'clean' W2003. Probably when the install wants to create user accounts the system rejects them because of the policy. Changing the password policy after the error message didn't help (it's a stand alone server btw)
Uninstall takes like 4 hours. :(

So I wait, then reset the pasword policy to zero and try again.
I just can't seem to find the 'group policy ' thingy? :D

Z.
 
Set the min. password legnth 0
max. password age: 0
password history: 0
disabled complexity requirements

now the install works.
Z.
 
Is this on the Windows 2003 Server editions? I have never had any problems installing on Web Edition relating to policies.
 
I installed on SBS2003 (internal development) and recieved the same error. I have reduced the complexity in the local policy.

Just as a security note, maybe Plesk should make the passwords conform to a minimum level of complexity that the IT industry is going to (read as follow Microsoft's default).

Chuck
 
Back
Top