When we connect to computers using the CM Remote Tool (SCCM 1710) and the our keyboard language differs from the user's language (we use EN by default, users - RUS) - language bar is desappeared, keyboard can not be swithched to ENG. If we and user has same keyboard language - all right.

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 need to push user/group based remote control permissions. It would be great to have custom settings for different groups atleast Prompt user for Remote Control Permission.

In our environment we need to implement prompt for permissions based on job profiles.

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.

Need is an easy way to allo Singel User allow Remote Control Clients
For Example: One Single User must remote controls one client you must create new Client Settings and deploy.
A Remote Control User Management would be nice

A Most Recently Used list of connections would be a timesaver!

Or is there other software that can connect to sccm clients?

If the user that tries to remote control matches the current logged in user then do not prompt for approval.
This is a common case where a IT support user login to a remote client in order to do support work with higher permission. If there is a connection drop the IT support user cannot remote back to device if the user is not there and the device will be left with a high permission account logged in.

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.

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.

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.

The Remote Control Viewer is missing features which are the norm in many other Remote Control solutions.
Among them:
- Button to Remote Lock the screen of the computer when the supporter is done with work.
- Button for a Remote Reboot and wait for the machine.
- Ability to configure that Key Combinations like Windows + R are sent to the remote computer instead of being executed locally.

I want to customize requests for remote control.
Now requested user see only login of requesting user.

it will useful to see other information about requestor (such as Department, Full Name and so...)

Please apply a simple string trim to the address field. A lot of copy and pasting goes on leading to an extra space that the tool take literally and refuses to connect. A small, simple thing, but something that can be frustrating.

I would like the ability to send the user of the device I'm remoting into a message.

I've just had a client leave his Surface Pro 6 on an aircraft. No MSA set up, just a corporate Microsoft 365 Business account with Azure AD P2.
I was surprised to discover I could not remote lock the device (like I can any mobile), just wipe it. Please add the ability to use "Find my device" and "Remote lock" without needing a MSA. You removed the ability to sync settings on domain joined machines using a MSA, why insist on having one for remote tracking and security!?

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.

It could be great if we allow triggering the client via the notification agent to start remote controlling,
So an admin could still start a remote control task from the console but the client will actually create the session.

this way we could:
1. eliminate the need for port 2701 to the clients
2. eliminate the need for client DNS name resolving
3. potentially, allow remote control via Cloud Management Gateway for internet clients