Windows 2003 remote desktop exit after the system automatically logout solution

Windows 2003 remote desktop exit system automatically logout solution Recently, the company has a strange demand, meaning that there is a web page, always open. Now only open this page on the server. This will meet the demand. But I met a problem in the application. After I open the webpage on the server, I turn off the remote, and after a while, the running effect of the webpage is gone. I logged in again with my account and found it to be a brand new desktop. The running program is gone. I thought that I should have not connected to the previous session state, but I thought it should not. It is estimated that the system is set up. I vaguely remember that there is a configuration in 2003 that sets the disconnection session time. So look for it online. The problem is that after I opened the program, I turned off the remote for a while and the server logged out of my body. So the running program naturally stops. The solution should be to prevent the server from logging out. The solution is as follows: Start-->Run-->gpedit.msc Computer Configuration->Administrative Template->Windows Component->Terminal Service-> Session Set "Set Time Limit for Disconnected Session" ; changed to "not configured". If, through the above operation, the remote desktop connection is disconnected for a while and the running software is automatically closed, then the following operations are performed: Start-->Run-->tscc.msc Connection--> The RDP-Tcp right-click property--> session changes the settings of the alternate user settings in this to none, and never check. Need to explain: After the above work, my remote server is still the problem, then: Cancel the boot press ctl + alt + del, this will everyone. Start-->All Programs-->Administrative Tools-->Local Security Policy-->Local Policies--> Security Options: microsoft web server: automatically log out users when login time is exhausted, change to &ldquo ; disabled”. Microsoft web server: The idle time required to suspend the session is changed to 99999, which is actually prohibited. Finally, if possible, log in to the server with the administrator once. Also, the most critical step: when you log in to the remote server, during the exit process, do not click on the remote desktop program's “×”, and you can't log out. Instead, on the desktop of the remote server, it is important to click “Start--Shutdown--Disconnect”.