x Want to participate? Join the group to interact
  • State Verified Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 76 subscribers
  • Views 4113 views
  • Users 0 members are here
Browse Forums
Announcements
105
topics
32
replies
General Discussion
6k
topics
18k
replies
Vega

Disable user inactivity timeout

SOLVED
Posted By

I've set the idle timeout in IIS on the App Pool to be 0 and for good measure I've set the time out action to be suspend. I've set the recycling so it is off. In CRM, under the administration -> users -> user configuration, the idle timeout is set to 240. If I want to disable the timeout in CRM, does setting it to 0 do that? I'm sure it does, but the help file doesn't say. All it says is this:

The inactivity period (in minutes) after which a user is automatically logged out of Sage CRM.

Sage CRM uses the value in this field only if it is less than the value in Idle Time-out (minutes) specified for the Sage CRM application pool in Microsoft Web Server (IIS). The default idle time-out value set for the Sage CRM application pool is 120 minutes.

The help file doesn't say how to disable the timeout. Also, I assume that setting the value in CRM to a value higher than the app pool timeout will be pointless as the app pool will suspend or kill the process anyway?

A common question I get asked is how to stop CRM booting you out after a period of inactivity. IE stop it completely. Anyone? This is CRM 2020.

Parents
  • 0
    SUGGESTED

    This may be seen as unconventional by a lot of IT shops, but having worked with Windows servers for a couple of decades, I've always found it helpful to schedule a server reboot, say at 2 AM.  This ensures that any programs that are experiencing problems, e.g. memory leaks, will get fully refreshed for the next day's CRM users.  Similarly, certain types of configuration changes might require an IIS reset, but they might not be urgent.  So rather than disrupt all of your CRM users in the middle of the day, you can just make the change and then let the server reboot implement them.  

    As for the CRM and Rewriter App Pool settings, I go with:

    • Idle Time-out (minutes): 0
    • Regular Time Internal (minutes): 0

    In CRM, the User Inactivity Timeout (minutes) is set very large: 900, so every 15 hours a user session will abort.  

    As I say, rebooting servers nightly (or weekly) is not always popular with IT folks, but:

    • there's no good reason not to do it
    • most importantly, it works like a charm.
Reply
  • 0
    SUGGESTED

    This may be seen as unconventional by a lot of IT shops, but having worked with Windows servers for a couple of decades, I've always found it helpful to schedule a server reboot, say at 2 AM.  This ensures that any programs that are experiencing problems, e.g. memory leaks, will get fully refreshed for the next day's CRM users.  Similarly, certain types of configuration changes might require an IIS reset, but they might not be urgent.  So rather than disrupt all of your CRM users in the middle of the day, you can just make the change and then let the server reboot implement them.  

    As for the CRM and Rewriter App Pool settings, I go with:

    • Idle Time-out (minutes): 0
    • Regular Time Internal (minutes): 0

    In CRM, the User Inactivity Timeout (minutes) is set very large: 900, so every 15 hours a user session will abort.  

    As I say, rebooting servers nightly (or weekly) is not always popular with IT folks, but:

    • there's no good reason not to do it
    • most importantly, it works like a charm.
Children
No Data

*Community Hub is the new name for Sage City