Yes, it is possible for multiple users to login remotely to a computer at the same time. However, only one of the users who has logged in can take control. The other users can only view the changes that are being made.

You can lock a keyboard or a mouse to ensure that you can make changes effectively. To lock the remote computer's keyboard and mouse, click the Lock Keyboard/Mouse icon from the viewer.Similarly, you can blacken the monitor of a remote computer when you do not want the user to view the changes that you are making. To blacken the remote monitor, click on the Blacken Monitor icon from the viewer.

When you take a remote session of a virtual computer, you will result in viewing the screen of the physical machine in which the remote session is hosted.

To locate the file where a remote control session is recorded, first navigate to the directory where the RMM server is installed. Then, go to RMM_Server\webapps\DesktopCentral\server-data\\rds\scr-rec Extract the zip file in this location to view the recorded video clip.

Collaboration can be done with any technician with "Remote Desktop Admin" privileges.

Yes, this is possible by navigating to tools --> Remote Control --> User Confirmation --> Enable "Make user confirmation permanent."

The RMM agent installed on your remote computer will run with system privileges, hence it will have the required permissions to execute remote control tasks.

The technician who initiates remote connection will have the privilege to swift his control, when additional technician join the same session.

De-fragmentation task from RMM is completely an independent schedule and it does not disturb the existing windows schedule. This task will be performed besides the existing task of Windows, if any.

Yes, there is an audit on this. However, it the tech account is hacked then the audit would say at what time and which technician has taken the remote session.

If you are connected to the machine from the console, yes. You can launch the cmd prompt from quick launch even if the user doesn't have access to open it. It will be opened with the system account privilege.

Establishing a remote connection does not blacken the remote monitor. Both the end user and the technician will have access to view the screen. If you want to blacken the display on the end user's screen, you can configure it using settings under Remote control.

RMM will maintain the orientation and the aspect ratio (Landscape and Portrait format). Ability to view multiple monitors on a single pane is in development phase and will be released soon.

Recorded remote sessions will be stored on the RMM server. You can locate it from RMM web console -> Tools -> Remote Control -> Settings -> History. You can hover the recorded session to find the exact storage location.

You can choose to re-initiate the chat session without disconnecting the remote control. Chat session is not dependent on the Remote Control Session.

RMM by default initiates the task based on the server time. So, it is recommended to schedule the task accordingly.

RMM can identify, if the port allotted for remote control is used by another process. You can modify the port from, RMM web console -> Tools -> Remote Control -> Settings -> Port Settings.

You will have to turn on the Recording feature (from, RMM web console -> Tools -> Remote Control -> Screen Recording -> Enable Screen Recording, before initiating the remote session for screen recording to capture.

RMM does not need any specific license for multiple technicians to participate in the same remote session. However the same technician can not try to initiate multiple remote sessions with the same computer simultaneously.

Yes, if you have initiated the reboot from the quick launch options available, the remote session will be reconnected automatically.

If the RMM agent on the roaming computer is able to reach the RMM server's gateway port, then the remote connection can be established. You can verify the port reachability using telnet.

"Disable Keyboard and Mouse" is applicable only for the user on the client machine, this does not apply to the technicians. Once the remote session is disconnected the mouse and keyboard will be automatically enabled on the remote computer.

RMM allows you to initiate remote session with a computer even when no user is logged on or when the "ctrl+alt+del" screen is active. You use the remote control tool bar to invoke "ctrl+alt+del" screen on the agent computer.

You can use Wake On LAN to wake computers, which are shutdown. However, if you want to wake a computer which is not in the LAN as RMM server, you will have to ensure that at least one computer within the same subnet (as the target computer) should be active and have RMM agent installed in it.

Initiating a remote session using RMM does not entitle the user with administrative privileges related to software deployment. You will have to use RMM's Software Deployment module to perform this operation. You can perform this operation from, RMM web console -> Software Deployment -> Deployment -> Install/uninstall Software -> create configuration -> Package settings.

You can check the action icon, if you could see "blacken monitor" is changed to "revoke monitor", then you can feel assured that the remote monitor has been blacked out.

You can enable it by configuring the settings, You can refer this document, to know the steps involved in configuring the "Wake on LAN" settings from, RMM web console -> Admin -> Global Settings -> Agent Settings- > Enable Wake On LAN Settings. You can also refer <https://www.manageengine.com/remote-monitoring-management/help/wake_on_lan_tool.html>this articlefor more details.

You can transfer any type/format of files and there is no restriction on the size of the file.

Wake on LAN might fail, if the target machine belongs to a different subnet. You should ensure that there should be at least one machine turned on in that subnet, so that it could act as the Wake on LAN proxy for the whole subnet.

Announcements work based on the "Server Time", if you schedule to broadcast an announcement at 12:00 hours, and the target computer time has not reached 12:00 hours, then the announcement will be displayed.

Yes, you can remove the reason box from, RMM console -> Tools -> Remote Control -> Settings ->disable "log reason for remote control."

The number of technicians is determined by the number of technician licenses that you own, however the speed depends on the available bandwidth.