Devolutions Remote Desktop Manager Reviews

We use the solution for a customer that needs pretty high security. They are in the poker machine manufacturing world based out of the US. They've got offices all over, and the Australia/Sydney office actually supports the whole of the Asia Pacific. They use it to to remotely connect into the management of the servers that run the poker machine manager software within a casino. 

The security on offer is the most valuable aspect of the solution. It offers, for example, two-factor authentification.

The remote connection across platforms is great. You can deploy it on anything, including Windows, Mac, iOS, your iPhone, et cetera. It offers multi-platform utility. This makes it great for enterprise.

Users can use it for PAM access as well.

The feature of Devolutions that has improved our customer's efficiency the most is probably the security side. It's gotten a lot tighter. Authentication and secure connections are helpful. They use encryption between them, which is just standard for them. The company has so many regulatory controls that they must ensure their security is very tight. There's a lot of potential cybercrime around casinos, and this solution ensures they are well-protected. Devolutions is a great product that can be safely used between China, Australia, or the Philippines, and it remains a good, safe product.

I use RDM to manage 99% of my remote connections, such as RDP, SSH, SCP File Transfer, iDRAC, iLO, VMware vSphere Web Client, VMware vSphere Client, URLs, etc.

RDM has enabled me to do most of my work in one place. This helps me be able to have an RDP session open to a server in one tab and an SSH session open to a VMware host in another.

Also, being able to store my credentials makes connecting a breeze.  And being able to search the over 500 entries via the status bar at the bottom makes connecting EVEN FASTER! :) 

My primary use case is the remote server connections for multiple protocols.

I also use it for managing multiple website login credentials and for application connections via available plugins.

I was able to maintain connections to over 400 different servers and services using password best practices. This allowed me to resolve the issue rather than waste time looking up passwords to the various servers. In addition, once I upgraded to the Enterprise version, I was able to manage some advanced connections (such as SQL Server .NET only connections) with the same interface and not have to remember the (relatively) convoluted steps taken each time to initiate the connection. Again, making me instantly more focused on resolving the issue rather than getting to the issue.

I use Remote Desktop Manager to centralize all my different connection types, like Linux servers via SSH, Windows servers via RDP, VMware hosts, and for all the devices that I manage.

The ability to have all the connection information in one location saves so much time from trying to manage the same information across different applications.

By integrating all our connections previously spread across multiple locations, a lot of time has been saved. 

The interface is great to work with as it allows multiple connections in a tabbed interface. It also has the option to automatically start a VPN or an SSH tunnel, if required.

• Centralize all our customer and in-house credentials and remote connections.
• Configure limited access to resources with the security-based role feature (for trainees and new employees).
• Daily usage of some of the numerous integrated VPN solutions for connecting to our customers, when we are remote.
• Keep the credentials up to date with version and Change History.

With the integrated VPN providers you are able to link the VPN entry directly to the session or entire folders, so you no longer have to configure the VPN manually on the machine.

More security with granular security features.

My company is a consulting practice that connects to client systems using various methods. So, we need credentials, VPN connections, and also operational instructions. RDM provides a single repository for all this and so much more.  You can include PowerShell scripts to accomplish tasks.

We used to store information in our CRM system, but it did not allow linking connections with credentials with VPNs. Now, when a consultant wants to connect to a client server: 

1. They launch the connection
2. It checks for connectivity
3. Opens the VPN
4. Then connects.

All without the consultant needing to look up information, or even if we wanted to restrict it, to have access to the credentials used.

We use this software to have all of our RDP and other connections in one place, which is primarily used for our server access.

It saves a lot of time for all of our IT staff from having to just use the RDP Windows client and reenter each server every time we access a different system. 

It also allows us to connect to our VNC clients and Lab PC.

We use this to control all of our virtual servers within the organization. We needed to switch to something other than vCenter since VMware went to a web-based client and it actually slowed down the support we could offer.

It sped up our response rate to anything that happened in the network. With vCenter it was starting to slow down and the web-based client just took forever to load. Since we have been using this it only takes two to three seconds to remote into one of our servers and be able to make changes and control it.