asked on

Password policies on SBS 2008

Hi Experts,

We encounter a strange issue on a SBS 2008 server. The password policy settings are all configured to disable the complexity, expiration or history. We can create a new user in dsa.msc or SBS control panel on the server but it is impossible on the client computers. An error about complexity or history appears, even if we set a complex password.
We tried to activate the complexity, it was successfully applied on the client computer (checked in gpedit.msc), but the result is the same...

We absolutely need to be able to create new local users on the client computers to install a software successfully.

Any idea ?

hsclater

If you set a password policy correctly, it will apply to your computers and you will be able to set it however you want. I suspect you are not applying the policy correctly. The setting is a computer setting, so either apply in the default domain policy (or better, create a new policy at the same level at the root of the domain), or apply a policy to an OU containing your computers. It will do nothing to users accounts.

As you can see the password policy is a computer configuration:
Computer Configuration/Windows Settings/Security Settings/Account Policies/Password Policy

jet-info

ASKER

Edit:
I tried on another computer and it works normally. The problem is only on one specific computer.
On this computer when I launch gpedit.msc I receive this error:

Resource '$(string.VerMgmtAuditModeEnable)' referenced in attribute displayName could not be found. File C:\windows\PolicyDefinitions\inetres.admx, line 1495, column 249

I installed the .msi from here (http://www.microsoft.com/en-us/download/details.aspx?id=6243) in C:\Windows with no amelioration.

Is there any registry key to edit to fix this problem?

Any idea?

Thanks.

ASKER CERTIFIED SOLUTION

hsclater

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

jet-info

ASKER

OK, the problem was because of HP protect tools installed on the computer... Thank you HP !

I installed all HP related products and it finally worked like a charm.

jet-info

ASKER

Thanks for your help and your time !

hsclater

Yes HP Protect Tools is horrible. All of the HP crapware is awful, and takes time to remove.

I always blow away the OEM image and reinstall using a clean image with the latest updates integrated. See mydigitallife for tools to do that yourself.