Logging off users on a RDP server, if application crashes
We have an Access application running on a remote server. This server is locked down and opens our application at login. When they exit the application - it runs the Logoff function and takes them back to their local desktop.
I have put several functions into the Access application that will allow users to logoff - should an issue occur. However, I do see a possibility of something going wrong and the user not being able to log out. The Taskbar/Desktop/TaskManage
I was thinking of writing a small c# process, that is triggered by the Access application once it has loaded. It would pass the process ID the the c# app, which would then monitor the process ID, to see if it's still running. If not (i.e a crash has taken place), it would log the user off.
Is this a good idea, and as I'm pretty new to c#, does anyone have any pointers (or better suggestions)?
I have put several functions into the Access application that will allow users to logoff - should an issue occur. However, I do see a possibility of something going wrong and the user not being able to log out. The Taskbar/Desktop/TaskManage
I was thinking of writing a small c# process, that is triggered by the Access application once it has loaded. It would pass the process ID the the c# app, which would then monitor the process ID, to see if it's still running. If not (i.e a crash has taken place), it would log the user off.
Is this a good idea, and as I'm pretty new to c#, does anyone have any pointers (or better suggestions)?
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Make it a runtime. It will close down - or ask the user to do so - if it runs into troubles your error handling doesn't catch.
/gustav
/gustav
Thanks Gustav - good to hear from you - hope all is well.
OK - that's a good point. Do you think it's a sound idea, or would you do it differently?
OK - that's a good point. Do you think it's a sound idea, or would you do it differently?
We've used the runtime environment for decades with zero issues. Should an error occur, a message is popped, and the only choice for the user is to close the application.
If you need to do something afterwards, you could launch the application from a shortcut that opens a batch/command/powershell file which launched Access, then waits for this to finish before moving on calling your termination command(s).
/gustav
If you need to do something afterwards, you could launch the application from a shortcut that opens a batch/command/powershell file which launched Access, then waits for this to finish before moving on calling your termination command(s).
/gustav
Premium Content
You need an Expert Office subscription to comment.Start Free Trial