Programs Close in Remote connection

Dongaschlonga · 13th April 2011, 9:57 AM

Hi all, and thank you in advance for the help I receive with this problem.

We currently have 65 users in our organisation and have just recently thought of the idea of moving towards the concept of cloud computing.

We currently Have TSPlus running on our terminal machine. (for those of you who are unsure this program allows multiple users to access one machine at the same time).

The performance of this machine is undoubtedly good, but when it comes down to the little differences between it and a physical desktop computer, it can be very annoying, which is why I am writing this.

We have one client who is based outside of our building and remote desktops into this newly purchased machine. He originally used to connect to a standard pc.

Now the issue is, that his connection from his house is a little left to be desired as he is in a relatively remote area. The issue being is that he loses connection to the Terminal Server and after he connects back, his programs are closed and his work is lost.

Now I know that it may be easy to say, just save your work. But working remotely is going to happen for allot of users in our organisation and the solution is simply not just to save your work constantly although it is a good habit to get into.

Strangely enough the computer he used to connect to, never closed his programs. Is there something I'm missing? or is it perhaps this program I'm using which is causing this issue, and if so what is the solution?

Once again thank you in advance for the help I receive.

Dongaschlonga · 13th April 2011, 11:44 AM

It seems as though I have fixed this issue.

Setting a GPO in the actual terminal server under "sessions and time Limits" - > Set time limit for disconnected sessions (set that to never).

It works. No longer have this issue.

toje · 13th April 2011, 3:46 PM

I suggest seting it to something like 6 hours, 2 is better.
Because leaving a session there indefinitely may lead to slow Downs and holding up resources

13th April 2011, 9:57 AM	#1
Dongaschlonga Member Join Date: Mar 2011 Posts: 22	Programs Close in Remote connection Hi all, and thank you in advance for the help I receive with this problem. We currently have 65 users in our organisation and have just recently thought of the idea of moving towards the concept of cloud computing. We currently Have TSPlus running on our terminal machine. (for those of you who are unsure this program allows multiple users to access one machine at the same time). The performance of this machine is undoubtedly good, but when it comes down to the little differences between it and a physical desktop computer, it can be very annoying, which is why I am writing this. We have one client who is based outside of our building and remote desktops into this newly purchased machine. He originally used to connect to a standard pc. Now the issue is, that his connection from his house is a little left to be desired as he is in a relatively remote area. The issue being is that he loses connection to the Terminal Server and after he connects back, his programs are closed and his work is lost. Now I know that it may be easy to say, just save your work. But working remotely is going to happen for allot of users in our organisation and the solution is simply not just to save your work constantly although it is a good habit to get into. Strangely enough the computer he used to connect to, never closed his programs. Is there something I'm missing? or is it perhaps this program I'm using which is causing this issue, and if so what is the solution? Once again thank you in advance for the help I receive.

13th April 2011, 3:46 PM	#3
toje Member Join Date: Dec 2004 Location: South NSW Posts: 878	I suggest seting it to something like 6 hours, 2 is better. Because leaving a session there indefinitely may lead to slow Downs and holding up resources __________________ Network Administrator, Rural Firefighter, and Terrible offroader

13th April 2011, 11:44 AM	#2
Dongaschlonga Member Join Date: Mar 2011 Posts: 22	It seems as though I have fixed this issue. Setting a GPO in the actual terminal server under "sessions and time Limits" - > Set time limit for disconnected sessions (set that to never). It works. No longer have this issue.