Thinstation's probably a good start and won't cost you anything onto your existing TS.
:: Thinstation - a light, full-featured Linux thin client OS ::
So i want to try having thin clients on the network, i have a server i can use for terminal server and volume lisncing so thats ok, but what do i need at the client end to make it work? I have some old celerons with 512MBram as hardware but what OS?
...or if you would prefer to test a dedicated thin-client we can loan you one. The only setting up required is to enable DHCP and provide the IP address of the server. From unboxing to setting up to being connected to your server will take less than 30 seconds!
Below are some comments of users who have gone down this route:
Axel AX3000 m70 for Lesson Monitor
PM me, or fill out the link on www.axel.com to have one sent to you...
Another vote for Thinstation here. Happy to package up our image and let you have a copy. Should only need a few tweaks to get it on your server.
i looked at thinstation, but in the config file appears as if it has to different for each thin client. is this correct?
We have 3 different types of computer all using the same thinstation image (about 30 machines in total).
Does Thinstation require PXE network cards or can you create an image so it will boot from the HD?
You can use PXE, make a disk bootable image, a CD-ROM bootable image or many other options.
We've always been told that we don't pay for the extra software we already have licenses for (ie. if we have 300 licenses for XP and our network grows to 310 XP machines) until the end of the year, but if it is something we don't have yet (like adding TS licenses to the agreement) then we needed to buy them.yes, but we dont pay them untill the end of the year, when our volume lisence renewal come round. (i've been told)
This is for both licensing and technical requirements - namely, terminal services requires a licensing server to run properly. And the licensing server requires some licenses to allow clients to connect - if you use a volume licensing scheme, this would involve entering your agreement number in the licensing console and it contacts MS to get your licenses.
@localzuk: I believe that mjs_mjs is describing a Schools Agreement where by adding an additional product part way through the year is fine (and doesn't require payment immediately) but you will be charged for it in the next year of your agreement.
For instance, you might license 5 Windows servers at the start of your agreement in January (assuming your agreement starts in January) but part way through the year (say June) decide you want to implement a sixth one. You would be allowed to implement your new server in June and would then add it to your agreement next January when it is renewed.
This is how it was recently described to me anyway.
There are currently 1 users browsing this thread. (0 members and 1 guests)