#Install citrix workspace install#
#Install citrix workspace driver#
#Install citrix workspace software#
#Install citrix workspace code#
#Install citrix workspace download#

#Install citrix workspace driver#

Here’s a video of the packaging process for the legacy client (which in this case is the 4.9 LTSR Receiver)Ī note about the warning received during packaging – ctxusbm.sys is a Citrix USB monitor driver (not mouse, as I speculated in the video).

#Install citrix workspace software#

In my production environments I use the Scheduler (because it is awesome), but for this test I am simply going to add the package to a GPO Software Installation Policy (no laughing at the back, and I wouldn’t recommend this in an enterprise environment).

#Install citrix workspace install#

You also don’t need to invest in complicated infra to deliver App-V apps – you can simply install the MSI into your image (as long as you’re using App-V 5.x), or deploy it through a GPO, or use the excellent App-V Scheduler (which has a free edition!) which I am going to be blogging more about in the very near future. Now obviously you (hopefully) don’t need me to tell you that you can simply enable App-V by turning on the GPO in Computer Config | Admin Templates | System | App-V. Step 1 – create the App-V package of your older client version

Ensure you have FSLogix Apps installed within your image, and the FSLogix Apps Rule Editor installed somewhere you can access it.

Create an AD security group that contains the users you wish to use the legacy client.

Ensure that App-V client is enabled on the target devices and images.

Ensure you have a sequencer machine with the App-V Sequencer installed.

#Install citrix workspace download#

Download all install files for legacy and current clients.

Without further ado, I set about my testing to see if this could be done. However, I then had an intriguing thought – what if I loaded a packaged version and an installed version, but leveraged FSLogix to mask them from each other? I know I said earlier to use FSLogix we’d need to have both versions “installed” – but with App-V in the mix, that line blurs a bit. However, when I tested this, the packaged version crashed with this errorĬlearly, there is still some interplay between a packaged version and an installed version that renders the first unusable. I’d also seen multiple Citrix clients running using Cloudhouse Compatibility Containers, but that raised the issue of budget – Cloudhouse isn’t free and there was no money available from this customer to pay for some level of remediation.Īfter a bit of thinking, I wondered whether this would be possible to do via App-V – package the 4.9 LTSR version, and install the 2006.1 version? This seemed feasible – the App-V version would be in its own filesystem and Registry area. If we chose to use something like FSLogix App Masking, for instance, we’d actually need both client versions installed alongside each other to make it work, and this wasn’t possible. After all, Citrix Receiver and Workspace App are essentially the same application, and therefore would share Registry keys and filesystem entries. So I was asked the question – can we run different Citrix client versions from the same image for different sets of users?Īt first thought, this seemed pretty impossible. Also, being a Citrix Cloud environment, silos potentially also meant that siloed servers could end up running with very low user density, which would increase the overall cost of the solution for business units which needed to use the older client version. Of course we could just spin up a silo of servers that had the old Receiver version installed and tie those users to those instances, but this was an environment that was running from a single image and had no wishes to start expanding that number. Whilst we can all say “well they need to remediate their old infrastructure”, many of you well know that getting large-scale remediations underway in enterprise environments can be very challenging. They had a small number of users (probably ~5% or so) that still needed to launch some applications from an older Citrix farm which required a downstream version of the client (Receiver 4.9 LTSR, to be precise).

#Install citrix workspace code#

This is a binary planting vulnerability and, whilst not allowing remote code execution per se, is still something that people would look to be patching sooner rather than later.Ī customer of mine (who are very security-conscious) were looking to get this addressed as soon as possible, but there was a snag. This week Citrix publicized some vulnerabilities in their Workspace App and Receiver clients that potentially would allow an attacker to elevate their privileges. Is it possible to use two Citrix client versions in one image? Actually – yes! The problem