https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
t
We are not tracking assets to which our users connect / or from which they connect (not enough to collate the information at least). We log the user off the session, and that's pretty much the end of it for us. However, we are in the process of updating a bunch of our thin clients, and this problem has seemed to decrease over time.
d
This isn't related to ctxgfx.exe per chance?
c
I saw this type of strange behavior with fslogix. Dropped the software and went back to UPM.
b
@David Inglis I’ll check ctxgfx.exe. @Cory Zaner, no FSLogix in this delivery group, legacy 2008 R2. Started when we rolled out CU4, and is more prevalent with a specific app.
d
@Brandon Mitchell We get individual sessions appearing to freeze. Win2016, VDA 1906, FSL, WEM, some with GRID. Killing the affected user's ctxcfg.exe miraculously unfreezes their session and they can reconnect to it. Your prob may be different of course but thought i'd mention it 🙂
b
@David Inglis the session isn't disconnected, from both receiver and director it shows connected. I get access to the offending app today to do some troubleshooting.
d
@Brandon Mitchell Sorry yes i used the wrong term - in our case the session would be visually frozen on the client device. When killing the user's ctxgfx.exe process on the VDA, the session would un-freeze on the client device and the user could carry on working. You're right, there was no disconnecting or reconnecting going on.
👍 1
a
I don't really have anything new to report either. As we've been phasing in and out workstations lately. I probably should circle back to the users.
b
@David Inglis, yep, killing ctxgfx.exe brings the session back to life. So, now, what's the real fix?
t
What graphics policies do you have applied? Might be worth going through those one at a time?
👍 1
t
^^++
And... You're probably not going to like it 🙂 But silo some users and enable CDF trace? Not sure how else you could debug ctxgfx.exe 😞
or just upgrade the next LTSR in 2-3 months
OR... This might be a crazy idea... but you can change the graphic policy settings on the fly and ctxgfx will pick them up and apply them in a couple seconds
b
looks like they started having an issue when we upgraded from CU1 to CU4.
I have access to the app and I can reproduce the issue.
t
Wooo! you can repro!?
how long does it take for the issue to occur?
a
I've got the issue on CU3 as well.
t
like, can you make it repro in a minute or two?
a
err, had...
b
it's odd the app works fine until click a specific button in the app and it appears to freeze.
t
if it's that specific then you can start the CDF trace right before you click and stop it right after
d
@Brandon Mitchell from memory it was similar here - app worked fine until a particular button was pressed. Think it was google earth pro for some surveyors. will find out. we use Grid vGPU on the affected VDAs, do you?
b
no, GPU
Even though we're on Windows 2008 R2 we have Optimized for Wan enabled, meaning we're using Thinwire Plus. We had an issue a couple years back with a build of Adobe Reader DC where they introduced a custom mouse pointer and there was drag with the mouse pointer with Adobe Reader DC in their sessions, I opened a case with Citrix and they suggested changing from Optimized for WAN - Legacy OS (legacy graphics mode). This resolved that issue, I need to do some testing, but I suspect it's the cause of this issue.
t
We had a TON of problems when we switched away from Legacy Graphics on 2008 R2. Had to turn it back on. Now that we're on 2016, glad to have that gone!
b
I need to test, but I think CTX234028 solves my Adobe Reader mouse pointer issue. I need to verify but I also suspect using legacy graphics fixes this app issue... trying to build this test out now.
b
@Brandon Mitchell this may be off course but does it happen with different versions of workspace app? Had a situation not long ago where LTSR receiver worked and no version of WSA would
b
@Benjamin Crill most everyone is on 4.9.6001, I haven't tested with different version of Receiver. Yes, Receiver version is something worth investigating.
b
Gotcha. Our issue didn’t matter what version of ltsr as long as it was so sounds different but who knows
b
Confirmed, applying "Optimized for WAN - Legacy OS" with legacy graphics resolves this issue.
👍 1
s
Holy crap. I love this community!
👍 1
a
Shut up, really?
Awesome! I'll check it out Monday
s
On PTO today and was following along. Will test this out Monday.
b
it least with WS2008 R2 VDA
s
yea so we are on 2012R2 so not sure that would fix our issue
@Tim Riegler now that you are on 2016 do you see this behavior anymore?
t
We do not. All we're seeing is FSLogix problems due to crappy SAN firmward 😡
FIRMWARE even
s
what it like to still have a SAN? Seems so "legacy". LOL
b
#nosan
runahv 1
nosan 1
t
There IS a problem with Session Recording on 7.15 CU4. No mouse pointer movement tracked on WSA for Windows. Mac is OK. Receiver LTSR is OK.
HEY NOW! 😃 I'd love to get there. Can't justify the expense at the moment =(
s
sounds like your UX disruptions have cost more than the investment for Nutanix 🙂
@Benjamin Crill did I see you are leading a NUG now?
t
Yeah, well...soft dollars vs. hard dollars. That's not an easy sell here, unfortunately.
s
Yea so long as they are not turning away patients it's just soft dollars
t
floppy money
t
Hey @Trentent - complete side note: any update on a web client for CU? =D Even publishing the console on its' own server is painful =( (Sorry Brandon for hijacking your thread)
t
Oooooo I bet it's getting close
👍 3
I think we're going to connect soon-ish. I can pull back some curtains for your then
*than
?
t
then
Yay Engrish!
t
right then
b
So, I've switched my legacy 2008 R2 delivery groups to "Optimized for WAN - Legacy OS" and the mysterious lockup issue is gone. I "fixed" the Adobe Reader DC mouse issue with the REG key from CTX234028.
@Steve Elgan, I've be interested when you have a lockup, if you kill ctxgfx.exe for that user if the locked up user session comes to.
s
So we tried this yesterday with a helpdesk call and we could not terminate it (via director).
b
it's a system process, there is one for each user, I don't think I saw it in director. I had to kill it via task manager.
s
i'll share that with my helpdesk team
👍 1
I hadn't really had a chance to follow up with them about it. They just sent me an FYI on internal slack yesterday sometime
b
If it's the same thing, you'll see a rogue ctxgfx.exe consuming a bunch of CPU.
s
Not sure we have that symptom
If it's a system process, and we can't kill it from director, and director doesn't show the PID. How will they know which to kill? Gotta make it easy for the helpdesk otherwise they'll just log the user out and call it good.
b
at least they are just logging them off, here our help desk loves to reset profiles for everything... sometimes humorous because we'll get an ticket escalated to us saying settings aren't saving, we've reset the profile 3 times and they still aren't saving.
anyhow, if there isn't a rogue ctxgfx, matching that up to a user session wouldn't be easy.
d
I think ctxcfg.exe runs in the user's context, so you will see a bunch of ctxcfg.exe's in task manager or equiv, so helpdesk can kill the right one.
No i am wrong sorry.
Controlup ties them up if that helps, looking under the user's session you can see their ctxcfg.exe with PID, right-click kill.
s
Yea this particular environment doesn't have control up, but we do have EG so I'll check that.
4 Views
Open in Slack
PreviousNext
Powered by