My Citrix Netscaler addon is fully updated and I'm on the latest RDM beta.
I'm running 2 separate Citrix Netscaler sessions, with the private session setting ticked:
Let's say I run session A first and then session B second. If I try to launch a Citrix desktop in session A, nothing happens.
Session A:
But if I launch the Desktop in Session B, it works:
Session B:
Now, if I try to launch Session B first and then Session A second, then I can run the desktop in Session A but not Session B. So even though RDM is able to open 2 separate Citrix Netscaler sessions, it seems to only work for the last open session.
I'm not sure which version was last working, I don't use this a lot but have just noticed this issue today. I know for sure it was working previously though, maybe 5~6 beta versions ago or maybe back in v13?
The other thing is, if I enable force 32-bit in both Citrix Netscaler sessions, then both will launch the desktops just fine:
But then the problem is that they do not AUTO SUBMIT the credentials, despite the setting already ticked:
If I do not force 32-bit, then auto submit works fine. So it seems like perhaps the Citrix Netscaler addon needs to be updated?
I'm using 64 bit RDM btw.
--------------------------------------------------------------------------------------------------------------------
I'm always using the latest beta RDM x64 version.
Local data source.
Hello,
A ticket has been opened to our engineering department regarding this.
The ticket number is DEVO-1127.
Best regards,
Jeff Dagenais
Hello,
Unfortunately we don't have a "real" fix for the issue with the desktops-- this is actually something that happens with the LogMeIn entry type too and it has to do with the IE embedded browser, which is a .NET control so we don't have much control over it.
The workaround is to use "Force 32 bits" as you already did. I've identified what caused the auto submit to fail in the "force 32 bits" mode and it will be fixed in the next RDM beta. Hopefully with this it should work better for you.
Regards,
Hubert Mireault
Hmm, not sure why it was working before, unless it's related to the recent Windows 10 1809 upgrade (but that was a month ago). Oh well, if the workaround works and achieves the same result, I am happy with that. Thanks for looking into this.
--------------------------------------------------------------------------------------------------------------------
I'm always using the latest beta RDM x64 version.
Local data source.
Auto refresh also doesn't work under force 32 bits.
--------------------------------------------------------------------------------------------------------------------
I'm always using the latest beta RDM x64 version.
Local data source.
I'll take a look, thanks for letting us know. :)
Regards,
Hubert Mireault
I made a fix for the automatic refresh and the delayed refresh settings, they should be available in the same version as the first fix.
Regards,
Hubert Mireault