Jump to content
Updated Privacy Statement

Leo Singleton

Internal Members
  • Posts

    1
  • Joined

  • Last visited

  • Days Won

    6

Posts posted by Leo Singleton

  1. 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.

    • Like 8
×
×
  • Create New...