How do I force WVD to route a connecting user to a disconnected session he has on host x?

%3CLINGO-SUB%20id%3D%22lingo-sub-552034%22%20slang%3D%22en-US%22%3EHow%20do%20I%20force%20WVD%20to%20route%20a%20connecting%20user%20to%20a%20disconnected%20session%20he%20has%20on%20host%20x%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552034%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20background%20is%20that%20I%20want%20my%20users%20to%20be%20able%20to%20loose%20the%20connection%20and%20still%20have%20the%20session%20available%20at%20the%20RDS%20side%20for%20a%20few%20hours.%20I%20want%20to%20cover%20scenarios%20like%20computer%20going%20to%20sleep%20etc%20and%20still%20keep%20any%20partial%20work.%26nbsp%3BI%20also%20use%20FSLogix%20profile%20shares%20to%20hide%20the%20fact%20that%20users%20can%20end%20up%20on%20one%20of%20many%20session%20hosts.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20get%20this%20to%20work%20with%20a%20single%20session%20host.%20WVD%20then%20picks%20the%20only%20available%20session%20host%20and%20the%20disconnected%20user%20session%20is%20automatically%20used.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20add%20a%20second%20session%20host%2C%20it%20seems%20that%20WVD%20does%20not%20care%20that%20the%20user%20already%20has%20a%20session%20on%20session%20host%20x%20and%20happily%20routes%20the%20user%20to%20session%20host%20y.%20(Where%20a%20completely%20new%20session%20is%20created%20-%20Adding%20to%20the%20problem%2C%20the%20profile%20share%20on%20FSLogix%20is%20locked%20by%20the%20disconnected%20session%20-%20a%20local%20profile%20on%20the%20machine%20is%20created%20after%20a%20timeout%20-%20this%20breaks%20my%20shared%20profile%20approach)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20can%20I%20force%20WVD%20to%20route%20users%20with%20disconnected%20sessions%20to%20the%20disconnected%20session%3F%3C%2FP%3E%3CP%3EHow%20can%20i%20configure%20FSLogix%20to%20fail%20the%20session%20rather%20than%20falling%20back%20to%20local%20profiles%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EJohan%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-552067%22%20slang%3D%22en-US%22%3ERe%3A%20How%20do%20I%20force%20WVD%20to%20route%20a%20connecting%20user%20to%20a%20disconnected%20session%20he%20has%20on%20host%20x%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552067%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309051%22%20target%3D%22_blank%22%3E%40Johan_Eriksson%3C%2FA%3E%26nbsp%3BSo%20basically%20you're%20asking%20for%20what%20Citrix%20is%20calling%20%22Auto%20Client%20Reconnect%22%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmyxenapp.com%2F2014%2F04%2F11%2Fdifference-between-session-reliability-auto-client-reconnect-and-ica-keep-alive-feature%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmyxenapp.com%2F2014%2F04%2F11%2Fdifference-between-session-reliability-auto-client-reconnect-and-ica-keep-alive-feature%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20hoping%20this%20would%20be%20a%20native%20function%20in%20WVD.%20This%20is%20quite%20important.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-552226%22%20slang%3D%22en-US%22%3ERe%3A%20How%20do%20I%20force%20WVD%20to%20route%20a%20connecting%20user%20to%20a%20disconnected%20session%20he%20has%20on%20host%20x%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552226%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F153507%22%20target%3D%22_blank%22%3E%40Ola%20Holtberget%3C%2FA%3E%26nbsp%3BI%20also%20had%20hoped%20it%20was%20supported.%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20I%20am%20just%20lacking%20some%20simple%20configuration%20step.%26nbsp%3B%3C%2FP%3E%3CP%3EOtherwise%20I%20will%20have%20to%20terminate%20sessions%20on%20any%20kind%20of%20disconnection%20such%20computer%20going%20to%20sleep%20which%20will%20lead%20to%20a%20worse%20user%20experience.%20Or%20I%20could%20possibly%20get%20a%20MUCH%20bigger%20session%20host%20and%20have%20just%20one%2C%20if%20this%20really%20is%20a%20WVD%20limitation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-552354%22%20slang%3D%22en-US%22%3ERe%3A%20How%20do%20I%20force%20WVD%20to%20route%20a%20connecting%20user%20to%20a%20disconnected%20session%20he%20has%20on%20host%20x%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552354%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F153507%22%20target%3D%22_blank%22%3E%40Ola%20Holtberget%3C%2FA%3E%26nbsp%3BTo%20be%20clear%3A%20I%20can%20accept%20another%20login%20-%20But%20I%20want%20WVD%20to%20connect%20the%20the%20existing%20session%20host%20x%2C%20not%20create%20a%20new%20one%20on%20host%20y%20in%20addition%20to%20the%20one%20in%20disconnected%20state%20on%20host%20x.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-552648%22%20slang%3D%22en-US%22%3ERE%3A%20How%20do%20I%20force%20WVD%20to%20route%20a%20connecting%20user%20to%20a%20disconnected%20session%20he%20has%20on%20host%20x%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552648%22%20slang%3D%22en-US%22%3EOdd%2C%20it%20seems%20that%20WVD%20understands%20that%20the%20disconnected%20session%20exists%20because%20it%20re-uses%20the%20same%20SessionId%2C%20but%20it%20sends%20the%20connection%20to%20%22the%20wrong%22%20session%20host%20y%20when%20the%20disconnected%20session%20with%20that%20SessionId%20exists%20on%20session%20host%20x.%20I%20end%20up%20with%20two%20sessions%20with%20the%20same%20SessionId%20for%20the%20same%20user.%20(One%20on%20host%20x%20and%20the%20other%20on%20host%20y)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-552693%22%20slang%3D%22en-US%22%3ERe%3A%20How%20do%20I%20force%20WVD%20to%20route%20a%20connecting%20user%20to%20a%20disconnected%20session%20he%20has%20on%20host%20x%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-552693%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F309051%22%20target%3D%22_blank%22%3E%40Johan_Eriksson%3C%2FA%3E%26nbsp%3BAlso%20running%20into%20the%20same%20issue.%20If%20a%20user%20disconnects%20for%20any%20reason%2C%20when%20attempting%20to%20reconnect%2C%20they%20get%20assigned%20a%20new%20session%20host%20as%20opposed%20to%20taking%20over%20their%20existing%20disconnected%20session.%20I%20have%20replicated%20this%20to%20happen%20every%20single%20disconnect%2Freconnect%20attempt.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-822651%22%20slang%3D%22en-US%22%3ERe%3A%20How%20do%20I%20force%20WVD%20to%20route%20a%20connecting%20user%20to%20a%20disconnected%20session%20he%20has%20on%20host%20x%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-822651%22%20slang%3D%22en-US%22%3EBy%20default%20FSLogix%20and%20WVD%20configured%20to%20reconnect%20to%20original%20session%20and%20rw%20access%20to%20the%20profile.%20I%20would%20imagine%20if%20you%20look%20at%20program%20data%20of%20vm%20that%20there%20is%20a%20profile%20issue%20listed%20in%20profile%20log.%20Usually%20the%20issue%20is%20permissions%20related%20for%20the%20container%20share.%3C%2FLINGO-BODY%3E
Contributor

The background is that I want my users to be able to loose the connection and still have the session available at the RDS side for a few hours. I want to cover scenarios like computer going to sleep etc and still keep any partial work. I also use FSLogix profile shares to hide the fact that users can end up on one of many session hosts.

 

I get this to work with a single session host. WVD then picks the only available session host and the disconnected user session is automatically used.

 

When I add a second session host, it seems that WVD does not care that the user already has a session on session host x and happily routes the user to session host y. (Where a completely new session is created - Adding to the problem, the profile share on FSLogix is locked by the disconnected session - a local profile on the machine is created after a timeout - this breaks my shared profile approach)

 

How can I force WVD to route users with disconnected sessions to the disconnected session?

How can i configure FSLogix to fail the session rather than falling back to local profiles?

 

Thanks,

Johan

 

 

6 Replies

@Johan_Eriksson So basically you're asking for what Citrix is calling "Auto Client Reconnect" ?

 

https://myxenapp.com/2014/04/11/difference-between-session-reliability-auto-client-reconnect-and-ica...

 

I was hoping this would be a native function in WVD. This is quite important.

@Ola Holtberget I also had hoped it was supported. 

I hope I am just lacking some simple configuration step. 

Otherwise I will have to terminate sessions on any kind of disconnection such computer going to sleep which will lead to a worse user experience. Or I could possibly get a MUCH bigger session host and have just one, if this really is a WVD limitation.

@Ola Holtberget To be clear: I can accept another login - But I want WVD to connect the the existing session host x, not create a new one on host y in addition to the one in disconnected state on host x. 

Odd, it seems that WVD understands that the disconnected session exists because it re-uses the same SessionId, but it sends the connection to "the wrong" session host y when the disconnected session with that SessionId exists on session host x. I end up with two sessions with the same SessionId for the same user. (One on host x and the other on host y)

@Johan_Eriksson Also running into the same issue. If a user disconnects for any reason, when attempting to reconnect, they get assigned a new session host as opposed to taking over their existing disconnected session. I have replicated this to happen every single disconnect/reconnect attempt.

By default FSLogix and WVD configured to reconnect to original session and rw access to the profile. I would imagine if you look at program data of vm that there is a profile issue listed in profile log. Usually the issue is permissions related for the container share.