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.

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.

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.

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.

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.

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.

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 include a feature for remote control to record remote system administration sessions in compressed video format for advanced auditing either in Configuration Manager 2016 or in Intune.

This is being asked in some outsourcing scenarios. Text based Logs are not sufficient in some cases.

When providing support using remote control, and the client needs to be restarted, I have to run a ping to see when the client is back up, and then restart remote control manually after waiting for the service to become available. Ideally remote control would perform these checks automatically once the client has been disconnected, and then reconnect as soon as the client is available again.

More and more products integrate teamviewer for remote control in there products like service now. SCCM should also include teamviewer in remote control to take over a system anywhere in the world over the internet also.

When devices have multiple IP address recorded in DNS this could be either obsolete records or where devices have more than one network connection (wired / wireless) it would be really useful if all available IP addresses were tried as part of the connection process.

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

1.Remote user Cursor visual when remote user use
2.choose Remote screen when user have dual screen
so if u remote you your client u can choose display to see.
3.add option for ping/
4.change service startup sms or cmremote to auto/
5.send file.
6.open remote control and insert immediately IP Or Hostname
7.speed up protocol

Provide an option to be used in conjunction with the "Prompt user for Remote Control permission" setting. The option would "Allow Connection if User Approval times out".
We want to have people get approval from users before dropping in on them, but sometimes the user has stepped away from their computer but needs something fixed while they're away. Allowing this option would provide a good middle ground.

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.