#Windows 7 not logging off code#
#Windows 7 not logging off windows#

It really boils down to them clicking 'Yes' or 'No' since if they are admins on the server they have other means to log off the 'service user' without interacting directly with a logon box if they really want to, and there is absolutely no way to get around this. Any administrator interacting with the server will be shown a message when they log in if your 'service user' is currently using that session or not, and they will have the option to log them off or not. I think the true root-cause resolution of the issue is to communicate to everyone who has the ability to log that user off to NOT log them off.

#Windows 7 not logging off windows#

Keep in mind that Windows Server typically has 3 total interactive sessions - the console session and 2 remote sessions (unless it is a terminal server in which case you are limited by your CALs, but I don't think you are using a terminal server in this case)

Other accounts, like local administrators, domain admins or even regular users can opne a new session and/or logon locally on the server without closing the other connection at all.Дepending on the main method used to interact with the server (either locally via the console or via RDP) there are 2 options. If someone logins to the server, even locally, it will not logoff this session. This session can only be logged off by the user it self, or forcedly by the Enterprise Admin. One of these sessions will be using a regular account credential to run the application. I need a way to login two sessions on the server (Windows Server 2000 or above). I need to find a way to keep an account always connected and running the application and everytime I need to check something on the application I can log with this account and open this same session.Д«ut when someone needs to manage the server, he/she can connect using his/her admin account which will not logoff the other account.

#Windows 7 not logging off code#

This is a critical application and it must be running 24/7.Д®verytime I need to manage the server I need to login using this account credentials to avoid close the application, since it's a windows form application showing a lot of information and cannot run as service and, as it's a third-party application, I can't change its code to work as a service neither.Дue this, the account needed to run the application is local administrator what's not safe at all, and every Sys Ad need to have its credentials, what also not safe since I can't keep track on who did what. I have a Windows application that must run under a certain user/pass in a server running Windows Server 2000 and another in a Windows Server 2003.