I’m currently working on deploying a Windows 2008 Terminal Server and was wondering if any 'dopers have been there and done it yet…and what your thoughts are, hints, tips or gotcha’s you know of. This is actually the first 2008 Server period I’ve deployed actually, but aside from having to work around the unattended install with an IBM server (it didn’t have 2008 as an option), that part went pretty well. I also installed the License Server on the same box and was able to activate it (after 3 tries), so the server is up and running…in theory.
But tomorrow I need to set up the applications (Windows 2007 Office Pro), attach the clients (Wyse Thin Clients using Wyse RDT client), configure group remote access and group policies, etc etc. So…any thoughts or tips anyone has will be greatly appreciated. In theory I know how to do what needs to be done, at least I have done this before with 2003.
We run a bunch of 2008 and have since B1. It’s kinda weird at first because so many of the admin tools are different. But we’ve been real pleased overall. IIS7 is da bomb.
Unfortunately for the OP, TS is one area we do not use at all.
Yeah, it’s not really up to me…the customer wants 2008 TS and so here we are. I wasn’t even given the option to build this in the lab and then deploy it on site (which is how I’d normally want to work this). Thus far it’s been, as I’m sure you guys can imagine, a Murphy’s Law deployment. I finally managed to get the server up and am waiting on the customer to give me the applications they want deployed on it. Normally you basically just load the applications on the TS and then give rights to the clients to use them…but this thing has something called RemoteApp Programs section where it looks like you add the apps available to the clients and how they can access them.
Oh well…I’m sure I’ll flail my way through it somehow. Was hoping some 'dopers might have been there and done that already in case there are any gotcha’s. C’est la vie.
