- #ONE PC MULTIPLE USERS SAME TIME SOFTWARE INSTALL#
- #ONE PC MULTIPLE USERS SAME TIME SOFTWARE CODE#
- #ONE PC MULTIPLE USERS SAME TIME SOFTWARE FREE#
![one pc multiple users same time software one pc multiple users same time software](https://assets.justinmind.com/wp-content/uploads/2021/11/design-prototyping-tool-web-mobile-apps.png)
#ONE PC MULTIPLE USERS SAME TIME SOFTWARE INSTALL#
Download all install files for legacy and current clients.Without further ado, I set about my testing to see if this could be done.
![one pc multiple users same time software one pc multiple users same time software](https://img.yumpu.com/50826370/1/500x640/sipass-entro-lite-sw-idtec.jpg)
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.
#ONE PC MULTIPLE USERS SAME TIME SOFTWARE FREE#
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.
![one pc multiple users same time software one pc multiple users same time software](https://m.media-amazon.com/images/I/41qRZuox-9L._AC_SY1000_.jpg)
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).
#ONE PC MULTIPLE USERS SAME TIME SOFTWARE 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