How can ControlUp Edge DX prompt users to confirm disconnects or logoffs in Citrix sessions to avoid hung VMs?

Hello. We are seeing lots of issues with users getting disconnected from sessions, and then not being able to reconnect to the VDI environment due to hung sessions on the VMs. Due to lack of training/access, our tier 1 staff can’t access Director to restart the VM and force release the session so that the user can reconnect to a new session. This is leading to tickets sitting in queues, and users waiting hours for what should be a 30 second "fix". There are quite a few settings in Citrix/iGel and with the infrastructure that we’ve made changes to that has drastically improved the performance of VDI, but we’re still experiencing the session hangs, and seem to be seeing more lately. Trying to log off or disconnect the user via Director is not doing anything either.

is there a way to use EdgeDx to send a prompt to a user when they disconnect from their Citrix session without logging off, to ask if the user meant to disconnect, or if they would like to log off of their session? if the user clicks yes, it initiates a script on ControlUp Real-Time DX to log user off of the session, and then customize the log off script to perform a check to see if the user actually logged off, and if not, to restart the VM?

Sorry if my verbiage is confusing or just wrong, pretty new to this VDI stuff.

Very interesting use case.. @member what do you think?

The issue here is making 100% sure the endpoint where you send the message too is actually used by the same users (users can have multiple endpoints and different username on the local endpoint). Could be doable though

You’d have to make a few assumptions.

• Client machines have unique names OR both Edge and RemoteDX are in use

• Edge API allows you to call scripts

In real-time DX you’d create a trigger:

• When user disconnects

• Run a script follow up action

• Script checks if client machine exists in Edge

• If so, initiate a pre-existing script against that machine/user via Edge

Ah, that would be problematic for the company I work for. Still trying to understand the logic behind past decisions, as I’m not sure if they are optimal or not, but one issue is that we have contractors signing in with a generic local login, then connecting to VPN/Citrix with their own credentials. So the local username would be something generic.

We do have unique names for all endpoints. We have RemoteDx and just did a PoC for EdgeDx, so in the process of purchasing licenses for that. Could this solution still work, considering the generic local usernames that a subset of users are using to access the local clients?So there is only 1 user on the client machine right?

for the thick clients that users use to access VDI, they are 1 user. the iGel are generally in training/onboarding areas, so they do have multiple users. However, we don’t have have AD authentication set up on the iGel, so the user only signs into the storefront, and they never actually sign into the iGel (at least from my understanding).

You can get the client name from real-time DX (RTDX). You can use that client name to lookup the machine in Edge.

Your challenges are going to be:

• When the user disconnects, the client name is gone. You can perhaps work around that by including client name = * in the trigger criteria. That way the cutriggerobject will have the previous value. I haven’t tested this. You might NOT have it, depending on timing.

• How are you going to capture the input on the client side? It isn’t impossible. But it would involve timeouts and assumptions. You could use monitor exports to lookup the user session and the previous clientname

Hi, have you seen this article before? I recall seeing a similar issue with freezing and grey/black screens a while back. It’s possible that it’s not related but probably worth checking out. https://cloudcomputing.help/kb/how-to-resolve-citrix-virtual-apps-and-desktops-edt-and-dtls-issues/?utm_content=expand_article

Hello. I just went through it, but it is not currently applicable to us. The article helps for my next project to convince management to allow adaptive transport though, so it is much appreciated. According to the tech I took over for, our INF architect didn’t want to allow the EDT/UDP protocol to be used in our environment, though I’m not sure if that is still the case. I have it on our stage environment, and was just about to start testing with users experiencing poor connectivity issues; see if i get flagged.

I really appreciate the guidance here, everyone! I’m eager to learn, and going to start testing some of the possible solutions listed here. I just didn’t want to go down a fruitless rabbit hole because I don’t understand IT -_- Will leave a message here if i get it working!Are you running 2303 of the vda? It is a known issue with reconnecting a disconnected session https://support.citrix.com/article/CTX547782/cvad-2303-users-stuck-on-welcome-screen-when-reconnecting-to-a-disconnected-session

Continue reading and comment on the thread ‘How can ControlUp Edge DX prompt users to confirm disconnects or logoffs in Citrix sessions to avoid hung VMs?’.  Not a member? Join Here!