Securing RDP sessions
-
@technobabble said:
40 of the users are contracted workers or doctors offices, would that sway you to add Pertino?
Depends on your architectural goals long term. But Pertino is nice in a situation like that because it is so easy to disable machines once they are no longer needed. Outside workers can manage their own connections but you get a central web console so that you can check on who has access, who is online, etc.
-
What are the users RDPing into, exactly?
-
Server desktops to use a Medical Billing program and scheduler.
-
@technobabble said:
Server desktops to use a Medical Billing program and scheduler.
I would probably want to secure that a bit. Pertino or OpenVPN or whatever is a pretty minimal cost and effort for a lot of peace of mind.
-
Thanks @scottalanmiller and others. I will add it to my list of must haves for this client.
-
SAM hit the nail on the head. We can secure the RDP sessions for you. The management console should make it easier to manage contractor sessions, especially compared to port-forwarding/opening for RDP or even traditional VPN.
If you haven't set up a Pertino network yet, definitely check it out. I'd want to make sure the topology matches what you had in mind. If you have any additional questions, you can get me at [email protected].
Thanks guys,
Josh
-
@technobabble said:
Server desktops to use a Medical Billing program and scheduler.
Are they servers, or are they desktops? Is it a 1:1 ratio VMs to users, or is it shared, like RDS?
-
@Nara
RDS -
You could put Pertino only on the RDS server and on the machines that connect to it. Very simple setup.
-
@technobabble said:
@Nara
RDSIn that case, why not an RDS Gateway? Combine it with RD Web Access, and you have an easy portal for users to access their RDS sessions with while still keeping things secure.
