Technically, yes, that's about all there is to it, provided your FW is allowing the connections (port 3389). The gateway in Win2K8 will let you SSL secure a single open port on your FW and broker backend connections if that's of interest to you.
Licensing, as you noted, will be an issue. As will resources for large numbers of concurrent connections. -sc From: Joe Heaton [mailto:[email protected]] Sent: Wednesday, July 01, 2009 1:09 PM To: NT System Admin Issues Subject: Terminal Services question I need a nuts and bolts answer, which I could probably get through research, but I'm getting kind of burnt out at the moment with other things going on. If I am at home, and I need to access my network through Terminal Server, is it as simple as opening up mstsc.exe and putting in the IP address of the Terminal Server, then putting in my credentials? Does this then open an RDP session to the desktop of the Terminal Server? I don't think I want users to be working on the server, so how do I then give them the environment I want them to work in? I'm still working on my "pandemic", everyone has to work from home solution, but I'm also trying to figure out the best method of giving remote access in general. I do have Citrix PS4 in place, but the number of licenses are limited, and I know that TS licenses are not for concurrent use, so I really need to get the backend requirements nailed down. Also, I am looking at more of a desktop experience for the users, as if they were sitting at their desks, as opposed to publishing applications only. Joe Heaton AISA Employment Training Panel 1100 J Street, 4th Floor Sacramento, CA 95814 (916) 327-5276 [email protected] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
