Remote control is unable to see the CMD window when connected to Windows Server Standard (datacenter not tested), build 2004 and 20H2. Tested working for Server 2019 Core. ConfigMgr 2006

It would be very useful if SCCM could integrate/manage/expand the Quick Assist native Windows 10 functionality. This could solve the lack of remote control functionality when client are connected over internet (both CMG or IBCM scenario). This would allow us to avoid using third parts software.

When remote controlling a device it would be great if a prompt could come up and ask if you want to wake-up the device either using Wake-On-LAN or Wake-Up in client notification based on site configuration if the client is turned off..

There should be a setting which allows to configure auto-disconnect behavior of remote tools when the session is inactive for certain mins (e.g. 15 mins).
We moved from LanDesk to SCCM, and we are really missing feature of "Close inactive session".

Using Remote Control in the new Edge for Business (Chromium) Browser. Not sure if there is a registry setting for this, but none of the features on the Supporttools page work (for me) in the new Edge Browser. Nothing happens when you try any of the links (Remote Control, ping, etc.)

In some environments the NETBIOS name and/or the DNS record of a Systemis not resolvable (VPN, multiple NICs, ..) but the System Resource IPs and Hardware Inventory IPs are often correct. Maybe the IP from the Client Online status Table "BGB_ResStatus" can also used for RCV.
So please use additionally these IP's addresses in connection attempts for CM Remote Control Viewer and not only the NETNIOS/ FQDN from DNS lookup.

The Configuration Manager Remote Control tool should prompt to wake the device if it cannot be reached. The wake should ideally go through ConfigMgr to allow for the proxy wake functionality.

When you enable Remote Control, the SCCM Agent only applies the settings once and never checks/validates the settings.

If the local Remote Control Group gets deleted/changed/corrupted, the SCCM Agent will never fix that and you cannot connect to a client.

Work arounds are a full policy reset or modify the client settings that the SCCM Agent reapplies the remote control settings.

I would like the functionality to just delegate helpdesk to connect with cmrcviewer without local right on the computer,
than we only delegate the right to read the Laps password and then the helpdesk connect with single click as admin.
Minimize the possibility to spread virus

As users roam from wireless to fixed networks the SCCM ip database is not updating frequently enough with the end user's IP/DNS entry.

This in turn causes frustration for service desks where they have to ask the customer to obtain their IP address manually.

Would be great if the remote control tool was able to obtain ip address to as close to real time as possible.

It would be great if we could schedule computers or collections to WOL at specified times. We can schedule shutdowns but not WOL.

Correct the bug that occasionally causes the "Cancel" button to disappear on the Contacting Remote Control Agent window. This is annoying. Hitting Escape will escape out without the "Cancel" button being present.

Remote Control allows the person in control to "Lock Remote Keyboard and Mouse". Also need to have an option to "Lock Remote Keyboard, Mouse, Power" button so that the machine can not be turned off during a Remote Control session. Younger kids in K-12 often do this to kick technology personnel out so they can use the computer, even if it's under repair.

Lock “Always show the connect Bar” on the client machine. This is a Feature request so that the remote control session bar will always present to the user.

We are moving from Remote Assistance (msra /offerra) to Remote Control as it's firewall-friendly but we miss the feature to connect to VIEW the remote session only without (yet) controlling the mouse and keyboard.

In the bar today, it shows the user SAM account name. It would be very useful to show the name of the person. In our environment, we use obfuscated usernames for Domain Admins as a security measure. It does mean when we activate remote control, the user at the other end does not have any idea who connected unless there is a prior conversation. Seeing the First Name / Last Name on the title would help use salivate this pain point.

Bonjour,

Nous utilisons CmRcViewer.exe comme seul outils de prise en main.
Nous voudrions pouvoir prendre la main a plusieurs sur un même poste (ou pouvoir voler la prise en main) car si un collègue oublie de quitter nous somme bloqué.

Give an option to Black Out the screen and lock the keyboard and mouse when in a Remote Control Session. This would be useful for public use/open area/lab Student computers

Novell Zenworks had this same feature years ago. (likely still does)