2008 R2 Remote Destkop Services External Connector
Posted on 2013-01-04
We would like to set up a new Windows Server 2008 R2 Remote Desktop Server. We have around 250 people that need to connect.
- Single 2008 R2 Remote Desktop Server
- This server will host one application that needs to get to a database on another server and users need to connect to a file share on a third server.
- We would like to use the Remote Desktop External Connector.
- The Remote Desktop Server computer is a member of our domain, prodata.local.
- The users are CLIENTS, not employees. They are CLIENTS. People that pay us money for services we provide. We are providing the Remote Desktop Server a part of our service so they can pull their own reports and so forth from the application aforementioned.
- All clients have a domain user account in our domain, prodata.local.
- The users connecting to us in most cases do not have their own Windows domain. They are small peer-to-peer networks of 3 - 8 computers, most still running Windows XP.
Can we use the External Connector in our scenario? I have had several conversations and have yet to receive a straight answer. Here is what I've been told so far:
* Sure! Just install that Connector and that puppy will open right on up and allow unlimited users!
* This will allow unlimited external users but internal users, employees, will be blocked. The way the server tells the difference between external users and employees is by <insert very hard to understand and barely believable process here >
* You'll have unlimited external users and employees won't be able to connect at all. Furthermore, external users can't access file shares and stuff. Just because they have domain accounts means nothing. The Session host provides its own permissions. You'll have to mirror that file share somewhere for external users.
See what I mean? Can someone shed some light on this? I would very much appreciate it if the people that answer would be those who have actually done this before and have practical knowledge.