Sessions Disconnect regardless of settings

[Inertiauk]

I'm using TSplus 8.40.10.30 which i believe is the newest version.
I'm on a server 2012 r2 server which is member of domain.

Ive set group policy on the domain to never disconnect sessions, allow reconnects, and never terminate disconnected sessions.
Please see the attached file to see how my session management is setup.

I have tried many different combinations of settings here, but no matter what I do, the session always ends immediately after either the use disconnects it, or if the network drops for a second.


So a tiny blip in the network is all it takes to end a session, kill all associated processes and loose any unsaved work.

When the user logs in from another device to take over their session, it immediately signs them out too.

Please help me fix this, I do like your product but with this 'bug' its useless to me.

Thanks
Mark

[jkuijt]

Hi,

All our TSplus customers use a single session per user so that they can always reconnect to the application they were working with, without the risk of data loss.
We all use the following registry settings which work very well (for years now):

Code: Select all

HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\fSingleSessionPerUser=1
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\MaxDisconnectionTime=0
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\KeepAliveEnable=1
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\KeepAliveInterval=1

Perhaps you can try the above settings.

Best regards
Jeffrey

[Inertiauk]

Thanks Jeffrey,

Which OS are these customers on please ?

I had these set as above except the 2 KeepAlive ones, which I just added, I will wait until later tonight when I can reboot the VM and see if this makes a difference.

In the meantime here are the rest of my registry settings for Terminal Services, in case you can spot anything else needs tweaking here ?

Thanks

[jkuijt]

Hi Mark,

We have customers running TSplus on Windows 7 Professional & Ultimate, Windows 8.1 Pro and Windows Server 2012 R2 and all use these registry settings.

The KeepAlive settings are important, please see:
nmsiam.blogspot.nl/2013/01/remote-desktop-session-timeouts.html

Some explanation:
Preventing Remote Desktop session timeouts due to idle tcp sessions
It's a good idea to configure keep-alives for the Remote Desktop Protocol.
A keep-alive of "1" ("send a keep alive packet every 1 minute") will make a TCP session appear to be "active" (not idle),
and will prevent idle tcp session disconnects on any networking equipment between your client and your Terminal Server.

Best regards
Jeffrey

[jkuijt]

Hi Mark,

I was wondering if the problem has been solved?

Best regards
Jeffrey

[admin]

Hello,

I found out recently that on some operating systems like 2012 R2 the reconnection feature would work only when using the "Use native Windows shell when opening sessions" option in the admin tool / server tile / Session Opening Preference.

[chopcomp]

issue does not appears to be fixed, i have updated to the latest version of tsplus... the one released today and switched to windows native and no luck

my machine is running windows 7 home edition.

[jkuijt]

Hi,

Home editions are limited, so don't use them.
Instead, use Pro or Ultimate.

Best regards
Jeffrey

[chopcomp]

Jeffery,

This machine has been working just fine for about a year or so... wonder if upgrading to windows 10 will help?

Thanks

[Inertiauk]

Hi, this problem has not been solved,
I have updated TSplus, i've switched to using windows for sessions instead of tsplus, its the same.

The only thing i haven't tried is installing the RDS role and switching to RDS mode under the license tab ? i wonder will this make any difference ? is it supported or do I need to have RDS licenses as well as TSplus to switch to this mode ?

I have set the keep alive to 1 as suggested, and keepalivetimout to 0, i've set it in local registry in both places as well as the group policy on the AD.

Its becoming a bit of a dead end for me.