One of the main benefits of using MRC instead of RDP is the ability to interact with the end-user. Because we specified that permission is required, the end-user will see a prompt before the session is initiated. Now let's go ahead and initiate an MRC session with a remote machine.

And on the Access tab, you can restrict access to the remote machine by requiring the admin to be a member of specific groups. Here we see the IP Filter, where you can define IP ranges that are allowed or not allowed to connect to this machine. Here we see the Notify dialog, and by checking this setting, the end-user is always notified that a session is in progress. There are also a number of other settings that can be configured on the MRC Client Agent that provide a very granular degree of control over how the admin can connect and interact with the end-user on the remote system. By selecting this setting, the end-user will be prompted to allow or deny any MRC connection attempt to that machine. Then check the “Permission Required” box. While on the remote control product, open the MRC Client Agent and then go to Additional Settings. This is easily done through a very simple configuration of the MRC Client Agent. Let's go ahead and get started.Ī common customer requirement is to require the end-user's permission before initiating a remote session with that user's machine.

In this video, we'll cover how to get around some of the headaches associated with using Microsoft Remote Desktop Protocol, also known as RDP.

My name is Craig McDonald, and I'm a Senior Product Manager here at SolarWinds.

Dameware mrc agent