Mike S
-
Posts
3 -
Joined
-
Last visited
Content Type
Forums
Articles
Labs
Videos
TechZone
Citrix Community Articles
Events
Profiles
Posts posted by Mike S
-
-
Did any of you find a fix by any chance? We recently updated to 2203 and had the ghost issue so we moved to 2203 CU2 and still have it. Was hoping their might be a fix or i might have to go back to 1912 LTSR. Thank you.
-
Hello Everyone. We updated on Monday the VDA from 1912 LTSR CU2 (I believe) to 2203 LTSR. Since then we have seen 2 very strange issues:
1. Users who have an inactivity of 10(ish) minutes get disconnected.
2. When they reconnect, it will sometimes connect them to another server.
When #2 happens, any files they have open will show in read only. So we have to find where the two sessions are (citrix monitor sometimes does not show both sessions which is another issue) and log them out of both and sometimes this makes them lose work (we tell users to save often, but you know how users can be).
A few details about our environment. We are using WS App and going to <domain>.cloud.com for the account. We use ADC's in HA to pass the traffic through to our network. We have two store front servers and two cloud connectors. Those have not been updated and I think they should, but I am trying to find a good documentation on how to do that. I'm hoping its easy but we;ve been learning that citrix is not easy at all.
I'm wondering if we should go back to the latest version of 1912 but we were having some issues with 1912 as well. Although the issues now with ghost sessions is much worse so I'll go back if needed.
We do have a support ticket and so far all support said was, its a good idea to keep all components up to date. I agree, but these ghost sessions i dont think should be happening even with some components on different versions.
Thank you for any help.
Since updating VDA to 2203 (and even 2203 CU2) users have ghost sessions
in XenDesktop 7.x
Posted
Browsing the forums after posting this and it looks like many people have been having this issue for a while with no real fix. The latest reply on a post I've seen is around Oct/Nov. Hoping someone might have a fix. Might need to go back to 1912.