|
|
|
|
|
by raffraffraff
1361 days ago
|
|
Back in the corporate Windows desktop space of the early 2000s, the Citrix product was almost like magic. The problem it aimed to solve was reduction in cost and effort to deliver applications to users. Instead of managing a fleet of 'expensive' desktop computers, you install the desktop applications on a Citrix server and 'publish' them over a remote desktop protocol. The potential was huge! It was a real challenge to do this at the time. Citrix made it relatively easy to turn any old desktop PC or cheap terminal into a powerful workstation with the resources of a large server. The effect was extremely exciting at the time. A user was assigned a bunch of applications, so when they lpgged into the Citrix client they'd be able to run those applications no matter what device they were on. They could disconnect from running applications and reconnect from another device. There was the added bonus that it worked pretty well over slow network connections (some screen lag, but all other operations at the backend were lightning fast since the application ran in the date center on a beefy server). However, it was expensive. Either you had to have very deep pockets, or you need to dip into you desktop PC budget, fulfilling new hardware requests with existing refurbished PCs or new thin clients (at a lower cost). I never met an IT manager that was willing to do that. If it didn't work out, they'd be stuck with useless thin clients and the prospect of an expensive desktop refresh along with a backlog of applications to repackage and deploy via other means (Windows SMS Server, Group Policy etc). Also, very few people were doing remote work back then. Citrix tried to pivot into other spaces like virtualization (Xen) but that market was flooded with alternatives, and most companies who used Xen were happy with the free version. |
|
Insanely unbaringly slow with tons of constant lag and IT issues.
I know, anecdote...