kesomir

Would have liked to have seen an example of one of the batch files though. @broken_url what school?

Ubuntu is a great distro to get your toes wet. SUSE is a bit more polished for enterprise use, but Ubuntu is 'better' for standalone / new users trying it out.

I'd be interested to hear the specifics. Can you attach these "batch files and things"? If you can't access cmd, it's unlikely that ranger would permit executing batch scripts - that is after all, the whole point of ranger.

I'm not sure I understand your problem. Are you talking about running ranger admin on a client machine under your normal user account? What is the primary usergroup for that account? are the required security settings enabled for that user account in ranger? What do you mean by "full-control"? If you can access the ranger admin panel from a client machine, then your account's primary usergroup must have been granted access via the ranger admin panel - afaik there isn't a limited access mode for the ranger admin panel. Are you the administrator? The sentinel forums can be useful - if a solution isn't apparent from either the knowledgebase or admin manual.

Promote the plus points: Lower TCO (smaller energy req, easier maintenance, higher reliability, 10 yr lifespan of clients) Shared processing power (upgrade server and everyone benefits) Just remember that you they aren't for everything: can't really use them for multimedia tasks and you may as well turn off sound as it's terrible - latency causes sound to reach you seconds after video if at all. Shame, since the linux implimentation is much better in that regard, feels much more like a full box with LTSP. Normal application use including flash is fine (full lab of flash games does slow things down a little ) Open Office, educational apps all good. My server has 2 quad core xeons and 8GB of ram - don't scrimp on the ram. Links: Windows 2003 Terminal Services (Part 1) Microsoft Windows Server 2003 Terminal Services EDIT: forgot to mention if it's a new deployment, you might consider server 2008. It has a few improvements to ts such as application deployment as opposed to desktop deployment - just the application window is transferred to the thin client. However atm for that I believe you need a windows based client - at least until the open source guys reverse engineer the new bits. Worth keeping in mind if you have linux clients.

If you join the terminal server as a member, it will authenticate ts users against the domain controller - however if you don't have control over group policy, then you may run into snags if, for example, users are denied terminal services access from AD. Setting up terminal services itself is fairly simple - just add the server role to the box and reboot. Next hiccup is allowing users to connect to terminal services, which I do from the DC. As long as main IT sets everything up in AD for your terminal server then it should all go fairly smoothly. I run 33 debian HP thin clients off of a server 2003 x64 box and have no real problems with them + they're all managed via tftp and altiris from the terminal server. Good luck, it's a good learning experience. Sounds like all you need to do is liase with the main IT dept.