Remote Desktop Protocol (RDP) Integrated in Bomgar
Natively, Microsoft Remote Desktop Protocol has no centralized management, limited identity management integration, no auditing or reporting, and no collaboration capabilities.
In addition, RDP is designed for remote access on a local area network (LAN). Establishing remote desktop connections to computers on remote networks usually requires VPN tunneling, port-forwarding, and firewall configurations that compromise security - such as opening the default listening port, TCP 3389.
Fortunately, Bomgar lets you eliminate these problems with RDP. Routing RDP through Bomgar brings all the appliance-based security benefits of Bomgar to each remote desktop connection and gives you new options for collaboration!
Worried about Security for Microsoft Remote Desktop Connections?
Eliminate RDP Port-Forwarding, VPN Tunneling and Risky Firewall Configuration
Bomgar works over the internet and through firewalls with no pre-installed client on the remote computer. Integrating remote desktop brings Bomgar’s streamlined connection process to RDP - which makes connecting to Windows systems on remote network both easier and more secure! When you route remote desktop through Bomgar, you can still use native RDP to support systems on remote networks. But because Bomgar works through firewalls, you prevent the exposure of listening ports to the internet.
Lock down port 3389 for good!
Define Who Can Use Remote Desktop Connections
Remote Desktop Protocol does have some identity management capabilities, such as Active Directory (AD) integration and smart card authentication. However, as with many traditional remote access tools, centralized user management remains difficult.
If a support representative leaves the company, for instance, his RDP privileges are automatically removed from Bomgar when you delete him from Active Directory. Automatic deletion protects your systems from unauthorized remote access.
Remote Desktop Security Requires an Audit Trail
Organizations who use native RDP need a better audit trail. Because RDP has no centralized, tamper-proof logging and reporting, it can be difficult to know how many remote desktop sessions took place, much less who did them or how long they lasted!
Bomgar changes that. Built-in reports give you visibility into every remote session, even those involving RDP. All of your support session reports are kept in one, secure repository. Bomgar even makes video recordings of remote desktop sessions.
Secure Encryption Guards Each Remote Desktop Connection
While more recent versions of Remote Desktop use 128-bit encryption, some older versions of RDP do not support this level of encryption.
Contrast that with Bomgar, where every connection is guarded with 256-AES SSL encryption. When you route RDP through Bomgar, that same level of encryption guards your remote desktop connection.
How Remote Desktop Protocol works in Bomgar
Every Integrated RDP session connects through a Jumpoint to the Bomgar appliance. The Jumpoint can also be used on a remote network to enable secure remote access to Windows systems on that network without opening an external firewall port.
Once you require RDP connections to go through the Jumpoint, you can centrally manage and report on all RDP activity through Bomgar.
Share or Transfer RDP Sessions with Bomgar’s Collaboration Features
Have you ever wanted to share a Remote Desktop session with another support rep or expert? The server version of the RDP client allows multiple RDP sessions to occur simultaneously on the same system. But does any version of RDP let multiple people access the same session?
No. But when your route RDP through Bomgar, all the collaboration features of Bomgar apply to your Remote Desktop session.
Bomgar lets you collaborate with almost anyone without disconnecting from your original Remote Desktop session. You can even share a Windows RDP session with a support rep on a Mac or Linux computer. Because you're working through Bomgar, you can access Windows systems from non-Windows platforms.
For organizations currently using normal (non-RDP) Bomgar sessions, Integrated RDP addresses the following issues:
Standard Bomgar session can only connect to a single instance of a Windows Server.
Integrated RDP can access the console and Terminal Services sessions of a Windows Server.
Current Bomgar clientless Jump-To requires a non-standard configuration of the endpoint.
Integrated RDP uses the built-in Remote Desktop feature of Windows operating systems.
Standard Bomgar sessions allow the end-user to view the screen (even privacy screen can be overridden by the end-user).
Integrated RDP allows reps to support an endpoint in a unique user session.
The endpoint screen resolution can be very different in a standard Bomgar session, which can be challenging to support.
Integrated RDP allows support reps to specify display resolution and quality before initiating a support session.
Use Jump Clients as a Remote Desktop Alternative
Integrated Microsoft Remote Desktop Protocol (RDP) allows you to access remote computers, even if the system is unattended. When you connect, you can use commands native to Windows.
But that's not the only way to connect to remote computers with Bomgar. Jump Clients are a great Remote Desktop alternative.
You should use a Jump Client whenever
The computer may leave the network
You want more detailed reporting
You want remote access from a mobile device, such as an iPad or Android tablet
You want the benefit of Bomgar's support session tools