Need documentation on how to change Password Policy. I need make a change and need to know what to do from there. Do I need to push it out somehow? Will it effect everyone that was under the Policy before? Do I just make the changes and save it and it will set everyone up from there?
Subject: Re: Changing A Password Policy
Hi,
If you have a Policy that is already applied to your users, then any change made to that Policy will be pushed down to your users upon their Authentication with the Server via DCC (Dynamic Client Configuration). I’ve seen changes some times take a day or so to completely push down to all users. But overall, if the Policy is applied to the user, then any change to the Policy will be applied to the user as well upon Server authentication.
Hope this helps and feel free to reply with any questions! I try to check back fairly often.
Regards,
-Bob
Subject: Cool thank. and anoher thing…
That is what I was looking for. Another question.Will a policy made on a 8.01 server get pushed to a 6.5 client?
Subject: Re: Policy Questions
Hi,
This is something that I have not tested personally. Going on my own knowledge and understanding, I would think it should work fine.
Notes/Domino is designed to be backwards compatible and I'm sure many customer's are upgrading to 8.5. That being said, the procedure to upgrade is Server First, then Clients, then Templates. Of course, this can take a period of time to complete each step of the upgrade. This would naturally create environments that are temporarily running Servers higher than Clients and such. Notes/Domino still needs to function normally; an upgrade shouldn't break certain things mid-way. Overall, I would be extremely surprised if a Policy did not push down to a Client because the Server is 8.5 and the Client is 6.5.x. However, this is something that can only be verified through testing.
Hope all goes well!
Regards,
-Bob