Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, Power Apps, Power Automate, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates and new features to Dynamics 365 planned through March 2020
Release overview guides and videos Release Plan | View virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
We are using GP 2018 and would like a system which kill user session if he/she is not using GP for last 30 minutes.
Any help highly appreciated.
Rockton Software has a solution for this.
Rockton Software's GP Toolbox is the only real option that does a proper activity check on current GP users.. anything else that you would do from your own carries the risk to corrupt data if an end-user has any open / incomplete transaction active on the screen..
GP Toolbox from Rockton will never kill an end-user session for which a window is open that requires any kind of confirmation and/or save action.
Currently Rockton offers GP Toolbox license to the original price when it was launched a decade back up to the end of 2018.. The price is based on your total concurrent user licenses.
Another similar function is provided by Willoware GP PowerPack, which contains much more functions than GP Toolbox, but the price might be higher as well..
I can only reiterate Beat.
I would not implement anything like this without a proper tool. The problem is while it might appear that the user hasn't been active for 30 minutes (which is a very short time by the way), they may actually be running a process inside Dynamics that is taking longer - e.g. posting massive payment batch, running reconcile processes, check links processes.
I have certainly been at the receiving end of this sort of process as a consultant where internal system processes at clients will log you fully off the terminal server if inactive for 2 hours. This resulted at one point in a weekend of having to get up every 1 hour 50 minutes to shake the mouse to stop it kicking me off the system.
Business Applications communities