Weoften find that the Citrix Receiver is already installed as part of the desktop software package at institutional clients. This is used to deploy other software and is tested and approved by the client.
Often the already installed version is older than the one that we normally use. It usually still works with our software, but tends to be slow to start or unreliable - I'm not sure if this is expected behaviour, but it is what we observe. I can replicate this by installing older versions on test PCs.
Ideally I would like to be able to run two versions of the Citrix Receiver side by side - the pre-installed older version, and our newer version. They should not impact each other. This is possible with many other pieces of software.
Just try to pack the second citrix receiver sw in App-v. We did that more than a few years ago as we used an old citrix 4.0 farm with the most possible new version of citrix pnagent and already had this new farm with the most sofisticated agent. That worked fine for the time we needed it. In fact you can install more than 2, as long as they are packed and virtually not seeing each other. I guess that works fine with receiver.
Recently I upgraded my system to Windows 11 with the latest AMD drivers (22.8.2). Everything works fine except my virtual desktop I need for work, my mouse pointer/cursor is invisible on white backgrounds. I tried multiple things to get it fixed but the only thing that works is reverting my AMD drivers back to WHQL 22.5.1. It seems that more people have this issue Citrix Workspace App: White mouse pointer when connecting from Win 11 to Win 10 - Receiver Compatibi...
When do expect the fix will take place? I think more and more people are having this issue. We already see here people are switching to Intel just for this reason. I don't want to push but if AMD doesn't provide a fix soon, people will turn. Not because they want to but they have to as they need to use the laptop to work.
There is slight workaround where you can click and drag the menu slider to the other monitor. I've been using excel and chats on my right monitor for anything I want to handle important. Would like to see this on known issues. Impact under estimated. Screenshots don't capture the issue. The user would have to take photo with physical camera. Thus your user base has difficulty proving it to you causing difficult traversing level 1.
Since last week I'm not able to downgrade the driver to a working version anymore. This occured after the most recent Windows 11 updates. We had to buy new laptops with Intel to avoid problems for the users in our company. Right now we have 6 new laptops with AMD we cannot use. So this is getting really annoying!
Is their an ETA on when this will be fixed? This needs sorting as a priority as we are getting loads of complaints. I will be sending the last batch of laptops back to the supplier and choosing laptops which are intel based. Please can we get an indication on when this will be fixed so we can communicate this to our users.
I have the same issue with thinkpad T16 gen 1 (21CH000JUS). AMD Ryzen 7 PRO 6850U + 680M. I figured out a walkaround: Open your Device Manager, then Display adapters=>Driver=>Update Drivers=>Browse my computer for drivers=>Let me pick from a list of available drivers on my computer, now choose "Microsoft Basic Display Adapter". With this old driver, I can connect my workspace with normal cursor. After using my workspace, I will do the same steps again and enable the latest driver for the other tasks/games. The good part for this is that there is no reboot needed. I really hope AMD can do better than this "Microsoft Basic Display Adapter"!
how do you deal with the problem when you have more then one display? I've tried the settings, but if I complete it like above. I can only use one of the three display I have.
Is there another solution? Downgrade to older drivers was not the correct solution.
Oh my gosh ninetiger you saved my rear! This was happening to multiple users in Microsoft Azure Virtual Desktop. I bought some AMD processors in HP Probooks out of desperation because they were in stock...and the first time I compromised....it bit me in the rear!
thank you @MadMess and others for reporting. I've had the issue as described across Win10 and Win11 over 5700XT and the only driver which supports a visible mouse cursor in full screen citrix workspace is 22.5.1. Hoping for a fix soon.
Having exactly the same issue as described by other users. The rollback worked for a period of time, but not recently. As a (poor) temporary workaround guys - you can try turning on the point trailer. It's not great and a bit laggy for me - but am using this till AMD can get a hotfix out.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
There are many questions online addressing how to enable Alt+Tab within the remote session, but not disable it. Naturally I've tried to do the reverse of these instructions but no luck. They typically suggest setting TransparentKeyPassthrough=Remote in the registry of the local machine, so I figured mine should have Remote already and I would just need to clear it or replace it with something else, but mine is a null value.
I had the same problem and solved it with an Autohotkey script. Autohotkey can intercept keypresses even when citrix has focus.This script will allow you to get out of your citrix session with Ctrl-F1.
If you have not used Autohotkey before: Download Autohotkey, install it, save the code above in a file named citrix.ahk, double-click that file. The hotkey is now active and the script is visible as a H icon in your taskbar.See here if you want to bind a different key.
I have a method for this that involves editing the registry on your local machine.It definitely counts as 'some other method' - essentially, it sets up a keyboard shortcut that (I think) passes the Win-key keystroke to your local machine.This opens your local start menu on top of Citrix - and from there you can Alt+Tab locally as normal.
Citrix has multiple entries in different parts of the registry, and also some settings that you can change with the Local Group Policy Editor (gpedit). Unfortunately, the only one I've found that helps is 'Hotkey13', which is only available in the registry.
Now, to access my local machine from within a Citrix session I press Shift+F1 to open my local Start menu and give focus to my local machine, and then while it is open Alt+Tab or anything else acts locally.
my setup:I use a windows desktop and 2 extra displayI put citrix on virtual desktop2, and fullscreen to all 3 screensuse the hotkey to toggle back to laptop host window virtual desktop 1 without any problem.
I am having performance problems with Citrix receiver when running forticlient real-time AV protection. The symptoms I see are mouse & Keyboard become very slow to respond in the citrix session. When trying to type, there will be a lag in the keystrokes showing up that could be ip to 1 second. Mouse performance is similarly lagging. If I disable the real-time protection, keyboard and mouse response become normal and responsive again. I am currently running Forticlient version 5.4.0 but have seen this as far back as 5.2.3. I am running citrix receiver version 4.3 but have seen the issue with several other versions as well.
In the forticlient configuration, disable the proxy setting (under File - Settings). I assume this changes the scanning to be flow based. After making the change, latency is similar to having Forticlient inactive.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
After installation, NT SERVICE\CitrixConfigurationReplication and NT SERVICE\CitrixClusterService must remain in the Administrators group on both StoreFront servers or propagation will fail.
After installation of the second server, NT SERVICE\CitrixConfigurationReplication and NT SERVICE\CitrixClusterService must remain in the Administrators group on both StoreFront servers or propagation will fail.
However, if you have StoreFront servers in multiple datacenters then you are probably using GSLB-enabled DNS names and StoreFront needs to resolve these names to VIPs in the local datacenter. Edit the HOSTS file (C:\Windows\System32\Drivers\Etc\HOSTS) on each StoreFront server with the following entries:
If StoreFront is installed on your Delivery Controllers then both functions share the same IIS website and the same SSL certificate. If you want to enable SSL for the Delivery Controller (XML) connection, then the cert name on each server must match the FQDN of the Delivery Controller. One option is to create an SSL certificate with the following Subject Alternative Names: the StoreFront load balanced DNS name and each of the Delivery Controller FQDNs. Then import this one certificate on all StoreFront/Delivery Controllers servers and load balancers. Or a wildcard certificate could match all of these names.
When you view a Subject Alternative Name certificate, on the Details tab, click Subject Alternative Name to verify that all names are listed, including the DNS name that resolves to the load balancing VIP.
The StoreFront Base URL should point to a URL with a FQDN that resolves to a load balancing VIP that load balances the StoreFront servers. Receiver uses this Base URL to connect to StoreFront. If remote, Receiver will first connect to NetScaler Gateway and then use Gateway to proxy a connection to the Base URL.
If you enabled Pass-through auth in the Authentication node it does not enable it from Receiver for Web. If you enable it in Receiver for Web, additional configuration is required on the Receiver side to fully enable pass-through auth.
3a8082e126