@flaxking said in Is RD Gateway useful?:
@bbigford said in Is RD Gateway useful?:
@flaxking said in Is RD Gateway useful?:
I know we've talked about RDP security before, but I'm bring it up again.
Is there a use case for RD Gateway in a single RDS server setup? (assuming we don't want to use the html5 web client) In this scenario it would be installed on the same server.
To me it seems like it would be only really be useful if it was on the edge separate from the RDS host server. RDP can be already be configured to only use TLS (though it looks like TLS 1.0 is the highest it uses).
Or am I missing something here? Is there something else that makes RD Gateway inherently more secure? I'm not too interested in the additional resource access configurations.
Are you going to use it external and configure your registrar to use something like remote.domain.com? If not then there is no purpose for it in your case. If you are, then it would give you better security if you did place it at the edge.
Yes. Basically we want to host our application for some of our clients. We have a hosting partner that has been figuring out the details for our clients, but our clients have been requesting things outside of their experience so it has come back to us to figure out some of the implementation details.
So the networks will basically be a RDS server and a database server (not actually sure where they put AD). I'm trying to figure out the smoothest setup for our clients with the lowest cost.
I would be looking into Guacamole, but no one has requested a web client. But presumably, our partner will be using Datacenter, so maybe an additional Windows Server for RD Gateway wouldn't be the cost increase for our clients that I would expect.
However, I simply don't have a grasp on what additional security it is going to provide. I assume it is going to sit at the same place on our hosting partner as the RDS server, just now the RDS host won't have a port exposed, the Gateway will. And if it was on the same server, what's the difference between the gateway port being exposed or the RDP port?
I mean, if it actually sat on edge infrastructure, I see the use. But otherwise, what's the point?
Honestly, you're all over the place.
You have some questions that need answered.
"I mean, if it actually sat on edge infrastructure, I see the use. But otherwise, what's the point?" -Security, as a proxy. That's the point. You're planning on exposing this to the outside; I would argue you absolutely need a gateway.
"However, I simply don't have a grasp on what additional security it is going to provide." -It's acting as a proxy, basically, that's the additional security.
"I would be looking into Guacamole, but no one has requested a web client." -What does that have to do with anything? Do you want to use Guacamole, or Windows Server RDS? Now is the time you should pick one.
"But presumably, our partner will be using Datacenter, so maybe an additional Windows Server for RD Gateway wouldn't be the cost increase for our clients that I would expect." -Are you concerned with cost, or functionality? Getting lost in this area as you had randomly thrown in Guacamole so I can't tell if you're going for cost or functionality as the bottom line because both have their strengths. What are you more familiar with, Linux or Windows Server?