Something weird that I noticed is if I lock my machine, then unlock it, my sessions will reconnect. Also worth noting is that when I select the value of ‘4’, which is supposed to reconnect sessions when the Receiver interface opens, that does not work either. However, the Receiver will not reconnect sessions at Windows logon I tried creating the same entry under the HKCU key, but it does not fix it either. If I change it from the default value of ‘3’ to ‘8’ it fixes the Refresh issue and the issue where all sessions are reconnected if a single session is launched. I tried to resolve this by modifying the WSCReconnectMode entry in the HKLM\Wow6432Node\Citrix\Dazzle key. After reading up on this further, I realize that this is by default. I also notice the following different behaviors in Receiver 4.x (1)when logged into a local machine, hitting ‘Refresh’ from the Receiver reconnects all disconnected/active sessions AND (2)when logged into a local machine, launching a single session will also reconnect any other disconnected/active XenDesktop and/or XenApp sessions. This feature is not working in Receiver v4.x (I have tried 4.2, 4.3, and 4.3.100). Currently, we have v3.3 in production and when a user logs into their LOCAL machine, if they have a disconnected and/or active session it will automatically launch. We are in the process or testing Receiver v4.3.100 for rollout to our LAN based machines.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |