Trying to change Idle Client Timeout - Not working as required

(0) Share

Report

Posted on by Community Member

Hi There,

I am trying to set Idle Client Timeout, I have tried it through below options but it is not working as require, may I please get a fix solution for this.

I want my client should get disconnect in 02:00:00 Hrs for that I have kept 72600 Sec time there in the configuration file.

1. I have changed through "ClientServicesKeepAliveInterval" option but it is not responding

2. Then tried changing it through the NavOne Client in "Idle Client Timout" option but no luck.

I have seen this from MS site itself but it's not working for me.

Any help would be appreciated.

Let me know if more details required on this...!!!

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

Community Member on at

Like (0)

Report

Please help

Was this reply helpful? Yes No
Suggested answer

Alexander Ermakov 28,096 on at

Like (0)

Report

I do not get clearly what is your target. Do you want to cut your users:

- after certain period of inactivity

- or do you want to cut users always at 02:00 a.m. regardless they are active or not

- or do you want to check if the user is inactive at 02:00 a.m. and cut if he is inactive

- or do you want to check at 02:00 a.m. that user has been inactive for certain period and cut him if so?

Was this reply helpful? Yes No
Suggested answer

Suresh Kulla 50,243 Super User 2025 Season 2 on at

Like (0)

Report

Do you want to disconnect a client if he is idle for 2 hours ? why do you want to disconnect a session which is active and for more than 2 hours ?

If you are looking to disconnect if the client/session is idle then use the IdleClientTimeOut property

www.metaphorix.co.uk/idle-client-timeout-nav-2013-r2-nav-2015-nav-2016

Was this reply helpful? Yes No
mbr 5,136 on at

Like (0)

Report

HI Suresh,

I am running into the same problem. So far it's working when I set Client Idle timeout to 4 mins or below. But I want to at least specify 30 minutes. We have Nav 2013 CU 37. Any thoughts?

Was this reply helpful? Yes No
Suggested answer

mbr 5,136 on at

Like (0)

Report

Hi All,

I have figured it out. With the CU that Nav did (in my case CU37) for Nav 2013, the Client Idle Timeout will not work for any settings higher than 2 minutes. One would need to ensure that the ClientServicesKeepAliveInterval key in the ClientUserSettings.config is also set up to be at least 1 min higher than the Client Idle Timeout. If this key is not present in the ClientUserSettings.config, users will stay logged on regardless of the Client Idle Timeout Settings (if set up as higher than 2 minutes).

So all you have to do is add below key in the ClientUserSettings.config. Below is setup

<add key="ClientServicesKeepAliveInterval" value="660" />

whereby Client Idle Timeout = 00:10:00 (for 10 min).

That should do it!

Was this reply helpful? Yes No
Suggested answer

mbr 5,136 on at

Like (0)

Report

Hi All,

I have figured it out. With the CU that Nav did (in my case CU37) for Nav 2013, the Client Idle Timeout will not work for any settings higher than 2 minutes. One would need to ensure that the ClientServicesKeepAliveInterval key in the ClientUserSettings.config is also set up to be at least 1 min higher than the Client Idle Timeout. If this key is not present in the ClientUserSettings.config, users will stay logged on regardless of the Client Idle Timeout Settings (if set up as higher than 2 minutes).

So all you have to do is add below key in the ClientUserSettings.config. Below is setup

<add key="ClientServicesKeepAliveInterval" value="660" />

whereby Client Idle Timeout = 00:10:00 (for 10 min).

That should do it!

Was this reply helpful? Yes No
Suggested answer

4BzSoftware 6,073 on at

Like (0)

Report

Hope everyone interested in our new tool!

mibuso.com/.../idle-session-management

Was this reply helpful? Yes No