![]() In the end though I really need to find a way to make this work with the newest Citrix client since I hate to depend on a legacy and unsupported client as a long-term solution. But we have been histant to upgrade because of the multiple logons on one device issue.Īnother solution to this problem would be to find a way to make it so that session stealing doesn't happen while using the legacy clients but I havn't been able to find a way to do that without a client connection method that supports workspace control. If we used the new Citrix client with PNAgent we could use workspace control to only connect to disconnected sessions. If it happens to logon to a seperate server everything is fine and it creates a new session as desired. You can also have the user log in once again to re-generate the logon duration graph. With our current legacy Citrix clients, if the second Generic1 account happens to logon to the same server as the first Generic1 account session it will "steal" the session from the first account. Citrix receiver login problems are often caused due to issues like installing a new application, an OS update, configuration changes and high profile load. We do NOT want the Generic1 session to roam to device B, we want a new and seperate session to log onto device B so the Gerneric1 account can be logged on twice. ![]() The same "Generic1" account needs to log in to device B. ![]() ![]() For example, account "Generic1" logs in to device A. Really the only issue I am having now without workspace control is unexpected and unpredictable "session stealing". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |