Disable Exchange Security Policy For Windows Mobile Devices
Jan 21st, 2008 by Tariq Bamadhaj
If you one of those who have been given a Windows Mobile device by your company, chances are it is connected to the company’s Exchange Server. In that case, the server’s security policy is pushed to your device and while this is meant to protect you and the company in case of stolen device, there are times when such security policies just become too troublesome for everyday use. For example, are you may not be able to set a password you really want. Then there are those whose device turn off after just a short time of inactivity. If you’ve talked to the System Administrator at your company to change these settings but he’s not able to do anything about it, it’s time to take the matter into your own hands.
All your problems can be solved with some registry hacks. As always, back up your registry before proceeding because you never know when something will become messed up.
Enable/Disable Exchange Security Policy
Registry Key: HKLM\Security\Policies\00001023
To enable it: Set value to 0
To disable it: Set value to 1
Enable/Disable Inactivity Time
Registry Key: HKLM\Comm\Security\Policy\LASSD\AE\
{50C13377-C66D-400C-889E-C316FC4AB374}\AEFrequencyType
To enable it: Set value to 1
To disable it: Set value to 0
Setting Inactivity Time
Registry Key: HKLM\Comm\Security\Policy\LASSD\AE\
{50C13377-C66D-400C-889E-C316FC4AB374}\AEFrequencyValue
Value: Set to any value you want want. This is the number of minutes before timeout.
Set Minimum Number Or Characters For Password
Registry Key: HKLM\Comm\Security\Policy\LASSD\LAP\
lap_pw\MinimumPasswordLength
Value: Set to any value you want want. This is the minimum number of characters needed for a password.
Determining Password Complexity
Registry Key: HKLM\Comm\Security\Policy\LASSD\LAP\
lap_pw\PasswordComplexity
Value: 0 = Require Alphanumeric. 1 = Require numeric (PIN). 2 = No restriction.
Setting Number Of Failed Attempts Before Information Gets Deleted
Registry Key: HKLM\Comm\Security\Policy\LASSD\DeviceWipeThreshold
Value: -1 = disabled. Any other positive number refers to the number of attempts.
Setting Number Of Failed Attempts Before Displaying Codeword
Registry Key: HKLM\Comm\Security\Policy\LASSD\CodewordFrequency
Value: You can set it to any value you want.
With all these registry hacks, you should be able to tame your company given Windows Mobile device. Does it work for you?
The hacks for this article were derived from Just Code. He also has a software on the site for those of you who do not like messing around with the registry hack but still want to change the Exchange Security Policy.























You can use my program to do it as well
Hi Tamir
Thanks for the heads up on the software.
I just had to use your search tool to get to this article. You have a “popular articles” list which includes a broken link to this article. The link there is:
http://openads.etenblog.com/2008/01/21/disable-exchange-security-policy-for-windows-mobile-devices/
The correct link shouldn’t include the openads reference.
Hi melvynadam
Thanks for the heads up. I have made the necessary changes.
Cool application Tamir. Thanks.
The intro to this article described me perfectly. The IT guy responsible for the security policy has *indeed* refused to help me. Now I can help myself - thanks etenblog!
Hi melvynadam
You’re welcome. Feel free to post questions in the forum if you need some help that is not found in the blog.