[rainmakr]

What's the difference between these two settings?:

- Max. Security Timeout
- Set Password Timeout

Thanks,
John

[jibi]

They are the same thing, except the first one allows the user to change the timeout to be less than the specified time (not that anyone would do that willingly).

[rainmakr]

After some experimenting, it appears as though the following is true:

- Set Password Timeout
Forces the password timeout interval. If the user changes the interval, it will get reset to the "Set Password Timeout" value when policy gets pushed to the handheld.

- Max. Security Timeout
Sets the maximum interval that the user select as the timeout value.

It appears that if the Max. Security Timeout is set, then "Set Password Timeout" should not be used. Is this correct?

[aschieman]

The Set Password Timeout policy sets the value of Options->Security->Security Timeout. As you stated, when you push the policy down, this value will be set.

The Maximum Security timeout changes the maximum valuable available as an option for Options->Security->Security Timeout.

For example, if you have the User Can Change Timeout policy = TRUE, and set the following policies:

Set Password Timeout = 15 minutes
Maximum Security Timeout = 30 minutes

.... the value of Options->Security->Security Timeout will be 15 minutes, but the user can change it to a maximum of 30 minutes. The user can always make this value lower, if you allow them to change the setting.

You can use them both without any problems.

Of course, there is also the Long Term Timeout and Periodic Challenge Time policies which control locking regardless of activity.

[rainmakr]

It appears that part of my problem has to do with our handhelds getting our policy pushed every 2-5 minutes.

It used to lock the device as well, but I found a workaround solution for that yesterday. Now it looks like I need to find out what is causing the policy to be pushed repeatedly.