Citrix
#1
Citrix
So I have this interview tomorrow. One of the things mentioned in the job add was Citrix. What do I need to know about Citrix so I can even pretend to have a clue. Citrix.com has a ton of products/services....any common app that's likely this company would use? They're a nonprofit dealing with affordible housing. Any websites other than citrix.com that might give me a crash course?
UC
UC
#2
I've only had experience with MetaFrame Clients. I used it on top of my terminal servers to augment the features and security. it had better encryption, printer support, and misc features (like copy and paste files not just the clipboard)
I know they have a physical install via a setup and a web based client which I believe is now the standard.
No good sites though...sorry.
I know they have a physical install via a setup and a web based client which I believe is now the standard.
No good sites though...sorry.
#3
Originally Posted by vader716
I've only had experience with MetaFrame Clients. I used it on top of my terminal servers to augment the features and security. it had better encryption, printer support, and misc features (like copy and paste files not just the clipboard)
#4
Here are a few answers from experts-exchange
Many differences:
Citrix is MUCH more secure, you can run all the traffic in 128 bit SSL. You would need to setup a few boxes though, Citrix secure gateway, a ticket authority, a citrix server, and if you want to publish your apps on the web you have an NFUSE server.
Citrix is much more stable as far as how many users you can get running per server.
You have the ability to publish a single application to a user so if I am Joe I login and get Internet explorer, but John might login and have Internet explorer and WORD. You can do this using the Citrix NFuse page which is just a web page and the users will see applications or you can do this just using the server and ciitrix clients. You also have to keep in mind licensing which is big. Terminal server cals are around 80 bucks a piece for each client. Citrix requires that you use a terminal server cal and a citrix cal and the citrix cals are around 200 (I think) been a while since I bought some.
with citrix if you get alot of users you can take a couple servers and load balance the applications so each user will get moved to the server with the most resources available, fewest users, etc all depending on what you setup.
You can also run dumb terminals in the office and people can run an entire desktop on one using just the citrix server.
CItrix runs on the ICA traffic protocol and Terminal Services runs on the RDP Protocol. ICA Is much quicker if you compare the users experience.
Plenty more but most companies that rollout remote thin clients use citrix and as all MS products TS has alot more vulnerabilities.
Citrix is MUCH more secure, you can run all the traffic in 128 bit SSL. You would need to setup a few boxes though, Citrix secure gateway, a ticket authority, a citrix server, and if you want to publish your apps on the web you have an NFUSE server.
Citrix is much more stable as far as how many users you can get running per server.
You have the ability to publish a single application to a user so if I am Joe I login and get Internet explorer, but John might login and have Internet explorer and WORD. You can do this using the Citrix NFuse page which is just a web page and the users will see applications or you can do this just using the server and ciitrix clients. You also have to keep in mind licensing which is big. Terminal server cals are around 80 bucks a piece for each client. Citrix requires that you use a terminal server cal and a citrix cal and the citrix cals are around 200 (I think) been a while since I bought some.
with citrix if you get alot of users you can take a couple servers and load balance the applications so each user will get moved to the server with the most resources available, fewest users, etc all depending on what you setup.
You can also run dumb terminals in the office and people can run an entire desktop on one using just the citrix server.
CItrix runs on the ICA traffic protocol and Terminal Services runs on the RDP Protocol. ICA Is much quicker if you compare the users experience.
Plenty more but most companies that rollout remote thin clients use citrix and as all MS products TS has alot more vulnerabilities.
- citrix clients for different platforms linux dos(very fast to boot from) Mac , windows
- Loadbalancing : when one server is down the other servers take the other client, this is not possible in Ts unless you define another server in the clientPC
- Shadow mode ( as admin you can get the screen of the user)
- you can run apps in seamless window : the user have the idea the the software is running locally.
- a very fast prtocol can be user over a very slow connection
- security is much better
the other side of citrix is
- expensive
- we had troubles with a client that took to much CAL's
- Loadbalancing : when one server is down the other servers take the other client, this is not possible in Ts unless you define another server in the clientPC
- Shadow mode ( as admin you can get the screen of the user)
- you can run apps in seamless window : the user have the idea the the software is running locally.
- a very fast prtocol can be user over a very slow connection
- security is much better
the other side of citrix is
- expensive
- we had troubles with a client that took to much CAL's
Citrix is loading each program once to determine how much memory is used it then cascade these Sessions to get maximal benefit on the memory. The next Session will just be a window but not the whole program.
TS for each Program that is opened a new Session is made and that's why you will see that when using the Citrix program much lesser memory is required and they run more stable using the Citrix.
TS for each Program that is opened a new Session is made and that's why you will see that when using the Citrix program much lesser memory is required and they run more stable using the Citrix.
#6
The basic concept is the same as terminal services... thin client on one end, all processing done on the head end. Critix is much more robust... and complex. Tell 'em you've worked with thin client technologies and you'll have no problem adapting your skills to the Critix environment. Deliver that line with confidence and that's all you need.
#7
Trending Topics
#8
#9
#10
#11