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 ?
jet-infoAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

hsclaterCommented:
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
0
jet-infoAuthor Commented:
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.
0
hsclaterCommented:
Hi there

So let me confirm, you have an SBS 2008 server, you can use ADUC on there or the SBS console with no issues, and have set a password policy to disable the complexity, expiration or history. This policy is applied to all of your PCs apart from one with no issues. So it seems to be local PC issue.

NB: it is not a good idea to disable all these password requirements, you are significantly reducing your security by doing this. I would seriously challenge this requirement.

Some questions:
- What version of Windows 7 is on the PC?
- Is it joined to the domain?
- Why do you need to create local user accounts? Most applications should work fine with a domain user account. The application would certainly have no place in an Enterprise if it required so much manual management. Confirm this with the vendor and again challenge them.

Regardless, you should not have the gpedit.msc error. inetres.admx is for Internet Explorer policies, run the following at an admin cmd prompt:

sfc /scannow

Then review the log, if there is anything wrong with your ADMX files it should fix it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

jet-infoAuthor Commented:
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.
0
jet-infoAuthor Commented:
Thanks for your help and your time !
0
hsclaterCommented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.