Firstly, I know this is not best practice...just bear with me!
We have taken on a new client which have their own SM server. We will be migrating all of their domains across to our SM instances, however, in the meantime we have implemented an updated password policy...as there wasn't one previously. However, they will still be adding users until we migrate, which will be in the coming months....so, we decided to modify the password policy but also enable 'Disable password strength for existing passwords' so that this didn't initially effect existing users....however this did not work! In fact, all users who didn't meet the password policy received the 'Password policy violation' email! Each and every one of them...as all of them had bad password choices! This is a different matter.
So, anyone else seen this? Does the check box for 'Disable password strength for existing passwords' actually do something entirely different to what I think it does? i.e. enable password policy for any new mailboxes but leaves the old unsecure ones alone?
Any clarification would be great :-)
This is in SM 13.4 Pro by the way.