A few words about Citrix... SH, this one's for you...
Quote:
Originally Posted by Shaggy Hiker
I'd like to hear a bit more on this. I have resisted using Citrix, which is the only means to do certain things with our network. I simply don't do those things, but I'd be curious to hear more about issues with Citrix, because it has always made me nervous. Seems more like a general dev question.
Shaggy - I took your post, and opened a new thread to allow this to be discussed with some seriousness...
The following re solely based on my experiences with Citrix. We have a client that uses a Citrix server in a virtual machine environment. It's got it's pros and cons.... pro - it seems to be easy to manage from their end. They install the app once, and all users into the Citrix get access to it. It's not that different than remoting into a Virtual Machine, it's just not Microsoft, and it's not VMWare. Unlike VM and VMW, I *think* Cirtix isn't software based, it's a hardware server, but I could be wrong about that.
Cons - our client is looking to dump it (actually it turns out that that's a pro for us, as will become evident). Somethings just don't work in Cirtix.... like Crystal Reports.... which, normally wouldn't be such a bad thing, except when it's your main reporting tool. Strangely, the problems with CR in Citrix are the same problem with CR in VM.... even if you copy the CR run files to a common point, where all users can see in the files, unless they are registered for EACH LOGIN on the box, CR won't run. At least now, I'm now able to recognize the symptoms when they happen.
From what I've been able to gather, Citrix is a behemoth and can be difficult to manage, and only the strong willed admins are willing to take it on.
just my two centavos.
-tg
Re: A few words about Citrix... SH, this one's for you...
Citrix is software based but must run on a server. It uses a base of terminal server functions. So when you install something it wil register the dependancy files for the dynamic user logon "virtual" path which is specific to the user logon and why it doesnt register for the actual path like C:\Windows\System32.
Not only that but its expensive but I believe it uses CALs too so not only do you need Terminal Server CALs but Citrix ones sending your expenses to an early grave.
My major client used to use it but just this past June we replaced all servers and upgraed to server 2003 from NT 4 :D So they dropped the Citrix to save money and headache. Terminal Server itself is so much better now that there really isnt much need for Citrix IMO.