Jump to content
Welcome to our new Citrix community!

Do not allow user session to roam from one client to another


Deepak Arora

Recommended Posts

Hi,

We are using XenDesktop/XenApp 7.5 and we do not want a user's application session to roam from one client to another.

So, if the user logs into the storefront from a client machine and launches an app, we do not want that when the same user logs into the storefront from another client machine and launches the same app, the app session from the previous client is taken over.

Somehow, it is extremely critical for our application. Any of the following scenarios will work:

1. Start a new app session and leave the previous one running on the previous client

2. Kill the old session and start a new one on the new client

3. Prevent user from starting a new session on the new client

 

I have already tried disabling the workspace control, turning off auto reconnect at logon to false and terminate the application session in the web.config file on the server.

Also, setting the WSCReconnectMode/User key to 0 in the registry on the client machines. 

Nothing seems to work and the clients are able to grab the active session from each other.

 

Any help is greatly appreciated.

 

Thanks

 

Link to comment
Share on other sites

  • 2 weeks later...

Hi,

 

We have exactly the same problem.

Xenapp 7.5 / Storefront 2.5.2 , workspacecontrol setting autoreconnect does not work, also WSCReconnectMode/User key does not work.

 

Dissappointing.....

 

Regards

 

Steve

Link to comment
Share on other sites

  • 2 months later...

I have a school that would really like to turn off workspace control because the teachers would like to be able to keep certain apps running on their desk machine while running different apps from their teaching machine and right now the apps follow them no matter the settings.

 

They have XenApp 7.5 on Windows 2012 servers and on the internal network they are using WI with a PN Agent site and on the client machines they are using the 12.3 online plugin.  Even though all the workspace control settings in WI are set to not reconnect apps on logon the apps still follow the users.

 

They are getting very frustrated and would like a solution.  Does anyone have anything new on this topic?

Link to comment
Share on other sites

  • 3 weeks later...

Hello,

Have you try this :

 

On XenApp 7.6, you can try the experimental SessionReconnection setting available via PowerShell. On any Server OS delivery group, run:

 

Set-BrokerEntitlementPolicyRule <Delivery Group Name> -SessionReconnection <Value>

 

Where <Value> can be:

Always - This is the default and matches the behavior of a VDI session. Sessions always roam, regardless of client device.

DisconnectedOnly - This reverts back to the XenApp 6.x and earlier behavior. Sessions may be roamed between client devices by first disconnecting them (or using Workspace Control) to explicitly roam them. However, active sessions are not stolen from another client device, and a new session is launched instead.

SameEndpointOnly - This matches the behavior of the "ReconnectSame" registry setting in XenApp 6.x. Each user will get a unique session for each client device they use, and roaming between clients is completely disabled.

This will change the roaming behavior for desktop sessions. For app sessions, use:

 

Set-BrokerAppEntitlementPolicyRule <Delivery Group Name> -SessionReconnection <Value>

 

Unfortunately, this feature was not fully tested in time for the 7.6 release and thus remains experimental. Offhand, the only known issue I'm aware of is that it doesn't work properly with Connection Leasing, and during a database outage, the roaming behavior will revert back to the default of Always. If you find any other issues, please report them via support, however we can't commit to fixing them until the next release.

 

http://discussions.citrix.com/topic/351114-xenapp-75-multiple-sessions-with-the-same-user-account/?do=findComment&comment=1838747

Link to comment
Share on other sites

  • 6 months later...

In our case, we were not using Web Interface/Storefront but static ica files with pass-thru authentication enabled. After setting up a published app to run from a single server, we quickly saw that the same user logging in on two machines would pull the session back and forth between the two pc's.

 

If we added a 2nd server to the published app, it would take 3 connections using the same credentials to force roaming of a session to the 3rd client. As long as there is another server the user can hit, the session doesn't move.

 

To stop this roaming behavior, in the RDS Host Configuration set "Restrict each user to a single session" to No.

Link to comment
Share on other sites

  • 4 years later...
On ‎11‎/‎3‎/‎2014 at 11:42 AM, Julien Bebronne said:

Hello,

Have you try this :

 

On XenApp 7.6, you can try the experimental SessionReconnection setting available via PowerShell. On any Server OS delivery group, run:

 

Set-BrokerEntitlementPolicyRule <Delivery Group Name> -SessionReconnection <Value>

 

Where <Value> can be:

Always - This is the default and matches the behavior of a VDI session. Sessions always roam, regardless of client device.

DisconnectedOnly - This reverts back to the XenApp 6.x and earlier behavior. Sessions may be roamed between client devices by first disconnecting them (or using Workspace Control) to explicitly roam them. However, active sessions are not stolen from another client device, and a new session is launched instead.

SameEndpointOnly - This matches the behavior of the "ReconnectSame" registry setting in XenApp 6.x. Each user will get a unique session for each client device they use, and roaming between clients is completely disabled.

This will change the roaming behavior for desktop sessions. For app sessions, use:

 

Set-BrokerAppEntitlementPolicyRule <Delivery Group Name> -SessionReconnection <Value>

 

Unfortunately, this feature was not fully tested in time for the 7.6 release and thus remains experimental. Offhand, the only known issue I'm aware of is that it doesn't work properly with Connection Leasing, and during a database outage, the roaming behavior will revert back to the default of Always. If you find any other issues, please report them via support, however we can't commit to fixing them until the next release.

 

http://discussions.citrix.com/topic/351114-xenapp-75-multiple-sessions-with-the-same-user-account/?do=findComment&comment=1838747

 

This doesn't work for application Delivery Groups?

Link to comment
Share on other sites

  • 6 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...