Thin Clients w/o backend infrastructure
Background: I was given a network that has a couple of switches, 3 servers (windows 2008r2) and 150 HP T5740e thin clients. The goal was to setup 2 servers as AD/DNS and then leave 1 for an app/DHCP/multipurpose server. After I complained about how inefficient the TC setup was, I was told there wasn't money left and I had to make it work just for internet usage.
---after 2 months of usage (or lack of) they see the light---
Question: What's the quickest, cheapest, efficient way to make "this" work? This being that IE doesn't work on the machines, there's no room for temp storage or swap space, I can't install app (obviously) and in general, it's just slow. I've come up with a couple of options, but I'm stuck with finding one that has proven use cases.
- Setup the app server for Thin Apps (VMware). I ran the demo, but I can't get confirmation from VMware that this is supported (thin apps from the Win7 Embedded OS). I've also found that I have to store the application exe on the TC, and I don't have a lot of space (Chrome was ~500mb and I only have about 450MB to use). I thought we could install USB storage on the TC and just put the apps there, but then there's the LoE to get 150 TC's installed with the storage.
- Buy a virtual backend. This is going to be expensive. I thought about using Dell's Virtual Appliance they're selling now, but it's pricey and I haven't even gotten licenses yet.
- Setup a terminal server on the App server. This may work, but apparently they want to limit who has access to licensed applications. Plus how hard is it to connect the HP TC's to a terminal server and can I integrate the domain logon at the TC with an automatic connection to the term server? Do I need a broker or can I use something that's already built into AD?