When using SCCM to remote control multiple monitors; allow the ability to select only one monitor to be remote controlled; vs. the option now of only stretching.

Internet based remote control with options such as file transfer and reboot. This could be accomplished using a reverse connection from a client to a new site role hosted in the DMZ.

One of the biggest issues I hear with the Remote Tools is that when you restart a machine it takes a couple of minutes before you can remote control it again. This is due to the delayed start of the service. I assume that this cannot be changed per default but give us the option using a client setting to change it to Automatic instead of using a GPO would be really sweet!
This is very similar to the following feedback item. https://configurationmanager.uservoice.com/forums/300492-ideas/suggestions/8471107-fix-remote-control-bug-after-client-reboot#comments

When we remote control a client , the client can see the mouse pointer, but when the client want to show us someting, we cant see mouse cursor.

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

It would be nice to have a chat feature within the remote control client. This way I can chat with my users when they are using the computer and I need them to complete a task after I am remoted in.

Improvement with Remote Control to support OS X , Windows ( inc mobile) with some new features - Chat, file transfer , privacy curten.

Having the ability to look through a dropdown history of connections would make reconnecting easier and shouldn't cause too much programming hassle.

Having a log of connections with date/time of connection/disconnection, IP of source and destination would also be valuable to have as reference.

Allow Remote Control by right-clicking a username so that the user doesn't have to look up the computer name.

This would be enormously helpful in the Education sector where users are constantly moving between PCs. Novell had this feature in ConsoleOne and it enabled superfast remote control of users for our Helpdesk staff.

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.

For some troubleshooting scenarios in a multi-tier service desk organization we need to have 3rd tier staff connected to a end user's PC simultaneously to an already ongoing 1st staff remote session.

When adding a printer on a Windows 10 client through remote control, the session gets disconnected.

It looks like others have encountered the same issue:
https://www.reddit.com/r/SCCM/comments/5ntq4v/remote_control_disconnects_when_addingworking/

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.

Remote control is nice but we are unable to use in my company due to Auditing issues where the sessions cannot be logged.

Could there be a option added to SCCM to allow for logging of the Session each time remote control of a computer occurs?

Allow more than one policy to be applied for remote control, giving the ability to allow for tier remote control access. Example: The ability to remote an unattended workstation with admin rights for help desk staff, while traning staff is only allowed to remote attended workstations and does not get admin rights.

Add a drop down box in the remote control viewer with recent computers. Additionally, add a prompt to select a computer when starting the program.

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.

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.