Computing.Net > Forums > Windows Server 2003 > Network boot client PCs

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to get for your free account now!

Network boot client PCs

Reply to Message Icon

Name: mikeliketrike
Date: January 9, 2009 at 11:22:56 Pacific
OS: Windows Server 2003
CPU/Ram: Intel 3GB
Manufacturer/Model: Dell / SERVER
Subcategory: Configurations
Comment:

I just got a job at a place with 30 or so PCs booting into 2X ThinClient and then going into a 2003 Server machine through terminal services. I don't believe this is the ideal situation.

Note that the computers in question are fairly old and don't have a lot of processing power at all.

I'd like to do some type of network boot for each client with a minimal footprint on each computer, but not go through 2X ThinClient. I'd like to use a fully Windows based solution, rather than using a Linux boot option. I realize that this isn't the ideal situation for everyone, but it's the best direction to go for the company I'm now working for.

What options do I have to accomplish what's needed? All computers have floppy drives and CD drives.


Report Offensive Message For Removal

Sponsored Link
Ads by Google

Response Number 1
Name: wanderer
Date: January 9, 2009 at 12:35:38 Pacific
Reply:

This may seem harsh but you don't understand thin computing and your assessment that changing this is the best move for the company is incorrect.

This is a perfect setup and example of how to use older hardware at reduced cost, increased security and control, to provide a company wide computing platform.

You also fail to understand the bandwidth considerations. A fat client, which is what you propose, puts far more network traffic on the network then a thin client implementation due to the fact the thin clients are only exchanging keyboard/mouse/video traffic instead of full blown fat client network traffic.

Don't believe me?

Then conduct a simple test. Google TinyXP [minimized xp] and install it. Compare its server access performance on one of these pcs vs the thin client access.

The correct path would be to add a server to provide failover and load balancing of terminal sessions. 30 plus clients, depending on software being used, on one server is a bit much for one server depending on hardware/cpus/memory of the server.

If going to fat clients you then have to consider group policies, antivirus/spyware software installs/licenses, etc. will all increase the cost to the company.

You may want to review the 2x site
http://www.2x.com/pxes/

"Boot clients via PXE, Harddisk, CDROM or USB "

sorry if I seem harsh


Report Offensive Follow Up For Removal

Response Number 2
Name: mikeliketrike
Date: January 9, 2009 at 12:47:33 Pacific
Reply:

So you're saying that using a 2X ThinClient setup is better than using an equivalent to a Bart Network Boot Disk?


Report Offensive Follow Up For Removal

Response Number 3
Name: bilbus
Date: January 9, 2009 at 13:48:40 Pacific
Reply:

Yes

your setup is ideal. All you need to do is manage a few servers .. not 30 desktops.

If hardware breaks, you open a box, configure the TS or remote boot ip (unless dhcp does this 2) and your done.

This is great for anyone who does not need a desktop. I like VDI for those.

And i agree, get a second server, you need some kind of fault tolerance ... if your server crashes your office is offline.

Hands off! Go thin computing!


Report Offensive Follow Up For Removal
Reply to Message Icon

Related Posts

See More







Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Network boot client PCs

Wireless network boot ? www.computing.net/answers/windows-2003/wireless-network-boot-/2887.html

How To Control Client PC from Serve www.computing.net/answers/windows-2003/how-to-control-client-pc-from-serve/4763.html

Limit client pc's internet access www.computing.net/answers/windows-2003/limit-client-pcs-internet-access/4037.html