First create a remote office with distribution server or direct communication. Then install the agent from Web Console -> UEM -> Agent -> Remote Office. Find out more details here. To install agents in Linux machines, click here.

Here is a list of ports that are used by the RMM application. You will need to open these ports for a hassle-free communication between the Agent, RMM Server and the Distribution Server.

Each customer, managed under RMM is provided with a unique ID and the users and machines associated with each customer are mapped to it. This ensures that users can only access the details of the customers associated with them and restricts access to other customers' data.

We can create various user accounts by clicking user administration under Admin tab. User administration enables associating users with customers. Either one user can manage several customers or one customer can be managed by several users.

While creating new customers, such details can be specified. To add details to existing customers, go to the Admin tab, select customer, choose Action, and then click on Modify

If you are using a distribution server, bandwidth consumption would be low as the clients' endpoints use local bandwidth to download updates from the distribution server.

One can achieve this using the AD connector.

Yes, you can generate bills through our billing feature.

While creating a customer, these details can be provided (can also be modified later).

Yes, you can get free technical support during evaluation. You can contact our support team at rmmcentral-support@manageengine.com.

Scope of Management is a feature in RMM that is used to specify which computers you can manage using RMM. You can add and manage computers that are from an Active Directory, a workgroup or any other directory service like Novell eDirectory. The computers can either be in the same Local Area Network (LAN) or in a remote location connected through a Virtual Private Network (VPN) connection or through the Internet. For more information, see defining Scope of Management.

RMM has predefined configurations available for users and computers. These configurations can be grouped and defined into collections if they are meant for the same user or computer. However, if they are meant for individual users or computers, they have to be defined and deployed individually.

Every configuration that is applied to computers and users will be applied in the following scenarios:

• User logon or system startup: All user configurations, except the Custom Script configuration, are applied when a user logs on or when a system is started.
• System startup or shutdown or user logon or logoff: The Custom Script configuration is applied when a user logs on or logs off. This also takes place when a computer is switched on or switched off.
• 90-minute refresh cycle.

Let us see a few examples: A configuration is deployed to computers and users, to block USB devices, If the computer is turned off - This configuration will be applied during the computer start up and the USB access will be blocked. If the computer is turned on - This configuration will get applied during the next refresh cycle, when the agent communicates with the RMM server. Assuming that a USB device was already plugged in and used in the computer, the access will be denied as soon the configuration gets applied. If the User has logged off - This configuration will get applied to the user's profile when the user logs on to the computer. So that the particular user will not have permission to access USB devices. If the User has logged on - This configuration will be applied during the subsequent refresh cycle. Assuming that the user has already plugged in a USB device and has been using the device, the access will be denied after the configuration gets applied.

To access the RMM UI from a remote location, follow the steps given below:

1. Open a supported browser.
2. Enter http://:in the address bar

Note: Here refers to the name / IP Address of the machine running RMM, refers to the port where the product is started, the default being 8090. For example, 192.168.100.110:8020. Press Enter. You can now login to the RMM UI.

The Define Target feature is used to identify targets, also called users or computers, to apply configurations to. The targets can be all the users or computers belonging to a site, domain, Organizational Unit (OU) or a group. They can also be a specific user or computer. For more information, see defining targets.

RMM is licensed on an annual-subscription basis depending on the number of computers you want to manage. RMM works on unit based licensing which will detect two devices when there is one device that needs to be registered for monitoring as well as management purpose. You can get the price for a specific number of desktops from our online store. You may also buy a permanent license by paying a one-time fee. Contact us further to get a quote from our sales team: sales@manageengine.com

Probe key is used to authenticate the probes in RMM Central monitoring component. The probes are necessary for monitoring the remote offices of each customer. Each remote office will have a unique probe key. There are no additional costs to procure these probe keys. To obtain a probe key,
Login to RMM Central web console.
Go to Admin -> General Settings and choice any of the below-given options.
1. Customer -> click on customer name -> Remote offices -> click on remote office name to view summary.
2. Remote office -> Click on remote office name to view summary.
Under probe details tab, you can download probe_key.zip file

RMM, with its Web-based interface, enables desktop administrators to access the application from anywhere within a network to complete various tasks; for example, to create configurations. This facilitates easy management of computers without being required to be present in any specific location.

Here is a list of ports that are used by the RMM application. You will need to open these ports for a hassle-free communication between the Agent, RMM Server and the Distribution Server.

RMM supports MySQL, PGSQL and MS SQL database to store data.

No, currently RMM does not support IIS.

Yes, computers that are newly added in the domain will receive all the deployed configurations automatically when they check in with the RMM Server.

All the features other than patch management works effectively while using RMM in home edition of windows operating system.

Yes, We accept multiple active directory inputs in RMM.

When the agents of the remote location are unable to contact the Distribution Server, they contact the RMM Server directly during the next 90 minutes refresh interval. They receive the modified port numbers of the Distribution Server and communicate with it henceforth.

RMM has different agents for different locations, for example a local office agent will not be the same as the remote office agent. Similarly every remote office has different agents as well. When you are managing computers one or more remote locations, you can have a defined set of IP ranges for different offices. This enables the RMM Server to identify the agents with respect to the IP range. So whenever a computer is moved from a local office to a remote location, an IP scope is used to detect and deploy the respective WAN agent automatically. RMM will check for the change in the IP address periodically and will deploy the appropriate agents whenever a change is detected.

Agents will report the status to the RMM server after performing every task. In case if the RMM Server is not reachable, then the agents will update the status during their subsequent refresh interval.

If you need to configure RMM without using domain admin account, then you need a common user created in all the computers with admin privilege. However you will not be able to install agents automatically and agent installation can be done using a GPO.

Yes, RMM is capable of managing virtual computers.

Download the agent and navigate to the downloaded location using command prompt. For example, if you wanted to download the agent in D drive, execute the below mentioned command. DesktopCentralAgent.msi TARGETDIR="D:\DesktopCentral_Agent\" REBOOT=ReallySuppress

This is a scheduled task created in the agents. This task runs on the client computer and scheduled every hour to ensure that the agent version is up to date.

No, RMM needs agents to perform any desktop management activity.

No, it is not necessary for all the managed computers to have internet connection. However RMM server would need connection to the internet in order to download the patches and software applications from the respective vendors website.

Yes, RMM can be used to manage computers even if they do not belong to a domain.

You can choose to download 32-bit or 64-bit based on your OS architecture.

Credentials that have admin privileges need to be specified for carrying out certain activities in RMM.

To remove a computer that has been taken offline, navigate to Admin>>Scope of Management>>Computers, select the computers that have been taken offline, and click on "Remove Computer(s)."

With the credential manager, multiple credentials can be stored and used accordingly for different actions. Click here to know more about credentials manager.

Domain Admin credentials are required to make any Domain-related changes. You can also use the Local Admin, if it is the same for all the computers in that domain.

In this situation, if you have an Active Directory you can ensure the agent is installed when he reaches AD. Alternatively, many of my clients would take a maintenance routine to bring the laptop to the office or have a standard time to get connected to the network so that the agent can be pushed to them.

We recommend you to use a component called Secure Gateway, which acts as an intermediate to route all the communication between the agents and the server.You can refer to this document for more details.

Status update and ease of management is better in RMM and RMM supports management of workgroup computers too. Hence you gain more control on configuration using RMM.

No, it is not required to be a Server OS, it can be a simple desktop. Dedicated machines are also not required. The only requirement would be the availability of that machine with zero down time.

Under Custom Group you can add all the computers managed by RMM and deploy configurations. Group management is a configuration through which you can manage the local groups in a particular computer.

If you move any configuration to trash, it can be restored anytime. Configurations are not automatically cleaned up from trash, you will have to remove them manually.

No, it will not get executed. Once you move the configuration to trash it wont get executed. To move the configurations to trash automatically go to configurations tab -> settings -> configuration settings -> enable move configuration to trash option.

You can choose to configure the notification settings while creating the configuration, so that the administrators will be notified whenever there is a change in the status of the configuration.

Moving a distribution to the edge is not necessary, distribution server will replicate the required data from RMM and the agents within the respective remote office will communicate with the distribution server.

No, the refresh policy cannot be changed.

Yes, if you deploy the configuration to security group/OU/Custom group then configuration is perpetual.

Restricted sites will be applied to Chrome and Internet Explorer.

You can block exe's using "Block Exe" feature.

Irrespective of the status, the configuration is moved to trash if it is inactive for the "X" number of days.

Blocking the USB is based on the device type. Hence, it will not block the critical devices.

Group Policy Settings will not be overwritten by using RMM Configurations.

We do have a configuration to defrag the Hard Disk Drive. However, finding the type of drive is unavailable for now.

You can download the Agent from Admin-->Scope of Management-->Computers tab and download Agent.

Yes, you can install Fonts using Display Configuration for computers.

It is available in the inventory tab, under USB audit.

Best choice is to overwrite the existing drive and also choose to apply always to make sure drive mapping gets configured during every logon.

Currently we do not have this option, however we will take it as a feature request.

You can choose to add multiple domains using RMM.

It is recommended is use either GPO or RMM configuration to apply the settings. Do not use both to do the same task.

No. Currently we do not have this option, however we will take it as a feature request.

Yes, Custom Script and File Folder operation configurations should be used to achieve this.

RMM supports both Domain and Workgroup. To install Agent for machines connected to network once in a week, then configure the agent retry to install it.

Yes, you can identify this, by using the Inventory reports from RMM web console -> Reports -> Inventory Reports -> Computers with/without software.