Hi Guys, We are running a Windows 2003 domain with Exchange 2007. Strange issue, we seem to be pulling our Password settings from the exchange server People are suddenly been asked for Complexity settings and passwords lengths that are different from our Default Domain policy. Is this normal or have I missed something? Regards, Adrian

Exchange does not specify any password policies or enforce it. You should check your GPOs. You can run rsop.msc from the client workstation and look at the policies being applied/enforced.

Similar thread: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3877731&SiteID=17 Regards, Xiu

Thanks Guys, Its a strange issue, from running RSOP it shows the "complexity requirements" as being "Not defined", which is the same as my Default Domain Policy. *as a side note, we have just moved from a Win 2000/2003 domain to a Win 2003 functional level domain. Could it be a cause of "tattooing" from a previous policy or setting? Where does OWA pull its password security settings from ? is it not the default domain policy? Would it matter if the domain was 2000or 2003 ? Thanks

OWA follows the defined policies in GPO. It is possible that the policy was set to be complex passwords required and then was changed to not defined. It is interesting to note when you change any policy from xyz to not defined, it may leave tatooing as you mentioned. Best way to negate effect of xyz is to define abc explicitly. It does not matter if it is 2000 or 2003 domain. Password policies are more granular in 2008 AD. However, that is not your case. All password settings in your domain should be defined from Default Domain Policy.

Yes, I think thats the case. Its a pity you cant figure out when tattooing is in effect.. Anyway thanks for your help all Case Closed

Please mark the thread as answered as it helps us track what needs attention vs. what is answered satisfactorily.