It would be nice if we could configure a non-default port for remote control and remote desktop. This will allow organizations to set a specific port.

Add the Computer's Description (not from AD) on the Devices window.

remote tools allows the end-user to disconnect the session. the problem with this is if the user that logs on what the IT Admin, the user can disconnect him/her and use their account instead of their own.

this scenario is common on a help desk, so it would be good to know who logged on (remote or local) and when the connection is lost, automatically lock/log off the session.

Teamviewer provides this feature, and it's incredibly helpful when working on machines.

Please allow us to see the remote mouse cursor in the remote control viewer!

We had to create a software that displays a little dot which follows the mouse of the remote user and our tech have to launch it manually when connected remotely, this way we can see where the remote cursor is located but it's of course very impractical.

Add an address book in the viewer in order to be able to populate it with useful targets

Provide the remote control viewer tool in MSI format "out of the box".
This will permit to distribute this tool to people who don't require the full console ( i.e devs, Help desk, ....).
Moreover, packaging it as a standalone tool will prevent from deploying binaries manually forgetting registry keys that are mandatory to log remote control events.

Remote to users workstation in invisible mode were they do not know you are on there station. This feature is available on dameware and it is extremely handy. Please Please Please implement this.

Remote tools connect on ping. Same as Dameware Mini remote Control if you restart a computer it will keep trying to connect until the machine has restarted. This is really handy so your are not guessing when to reconnect.

When trying to use Remote Control from start->remote control in the console, it is not possible to connect to machine that is not part the same domain as the server as netbios is used. If the FQDN is called than it would be possible to connect to devices in trusted domains.

I have noticed that the clipboard is cleared after pasting the computer name\IP into the address field. I know its a small issue but it gets tiresome to have to go back and copy the computer name every time I use the remote viewer.

Add a better message to distmgr.log including which certificate and site system it’s having problems with.

Right now you have to guess which DP is having issues, which can be a tedious and large task if you have a lot DPs.

Jason Sandy has also suggested this to the product team earlier this year:
http://blog.configmgrftw.com/configmgr-post-restore-step/

It could be really useful to have a way to fully disable the clipboard sharing during a remote control session.
We can do it with a registry key in HKCU but it can be enabled without admin rights, just by clicking on Action -> Enable Clipboard sharing.

A better solution would be to disable it for a computer in HKLM or ideally directly in the SCCM console.

CAC card authentication via remote control doesn't work. For organizations that utilize CAC cards this would eliminate the need for utilizing username and password which is a pass the hash vulnerability.

Please provide smart card pass through for RDP/Remote Control sessions.

Add a feature to send a message to a user which appears in the request to remote control. e.g. connecting to fix your office issue.

lets the end user know why someone is connecting.

Some issues can only be resolved after the user is no longer in the building. Often times users turn computers off and walk away. It doesn't appear that there is an easy way to just send a WOL packet from the SCCM Console to boot the machine back up.

We cannot use Remote Control as Administrators cannot route to all endpoints from their PCs. We would like to proxy the Remote Control through a central server or be able to leverage RD Gateway.

Support for Windows 10 1607 Remote Credential Guard in the remote control.
Add a client policy to require och prefer connection with Remote Credential Guard or Restricted Admin