8,200 pts.
 ncomputing versus thin client
What are the pros and cons in ncomputing versus thin client - in terms of infra and software licenses.

Please give practical examples and scenarios based on experience. No links or theretical answers.


Software/Hardware used:
ncomputing, thin client
ASKED: Jan 30, 2012  2:21 PM GMT
UPDATED: March 9, 2012  10:25:49 AM GMT
8,200 pts.

Answer Wiki:
Last Wiki Answer Submitted:  Jan 30, 2012  2:21 PM (GMT)  by  Jaideepkhanduja   8,200 pts.
To see other answers submitted to the Answer Wiki View Answer History.
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _




 

Manageability vs Reliability.

Think of it this way:

Choice 2
If you have a server that all users connect to, then thin client will work great with.

Choice 1
If your users don’t need to ’sign on’ to a server and do what they need, then individual computing with network - so called ‘ncomputing’ will work just fine.

In term of infrastructure, my experience, choice 1 is preferred because my application demands complexity. I can’t cookie cut everything. Ends up, I have multiple department to settle with. Choice two would work in an environment that everyone is doing the same thing. So, you can break it down and apply to a single area that users repeat the functions over and over.

In term of software licenses, I don’t see any big saving but required the necessary knowledge to manage/control the access and provide availability. If the server goes down, all goes down. Software license wise, it measure by concurrent users online. Otherwise, it is cheaper as needed instead of buying all ten having paid all ten with individual licensing.

-Michael
arch4ngel@gmail.com

 250 pts.