Would like to see an option to configure a timeout on remote control sessions in N-central. Would like to be able to configure a 15 minute timeout after no activity for the specified time. Currently there is no option to configure a timeout (N-central Case# 00927594).
I would like an option to globally, or per customer restrict the number of concurrent remote control / remote management sessions. For customers with certain compliance requirements, we need to ensure we can account for every remote control session and change made on a per-tech basis. Maintaining a unique set of credentials for every device in every customer environment for each of our Technicians is not easy. If we ...more »
There should be option to edit remote desktop session timeout value. When n-central users connect to devices, connection stay open even after initial RDP session window is closed.. In many cases only way to close remote control session is to push the red button to disconnect. This kind of behaviour can be also seen from audit trail.
While current MDM functionality is a boon, I opine that the most needed feature is remote control of mobile devices.
Please add this functionality as soon as possible.
Thanks in advance,
MSPAnywhere is not a complete replacement for Team Viewer. Not being able to hear the audio for some of my clients is an issue because they do work with audio equipment. Additionally we lost the ability to Call by Internet or Voice Chat. These features need to be brought back.
We would like to be able to report on devices based on their remote control method, and whether unattended access is configured. A "who changed this" would be great as well.
This would be useful to determine compliance in situations that require this information, and to easily let our clients know when they ask for this information.
When is MSPAnywhere based remote support viewer going to be implemented to replace the antiquated and unreliable VNC based one? The existing VNC based one isn't even supported any more.
This could be an invaluable tool to onboard new agents and to be able to offer support to client pcs (without agents - like their home computers) for attended remote support.
Please give us the Option to close MSPA Sessions from Client side.
Currently there is only a Reboot as viable stop to the Remote Connection...
Closing the Processes does not really kill the Remote Connection
Show a pop-up window confirming the tech has disconnected from the session. We often stay connected accidentally or the client wants to be sure we are disconnected. We usually close the blue pop-up window showing that "So and So has Connected" remotely, but we also need a confirmation saying when we've DISconnected. Allow the End User to disconnect if desired. All other remote tools have this functionality. Also ...more »
Starting with Windows Build Build 1497, Powershell is to replace the command prompt as the default shell and signalling the end is near for the command shell sub-system. Please change the shell to Powershell in the Remote Background feature before it becomes unavailable/unusable (or give us the option choose the shell via a policy). https://blogs.windows.com/windowsexperience/2016/11/17/announcing-windows-10-insider-preview-build-14971-for-pc/#3dUWruqyP1tX5x0V.97 ...more »
Include a "leave a note for end user" function in Take Control so when we are done with a remote session they will know without us trying to communicate with them via phone call. Similar to Chat only it stays displayed on screen after we close out.
Pleas don't replace Teamviewer/TakeControl through your own bad solution. The software works so much worse than Teamviewer.