Citrix Receiver Cleanup Utility For Windows Free Download

0 views

Skip to first unread message

Stephany Tousley

unread,

Aug 5, 2024, 2:36:27 PM8/5/24

to chicmerecom

Thisis what my installation directory looks like. But when I install the Receiver on a user's PC, they only get like 6 DLLs and the CDViewer.exe. Everything else is missing, so they can't open anything from Citrix.

His receiver installation was originally messed up. So I tried uninstall and re-installing, but it kept saying it was already installed. So I ran the cleanup utility and then installed it from the login prompt. Which didn't work. So I repeated the process and installed from That also didn't work, so I repeated the process once more and then installed from But it also didn't work.

Thank you for this. I have run into the 1612 issue with various components before myself. The script uses the Receiver clean-up utility (in addition to its own clean-up logic) which usually cleans up the HKLM MSI product keys fairly well. I did add cleanup logic in the script for the Products key under HKCU since I saw one or two of those products keys getting left behind.

There was a feature enhancement request submitted to the Development team and I provided the method to load the Classes user hives to clean up the user profile section. Citrix added this code to the Receiver Cleanup utility released in September 2018 version 2.3.0.42 .

The use case that you provided is what triggered contacting Citrix Support.

The issue we experienced was a system level install of CR was already done via SCCM, Storefront is configured by default to install CR if its not installed on the client, well most users were running Chrome and Storefront was not able to properly search for the Receiver install because Google disabled the NPAPI plugin feature, therefore thousands of machines with both user and system level installs of wfica32.exe.

I have also seen cases with both user and system level installs of CR crashing on the wifa32.exe process.

In addition to the RCU enhancement request, I have also requested that the Citrix Receiver installer never attempt to install in user-mode if a system level install is already present. Citrix Development team has changed this install check beginning with CR 4.12, 4.9.6000 LTSR (maybe even CU5) and CWA 18.12 to resolve this chaos.

Please, feel free to reference this post and the script to Citrix with you enhancement requests. I tried going that route years ago and had less success than you have had. I needed to create this script or the issue was going to haunt me forever.

I like the new feature of a CR system level install has higher priority than a user-level install better than applying a GPO anyway.

There is still the risk of a user-level occurs first, but with our Storefront servers modified to no longer install Receiver, the user would need to goto Citrix.com and install as a non-admin for this to happen.

Steps for your blog visitors: (Curious on their responses: System-level Only, User-level Only or both System-level and User-level installs)

The best way to check is logon to a workstation as admin and open a command prompt, make sure your at the root c:\ drive and type: C:\dir /s wfica32.exe

Yes, I see this. Other items in there are hard coded in that array, but then later have more intelligent detection later in the code. This one needs some tweaking to catch variations. I will add this soon.

Here is the error log (PDQ)

Loading profile registry hives for username: xxxx

Loading profile registry hives for username: xxx

Loading profile registry hives for username: xxxx

The wrapper that PDQ users is catching some error and failing. The fact that it is getting the error when trying to load the cleanup utility leads me to think that that is related. Did you download that utility and deploy it along with the script in the script location? If PDQ does not copy the utility along with the script it will fail. The cleanup utility EXE needs to be present wherever PDQ is launching the script from.

Mark this is quite a post. We have been grappling with an issue where desktop shortcuts are only delivered to Admin users and not others (with workspace app 1912ltsr and beyond), whereas the same users get the shortcuts delivered if i use Citrix receiver 3.3. I am talking about a Hybrid Virtual Desktops and applications platform.

Citrix XenApp is a commercial tool that allows users to remotely access "published" applications. It allows reasonable application performance over the internet. Citrix works well with most applications, but is not well-suited for graphics-intensive applications. Graphic intensive applications require a product like RGS.

Many applications available on the desktop computers in the labs are provided through Citrix. Upon selecting one of these applications, a connection is made to a Citrix terminal server, and the application is shown locally, but is running remotely. Seamless integration causes the application to look like it is running locally. Unlike RGS, Citrix servers are a shared resource. There can be several users logged onto the same Citrix server simultaneously. Each Citrix server has multiple processors and generous memory allocations.

If accessing Citrix from a Windows desktop/laptop, you can use any internet browser (IE/Edge works best, but Firefox and Chrome work also) to go directly to the CAEDM Citrix web interface. After logging in with your CAEDM credentials, you will be prompted to accept the install of the Citrix client software. On Windows, this is a quick, painless, "download, next, next finish" process.

When accessing Citrix from a RedHat desktop/laptop, go directly to the CAEDM Citrix web interface. After logging in with your CAEDM credentials, you will be prompted to accept the install of the Citrix client software. as you would on a Windows machine. Find the tar.gz file that was just downloaded, and extract it (tar -xvf filename.tar.gz).Run setupwfc, in the configuration, set the default directory to be /usr/lib/, choose 'yes' to integrate with KDE and Gnome, do not install USB support.Open /etc/bashrc in vim, or your preferred text editor, and add: export LANG=C to the first line of the file.Run /usr/lib/ICAClient/wfica to test for dependiencies.

First you need to download the Citrix receiver from [1] (My testing was down with Receiver version 13.5). Choose Debian Packages and download the web package (the full package instructions are below). Next install the .deb file you just downloaded either with the software manager or by navigating to the file in the terminal and running something like this sudo dpkg -i icaclientWeb_13.5.0.10185126_amd64.deb

Finally you need to restart you browser and navigate to CAEDM Citrix web interface. Ignore the Install by clicking skip to log on because if you look above the install button will give you the receiver for red hat which won't work for Debian-based linux.

Similar to the Web Receiver you need to download the Citrix receiver from [2] (My testing was down with Receiver version 13.5). Choose Debian Packages and download the full package receiver. Next install the .deb file you just downloaded either with the software manager or by navigating to the file in the terminal and running something like this sudo dpkg -i icaclient_13.5.0.10185126_amd64.deb

Next you need to add more SSL certificates. By default, Citrix Receiver only trusts a few root CA certificates, which causes connections to many Citrix servers to fail with an SSL error. The 'ca-certificates' package (already installed on most Ubuntu systems) provides additional CA certificates in /usr/share/ca-certificates/mozilla/ that can be conveniently added to Citrix Receiver to avoid these errors:

Finally launch the citrix receiver by searching for it in the application menu. After you agree to the EULA it will prompt to you to add a server enter and you should prompted to log in. Use your caedm username and password and et.byu.edu as the domain.

Use the Java client for tech podiums, internet cafes, or any computer where it is not possible to install the Citrix client, but Java is installed. The Java client is slower to react to user input and may not produce the best user experience compared to the Citrix receiver as explained above. The Java client displays a desktop with a start menu in a browser instead of individual applications in their own windows.

Once the Citrix Receiver is installed, access Citrix applications through the CAEDM Citrix website. The website will show a series of folders and icons available to launch. Clicking on program icons will cause that software to load in a separate window on your computer. To log out of Citrix, exit the software accessed through Citrix using File -> Exit, or the equivalent menu option.

Citrix will automatically detect existing printer drivers on the local computer. Citrix also permits printing to the CAEDM printers. Citrix also provides standard office programs that are omitted on the RGS blades. In order to print from a Citrix session simply print the file as you would normally. To print to the CAEDM printers, select CAEDM in the printer options and select the appropriate printer in the correct lab.

Citrix will connect to the J Drive, to USB on the local machine, and to the files on the local drive (Windows only). It will automatically capture USB devices when they are plugged in, and is configured to use the J Drive as its primary source. Because of the difference in infrastructure and file system types, the Citrix client will only be able to access Local Hard Disks in Windows. Linux and Mac will not connect. In Windows, a pop-up will appear querying whether to allow a program access to the local personal files. Check that it is the Citrix receiver making the request, then allow it. The local drive will appear in the places menu as Local Disk (C: on localhostname).