Enforcing single session mode

[cmarsura]

Hi
I am trying to enforce single session mode on one server. It works well when I connect same user from same machine or another machine using same connection method:
Html5 reconnecting over Html5: OK, reconnect to same session
RemoteApp reconnecting over RemoteApp: OK, reconnect to same session

What seems to not work is:
A) When using cross connection, for example connecting a previously connected Html5 user, with a new connection using RemoteApp (and viceversa) creates a new connection, resulting in two active sessions.
B) When using client generator to connect to an existing session, the session is initially captured but next it is terminated, so I end with 0 active sessions. This happens whether I launch generated client executable from same machine or another machine.

- On tsplusadmin > Server > Group Policies of the application server I have set:
-- Only one session per user: The second session will capture the first one
-- Allow users reconnections when sessions are disconnected : checked
-- Allow automatic reconnections when a session is disconnected: checked

Am I missing something?

Best

OS: Windows 2012 R2
Application server: Flexi Cloud 10.40.7.7
Reverse-Proxy server Flexi Cloud 10.40.7.7

[John]

Hello,

If your goal is to inforce the rule "only one session per user", then I recommend you to use the option

"The second session will be logoff"

I think this will do the job you are expecting, because, at logon, TSplus will look if an other session exists for this user.
If yes, it will immediatly logoff.

Kind regards

John

[cmarsura]

Hello John.

No, I want that the user can grab the existing connection without logging off the existing session, but with the advent of Flexi Cloud 10.40.7.7 things has slightly changed:

What seems to not work now is:
A) When using cross connection, for example connecting a previously connected Html5 user, with a new connection using RemoteApp (and viceversa) the user is unable to grab the existing session (a new session is created and immediately destroyed);
B) When using client generator to connect to an existing session, the session is initially captured but next it is terminated, so I end with 0 active sessions. It happens whether I launch generated client executable from same machine or another machine. NOTE: this happen only if I set the startup program in the Windows Client Generator; leaving the field blank causes the client to behave as a Remoteapp launched from web page, with same limitations described in A);

Best.
Carlo

[cmarsura]

Any news on the argument ?

[John]

Hello,

Let me explain you more in detail what is behing these questions.

IF you are using "The second session will be logoff", and only with this specific option, we do not use the Windows system.
It is TSplus logon process which is detecting that a new customer is a second session and TSplus is processing the logoff.
For all other case, we just use registry settings and it is Windows standard behavor which prevail.

-- A) When using cross connection, for example connecting a previously connected Html5 user, with a new connection using RemoteApp (and viceversa)

This absolutly expected.
In HTML5, the client IS NOT on the user PC. The connection client run on the server side and it is our server side technology which turn the session trafic into a pure web (HTML5) trafic.
In RemoteApp, the client run on the user PC.
So, this is a completly different paradygm.
This is why we cannot, technically, handle such kind of "cross connection" cases.

Kind regards

John

[cmarsura]

Now things are clear.

Thank you for attention, John.

Carlo