Menu
Hi Carl, can you help me? I’m implementing peripherals in a Citrix XenApp 7.15.3000 environment, I have a problem with one of them, it’s a HID Omnikey 5022 Smart Card Reader, basically what the device has to do is read the user cards of the company by means of a software (not for authentication) I tried everything, I have an open case with Citrix, but they have not been able to help me. I followed the following tutorial: I have tested with Citrix XenDesktop, delivering virtual desktops based on Windows 7 and Windows 10 and it works perfectly, but by Citrix XenApp based on Windows 2012 or 2016 it does not work.
After you logging in to your account, you can launch a Citrix applications by single-clicking on its respective icon. It may take a few moments for the application to virtualize depending on your internet connection and the application you are trying to open.
Do you have any idea how it could work? Beforehand thank you very much. What is the latest version of Citrix Receiver that can be used again XenApp 6.5 with minimal issues? I tried to look for a document in which Citrix said, in effect, “If you use anything beyond the version of Citrix Receiver, you are more likely to run into problems” but couldn’t find one. In a forum, I saw a Citrix employee make a comment that using more recent versions of Receiver was problematic against 6.5 but then they proceeded.not.
to recommend a best and final version. Yes, I am well-aware that 6.5 is out of support. Yes all work fine with the Gateway FQDN but when we enter the alias FQDN it doens’t work. We try with the alias because the adress is more complicate for our users: the fqdn of the netscaler is netscaler-gateway.domain.com, and we create an alias in our dns ok.domain.com for having an more simple adress. When our customers are not in our place, they can use an internet browser with the adress ok.domain.com and all is ok. We try to enter ok.domain.com in Citrix Workspace App and it doesn’t work, but, when we enter netscaler-gateway.domain.com, it works.
Is it possible to make it work with ok.domain.com?(sorry for my bad english, i hope you understand what i mean, and thank you for your responses). Hi Carl I have two questions regarding an issue with beacon / location detection we have with the Workspace Client for Mac. We have the issue that sometimes the Workspace Client for Mac tries to reach the – unreachable – internal beacon from outside our network for 80 seconds while ignoring the – reachable – external beacons which results in a 80s wait time for the user until he can connect. We do not need the check because all our users connect from the outside (external) through a netscaler gateway to the storefront server – there is no “internal” connection possible 1.
Where are the settings stored on a Mac which are part of the registry on a Windows client and how can they be changed (if not available through the app itself)? Is there a way to disable the whole location checking (internal/external) that the Workspace Client always performs after a network adapter change. The last few days we have seen an increasing number of users not being able to connect to Xenapp desktop via Storefront. What we have seen on all affected clients, Receiver is ver. 4.9 HDX plugin 2.4 is installed Security update to Flash player has resently been installed KB4343902.
What we also see in event log is this: Product: Citrix HDX RealTime Media Engine 2.4 — Error 1706. An installation package for the product Citrix HDX RealTime Media Engine 2.4 cannot be found. Try the installation again using a valid copy of the installation package ‘HDXRealTimeMediaEngine2.4forWindows.msi’. We fixed It by uninstalling HDX plugin and receiver, and then running “clean up” tool reboot pc Then reinstalling receiver and hdx plugin Do any of you guys have experienced this issue?
Are HDX plugin integrated in new Workspace client, or Is it still an separate component? Hello Stefan, Sorry for the late reply. We had a similar problem. The icon you use for the published application is the problem. It needs to include the following sizes (in px): 16×16, 32×32, 48×48 at a minimum.
To accommodate for high dpi devices we also add 128×128, 256×265 and 512×512. Many times even the vendors have only one size for an application icon, which is just laziness, but causes this issue for us. I use icofx3 to merge all the sizes into a single.ico file. We have reported this issue to Citrix in 2017. I believe Citrix Receiver v4.11 might have fixed this issue though?