How to Connect 50 HP t505 thin clients with HP DL 380p

Toggle sidebar Toggle sidebar
E

enjoylife1788

Reputable
Feb 20, 2014
4
0
4,510
Hey guys,

An uncle of mine has a business and he wants to connect 50 thin clients, HP t505 with HP 380p Hexa core processor. He has already ordered the hardware. I insisted I want to do the installation since it would be a great learning curve for me.

So the design is as follows:

Hardware

Server : HP 380p hexa core
Thin Clients : HP t505
Switches: Netgear 7224-200 as the main aggregation switch total 1
Netgear 724t as the edge switchs Total 4
NAS: Netgear RN314 for storage

Connectivity:

Fiber Connectivity between the aggregation switch and edge switches.
Copper connectivity between the edge and the thin clients.
Since I have four SFPs on the aggregation switch, I can afford to go for a star topology. Please advise for anything better.

Now, I have never configured a server with thin clients before. So please guide me step by step.

I know the basics of connectivity and all that. However, I am quite confused on the licensing aspect. I know there are CAL licenses and tCAL licenses. Please guide me through that.

Please let me know what else do i need to provide for better understanding of the situation.


Also, the applications for all the thin clients is to use Microsoft word, emails and basic computing. So please advise on the licensing and installation options for those as well.

Thanks in anticipation. :)
 
Solution
choucove
This is a tough one for me to dive in on because simply I just don't know what your intended usage is. You've got a single server and a lot of thin clients. Are you just wanting to set up remote desktop with a terminal server in Windows? Are you doing something more complex like VMWare View, or VDI? What are you meaning by "connect" the thin clients to the server? What is the OS that is loaded on these thin clients?

A thin client is just a basic computer but you still have to have some sort of software infrastructure on the server for the thin client to access. I'm not an expert at this as I've only done RDSH with thin clients in my personal lab testing and playing around. However, there's a lot more information that we need...
Sort by date Sort by votes
E

enjoylife1788

Reputable
Feb 20, 2014
4
0
4,510


Ya what i need is a network specialist. But, I have seen people like that on this forum. So i guess its possible here.

However, thank you for your reply. :)
 
Upvote 0 Downvote
choucove

choucove

Distinguished
May 13, 2011
756
0
19,360
This is a tough one for me to dive in on because simply I just don't know what your intended usage is. You've got a single server and a lot of thin clients. Are you just wanting to set up remote desktop with a terminal server in Windows? Are you doing something more complex like VMWare View, or VDI? What are you meaning by "connect" the thin clients to the server? What is the OS that is loaded on these thin clients?

A thin client is just a basic computer but you still have to have some sort of software infrastructure on the server for the thin client to access. I'm not an expert at this as I've only done RDSH with thin clients in my personal lab testing and playing around. However, there's a lot more information that we need before figuring out what I can do to help you and make some recommendations.

For starters, what is the exact hardware configuration of your server? I need more information about your processor, available memory, network capacity and configuration, and storage. Next, what are you doing specifically with this server? Are you planning to run everything in this network on the server, such as domain services, storage, application server, etc. or do you have additional servers in your environment as well? You said you have 50 thin clients, does this mean you have 50 concurrent connections as well all doing the same thing, or only some connected at intermittent intervals? What OS are you using on your thin client and for your server?

Once we get some more information I may be able to help out some more with suggestions, but this sort of task is far greater than anything we can discuss step-by-step here to set up. It requires a multitude of components, services, and settings to be configured and working properly, so it's not something near as simple as start at step1, click these buttons, step2, type this text, and after a few more steps you are done. This may take weeks to get working properly.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom