I have searched high and low and can’t seem to find an answer to if a user can be booted out of Epicor after a set time. We are Private Cloud ( ? Single Tenant? ) . The reason for this is that in our VM Environment, we all share the same config file(Smart Client ( aka fat client) to run Epicor and if 1 person stays logged into Epicor over an update weekend, guess what, no one can log in due to a mismatched version error… The culprit must be located and then told to log off. A little harder now as some employees are working from home. I cant stroll around and see who is working in Epicor…
Add this to the email before upgrade weekends… It works.
“If your workstation is left logged in, you will be written up, and after 3 write-ups, we deem you are not responsible enough for this company. We need folks with attention to detail.”
We also have 3rd party Data center that manages our network so I will get a call early squirly in morning to call their hotline early squirly to wake somebody up…
Could also blast out email after back up explaining who was logged on and kept everybody from working…Peer pressure…
Just getting ideas, would hate to have to pay for scripting to force EVERYBODY off at 6pm every day. I would be the on getting caught up on a non update weekend.
What I’ve always wanted was a script that was created by the users and run by whomever is running the update. Kick out users, check for running jobs and pause until finished, run pre-update reports to disc, etc.
Hmm. Scripted updates. What would we call something like that?
I can check, Would that stop their instance of Epicor.exe or just end their RDS session? Forgive me if my verbiage is not correct, IT is one of my hats ( small company)