This vid explains how to uninstall Citrix Receiver manually. Plz use this app uninstaller PRO@ if you are having. Find answers to Citrix Receiver (iPhone) with Presentation Server 4.5 from the expert community at Experts Exchange. The Citrix Workspace App does not have the same version information as Citrix Receiver, as it is now a so called evergreen application. This means that the only version information availbale is going to be in the same format as Microsoft uses, ie Citrix Workspace App 1808, which indicates that this particular Citrix Workspace App version was. Citrix Receiver: Accessing PSD Apps and Network Drives Citrix Receiver is a tool that allows users with Puyallup School District network accounts to access PSD applications and documents stored on their (U:) Drive or the shared (Y:) Drive when they are away from their school or building.

1. Citrix Receiver 4.5 Ltsr
2. Citrix Receiver 4.5.0.10018 Download

Looking to download an old but stable Citrix ICA client, Citrix Online Plugin or download Citrix Receiver? You Have come to the right place.

Below you can download old Citrix clients that I was able to gather through the years as Citrix Consultant. I also included some online and offline information where possible. If there is sufficient time, I will also will attempt to indicate possible Stable Versions, based on community feedback, and bugs.

Citrix certainly doesn’t make it easy to let you find a place to download the version you are looking for. The site changes all the time, and articles are removed regularly. And how many Citrix clients are there? And which one is the latest?

For sure you know a 9-10 of them, right? But did you know, Citrix has released more than 100 versions already for the Windows platform only? This includes limited releases.

LATEST Citrix Receiver 4 versions

These are the LATEST Citrix Receiver 4 versions: (more details see in table at the bottom of the page)

Download Citrix Receiver 4.12 (14.12.0.18020)
Download Citrix Receiver 4.11 (14.11.0.17061)
Download Citrix Receiver 4.10 (14.10.1.22)
Download Citrix Receiver 4.9 (14.9.3000.11)
Download Citrix Receiver 4.9 (14.9.2000.21)
Download Citrix Receiver 4.9 (14.9.1000.17)
Download Citrix Receiver 4.9 (14.9.02539)
Download Citrix Receiver 4.8 (14.8.0.1010)
Download Citrix Receiver 4.7 (14.7.0.13011)
Download Citrix Receiver 4.6 (14.6.0.12010)
Download Citrix Receiver 4.5 (14.5.0.10018)
Download Citrix Receiver 4.4 (14.4.5000.8)
Download Citrix Receiver 4.4 (14.4.4000.10)
Download Citrix Receiver 4.4 (14.4.1000.16)
Download Citrix Receiver 4.4 (14.4.1000)
Download Citrix Receiver 4.4 (14.4.0.8014)
Download Citrix Receiver 4.3 (14.3.100)
Download Citrix Receiver 4.3 (14.3.1.1)
Download Citrix Receiver 4.3 (14.3.0.5014)
Download Citrix Receiver 4.2 (14.2.100.14)
Download Citrix Receiver 4.2 (14.2.0.10)
Download Citrix Receiver 4.1 (14.1.200.13)
Download Citrix Receiver 4.1 (14.1.2.3)
Download Citrix Receiver 4.1 (14.1.100.12)
Download Citrix Receiver 4.1 (14.1.0.0)
Download Citrix Receiver 4.0 (14.0.1.4)
Download Citrix Receiver 4.0 (14.0.0.91)

All older Citrix Receiver versions see in the big table BELOW (wait for table to load)

Keeping the Citrix client versions up-to-date is important to create a stable Citrix Farm. And choosing the right one even more.
More often than not, the Citrix Client upgrade is not the favorite project of a Citrix administrator.

I won’t go into the details of the most common issues that arise, but we can safely state that Citrix doesn’t have the best reputation when it comes to releasing new Citrix Clients.

Citrix Receiver 4.5 Ltsr

Citrix can and SHOULD improve a lot on some weaker points: uniformity, proper communication on the implemented changes, clear version information, improved installation automatisation and decreased complexity. Citrix developers should also clearly separate bugfixes with new features. Almost every version includes new features, which cause new problems, while the admins just want to have the same client with all bugs fixed.
Personally, I demand Free Citrix Support for anyone having problems with the installation of the client. The attitude “Download it, see if it works, good luck!” is a huge gap in Citrix’ service towards all customers.

An experienced Citrix consultant told me recently that these client deployments have been causing so many headaches in his latest projects, he had to decide to exclude the deployment of the Citrix client from the project scope! The XenApp farm is built, or migrated, but any possible upgrade for the Citrix Client on the corporate desktops is not done by the consultants: “Let the customer desktop support team deal with this mess!”

In Citrix’ defense, one must know that their clients run on many, many different platforms. And those clients need to cover numerous situations (badly written applications, OS upgrades, hotfixes, updates or service packs, single, dual or very large screens, and a client release should preferably work for all customers worldwide. Seems like a huge challenge!
Then again, the RDP client only has had a handful releases, seems to be rock-stable and works nicely in all these situations? Maybe time to borrow those Microsoft developers for a while?

Another issue I try to deal with here is the lack of information.

Citrix officially only supports the latest version, ánd the one but last release. Which means that by the time the Citrix admins want or need to upgrade their client, older stable version are simply not downloadable anymore from the site. Want to deploy Citrix Receiver 3.2? Bad luck! Citrix has removed the download and related webpages regarding deployment have been taken offline.

Any feedback, additions are welcome. If time allows, I will try to add new clients, also the ones for other OS, and critical information.

Citrix Receiver 4.5.0.10018 Download

SSO Overview

There are to ways you can use SSO in a Citrix 7.5+ environment using built-in Citrix technologies:

1. SSO via Citrix Receiver for Web
2. SSO via the Citrix Receiver client

Depending on which method you choose the prerequisites differ, however not by much. Below are the prerequisites that are required for either method, meaning it doesn’t matter which method you choose the same prerequisites exist:

1. Citrx Receiver must be installed on the client device with the SSON component installed
2. Receiver for Web website must be in the Local Intranet Zone
3. If using the Trusted Sites zone instead, Automatic logon with current username and password must be set in Trusted Sites zone (I will talk no further about using the Trusted Sites zone)
4. Domain pass-through must be enabled on Receiver for Web via StoreFront console
5. Requests sent to the XML service port on your DDCs must be trusted

Now below are the remaining unique prerequisites/differences for each method.

Receiver for Web

1. Always use Receiver for HTML5 must not be selected in StoreFront
2. Internet Explorer must be used when accessing Receiver for Web
3. Group Policies do not need created for Receiver for Web SSO
4. The User Name and Password Receiver for Web authentication method should be disabled to avoid extra prompts which will later be explained

Receiver client

1. Group Policies do need created for Receiver client SSO

Installing and configuring SSO (Receiver for Web):

1. Citrix Receiver client must be installed on the end device. The SSO component is not required so a simple GUI or command line interface command can be used to install the client.
2. Using StoreFront MMC, enable Domain pass-through on Receiver for Web
3. Using StoreFront MMC, disable User Name and Password authentication against Receiver for Web
4. Launch Internet Explorer on logon by placing a shortcut in the Startup folder C:ProgramDataMicrosoftWindowsStart MenuProgramsStartup. This should be done on the base/gold image
5. Set Internet Explorers homepage to the Receiver for Web website address
6. Create a GPO linked to all machnes participating in Citrix Receiver for Web SSO or use an existing policy
7. Using the above created policy, edit the setting Computer Configuration -> Policies -> Administrative Templates -> Windows Components -> Internet Explorer -> Internet Control Panel to include the Receiver for Web website address in the Local Intranet zone

Decision: To get rid of the first-time logon prompt which will be shown later in this post, you need to disable User Name and Password authentication. Doing so partly reduces functionality:

1. Non domain machines cannot authenticate to this Receiver for Web website
2. Usrs can not log on using a set of credentials different than those they used to log on to their domain joined client device

Keeping the above restrictions in mind, a decision must be made to bring true SSO experience at the expense of reduced authentication ability, or accept that a prompt will be given to users on first log on to Receiver for Web in favour of keeping maximum authentication abilities. It is also possible to create a seperate Receiver for Web website for SSO users only, or create sites for non-SSO participants. This means you can configure seperate devices/users to point to specific Receiver for Web websites based on authentication needs.

Installing and configuring SSO (Receiver client)

1. Citrix Receiver client must be installed on the end-device. The SSO component is required so a simple GUI or command line interface command can be used to install the client. A command line install if preferred because you can automate Citrix Store configuration. The following command at minimum is required to install Receiver client: CitrixReceiver.exe /includeSSON (tested on Receiver 4.3)
2. Using StoreFront MMC, enable Domain pass-through on Receiver for Web
3. Download and copy receiver.admx and receiver.adml template files to the PolicyDefinitions folder on a Domain Controller
4. Create a GPO linked to all machines participating in Citrix Receiver client SSO or use an existing one
5. Using the above created policy, edit the setting Computer Configuration -> Policies -> Administrative Templates -> Citrix -> Components -> Citrix Receiver -> Local User Name and Password enabling Enable pass-through authentication
6. Using the above created policy, edit the setting Computer Configuration -> Policies -> Administrative Templates -> Windows Components -> Internet Explorer -> Internet Control Panel to include the Receiver for Web website address in the Local Intranet zone

The Receiver for Web logon prompt

Now that we have discussed the prompt and the advantages/disadvantages with enabling/disabling this feature, here below is a picture of what the prompt actually is and looks like.

When you have enabled Domain pass-through and User name and Password authentication on Receiver for Web, the first time a user logs on they get this prompt to either log on using the account used to sign on to the computer or to switch to the username and password logon screen. The user name and password logon screen gives the user the ability to authenticate with any set of credentials they have. Since I mention “first time” above, first time means the first time a user logs on to Receiver for Web on a device that they have never used before. The next time they use the same machine the same prompt does not appear. If you log off, you may also get the below message.

If the device is a thin-client with a write-based restrictive filter, the profiles may not be stored and as such the user is using that machine for the first time every time as far as the device is concerned after said device is restarted. This reduces the SSO experience, as the prompt requires manual input. Users wanting true SSO experience must disable User name and Password authentication. User name and Password authentication conflicts with SSO and is not required. A seperate Receiver for Web site must be created for users who do require the User name and Password authentication method. User name and Password is enabled by default when you install Citrix StoreFront.

The User Name and Password authentication method

Configuring SSO for Receiver client

Now that we have covered the theory, I will walk through configuring SSO for Receiver client. I won’t go through SSO with Receiver for Web but it is just as similar to configure.

Install Citrix Receiver on the client device with SSON component included. I am using a command to install. The command automatically configures the store.

You could also enable SSO by checking the box on newer versions (4.3+) if you prefer however you will have to manually configure the store or use the Receiver ADMX templates with Group Policy.

Insert the Receiver for Web site in the Local Intranet Zone. If using the Trusted Sites zone instead, Automatic logon with current username and password must be set in the Trusted Sites zone. In most cases you will use the Local Intranet zone. This is best done via GPO.

Values:

1. Intranet Zone = 1
2. Trusted Sites = 2

If using the Trusted Sites zone, enable Automatic logon with current username and password.

Enable Domain pass-through on Receiver for Web via StoreFront console and remove other authentication method(s). Pass-through from NetScaler Gateway can be enabled, however User name and password should not.

On your DDCs requests sent to the XML service port on your DDCs must be trusted, so run the following command:

Configure Group Policy to enable pass-through authentication on Receiver. You will need to have imported the Receiver.admx and Receiver.adml files to the Group Policy Central Store.

Outcome

Now if you open the Citrix Receiver client on your device, it should not ask to configure the store or ask for credentials. Instead, you will be passed through to StoreFront and presented with your subscribed applications and desktops.

Be aware after installing Receiver you must log off/on to your client device for the SSONSVR.EXE process to start and capture your credentials.

Additional feature – Desktop Lock

You can also turn your PC/Thin Clients in to kiosk type machines using what is called Citrix Desktop Lock. When a user logs on to their device the Citrix desktop automatically launches in full-screen mode and if the user disconnects or logs off the Citrix desktop the user is automatically logged off the local device. This is great in a VDI environment if you want to bring a true no-touch experience to your users. You can download Desktop Lock from the Citrix website.

Once downloaded launch the Citrix Desktop Lock software on an SSON configured client device.

Click Close once the software has installed.

Restart the client device.

Now log on as a standard user who has one Citrix desktop assigned to them.

Desktop Lock automatically launches the desktop in full screen.

The Desktop Viewer toolbar has some missing buttons to prevent the user from minimizing the desktop for example.

When the user disonnects or logs off, the local client device is also logged off. This helps secure the device and not leave any unattended workstations logged on.

If you need to control the local device yourself, log on as a user who is a Local Administrator of that machine and you will be presented with the below prompt.

After clicking OK you can access the local desktop to perform management tasks.

Troubleshooting SSO

• The SSONSVR.EXE process must be running on your client device
• Ensure you have met all the prerequisites stated above for your SSO method (Receiver client/Receiver for Web)
• Using an SSO configured device go to https://yourstorefrontserver.domain.com/citrix/storename/domainpassthroughauth/test.aspx. The web address I would go to is https://storefront.citrixpro.co.uk/citrix/cpsweb/domainpassthroughauth/test.aspx and if SSO is correctly configured you should see results similar to the below. (Included in StoreFront 2.5)
• Restart the client device (requirement after Receiver install with SSON)

Receiver 4.5 (released September 2016):

New with Citrix Receiver for Windows 4.5 is the Configuration Checker tool which performs various checks against the prerequisites needed for SSO to work. Open Advanced Preferences by right-clicking the Receiver icon in the system tray. Click Configuration Checker.

Tick SSONChecker and click Run.

As you can see a number of checks have been performed with one failure.

Looking closer at the failure alert we can see the Single Sign-on process is not running. After installing the SSON components you only need to log off/on for the process to run. In this case, I deliberately left out the SSON component so it is not installed at all. Click on Save Report to save the results to .TXT.

Heres a look at the results .TXT file.

I’ve now ran the SSON Checker on a machine that is properly configured for SSO. As expected, all checks have passed.

Receiver SSON logging:

You can enable SSON logging which may be help in identifying an issue.

Add a the following values to HKLMSoftwareCitrixInstallSSON (32bit) or HKLMSoftwareWOW6432NodeCitrixInstallSSON (64bit).

REG_SZ DebugEnabled = true

REG_SZ LogPath = Path location

When you log off and on again log files will be created relating to SSON.

The trace-pnsson.log file shows information such as the credentials captured and packaged by SSON.