- Joined
- 8 Apr 2005
- Messages
- 16,950
My company implemented a "strong" password policy on 8/22, problem is it breaks one of our "home-grown" applications. We have this program, let's call it "Application X", that feeds off of two local user accounts - let's call them USER1 and USER2. In some cases, you have to delete and re-create USER1 and USER2, with very specific passwords that are coded into the application itself.
Due to this policy, you can't use the passwords that the program needs to work since they don't meet the criteria. The only fix we have at the moment, is to remove the machine from the domain, make the change (since the domain settings are no longer applicable), and then re-add it.
Couldn't I just essentially reset the security template, without having to remove from the domain?
Any thoughts on how to create passwords for LOCAL accounts that don't meet DOMAIN criteria, without removing them?
Due to this policy, you can't use the passwords that the program needs to work since they don't meet the criteria. The only fix we have at the moment, is to remove the machine from the domain, make the change (since the domain settings are no longer applicable), and then re-add it.
Couldn't I just essentially reset the security template, without having to remove from the domain?
Any thoughts on how to create passwords for LOCAL accounts that don't meet DOMAIN criteria, without removing them?