The Terminal Server reboots at least once a month for Windows security patches. If the process you are running is expected to take more than 12 hours, you will need to periodically reconnect to your Terminal Server session so your connection doesn’t get terminated. For example, if a Terminal Server session is left unattended for twelve hours with no user interaction, that constitutes an idle session and will be terminated. If you do not sign out (log out), programs you have running will continue, but your session will be reported as inactive.Īn idle session occurs when no mouse or keyboard input is detected over a period of time.
This includes closing the Remote Desktop session via the “X” button of the Remote Desktop window, clicking on Start → Disconnect, or by any number of other means including your computer freezing before properly disconnecting or losing network connectivity before cleanly disconnecting. This happens when you are connected to the Terminal Server (ts.) via remote desktop, and leave your session by any means other than “Log Off” via its Start Menu. Sessions inactive for 12 hours will be terminatedĪny sessions that have been idle or disconnected for more than 12 hours will be terminated.Ī disconnected session is where the user is still logged in, but no longer has an active network connection to their session. We will terminate any process that is found to be negatively impacting system resources and inhibiting the use of the Terminal Server by other users.
You will need to ensure that the programs you are running do not impact other users. The Windows Terminal Server (ts.) is a Shared Resource and processes that make excessive use of resources (CPU, Memory, Disk) should not be run there. If you must use a web browser on a remote system, please use them on one of the remote lab systems by going to: We strongly recommend that you do your web browsing on your local computer. Due to the limited capacity on the terminal server and the expected heavy rush of users, we don’t want web browsers parked on this system. Web browsers are notorious resource hogs and casual web browsing with a few open tabs can consume a lot of RAM and CPU. Make sure you follow these guidelines when using the Terminal Server Avoid using web browsers
Details of how to do this from various platforms can be found at this link: You will need a Remote Desktop program (commonly referred to as a Remote Desktop Client or an RDP client) to access the Terminal Server (ts.). Notably, the Microsoft Office suite is not available because of software licensing restrictions. Due to licensing restrictions and resource limitations, the Terminal Server only contains a subset of the software load we install in the general MCECS Windows Labs.
0 kommentar(er)
