Yes, all the configurations applied to the OU will be automatically applied to the newly added computers.

Scanning will be initiated incrementally in order to avoid bandwidth bottlenecks.

You can create a custom group with the computers which you wanted to exclude. Decline the application from, Patch Mgmt -> Decline Patch -> Decline Patch for Group -> specify the application.

You should configure “Automated Patch Deployment Task” and ensure that the schedule is run every day to keep your computers up-to-date.

You can see the “Installed Time”, against the patch, if it is installed using RMM Central. If you do not find the “Installed Time”, then it could be patched using automatic updates. In such cases, you will have to disable auto-updates from, Configurations -> Script Repository ->Templates tab -> Search for AutomaticUpdates.exe -> add to repository. Create a configuration, select the target computers and deploy it.

We would recommend using a HTTP share as the software repository for computers at remote locations. This would ensure that all the computers can reach the software repository easily.

"Run As" is the option which is used for the applications that need to be installed as a different User. Since RMM Central supports Multiple Active Directory domains and work-groups, we need to associate the credential supplied in SoM with the corresponding Domain or work-group.  In order to handle such scenarios, RMM Central gets the additional user name and password for RunAs.  However, if "Run As" is not specified then system credentials will be taken by default.

The MSI Root Path is mainly used for the following:

If the MSI file is browsed and chosen then the MSI Root Path is automatically taken.  It becomes mandatory only when the MSI file name with network path is manually entered.

Yes, you can install a software application when the UAC feature is enabled if you are not required to enter information during installation. However, if you have to enter information during the installation of a software application, you must create a user configuration without selecting the Run As option. When you use the Run As option in a user configuration, use the Default Administrator account.

No, installation will not happen, only the installables will get copied to the end user's machine.

Yes, you can use RMM Central to group the software based on versions. "Group Software" is the feature which allows you to group different versions of same software for better visibility and license management.

If a software was rejected, then the software would be removed from the target computer based on the auto-uninstall policy specified. However, if the admin again approves it, it can be reinstalled and won't be removed. Lets imagine there is a delay in approval. So, it would be automatically uninstalled if it was not approved till the given threshold day count. If the uninstall threshold is yet to reach then the software would be available.

If the new version of program is automatically upgraded then it is not required to add the new version into prohibited list. Else, you will have to add it manually. Create a software group with all versions of the particular software and include the software group to the prohibited software list. It also provides a great way to have software version control in the network by not allowing other versions of same software.

You can use "Block Executable", to block the application/software in a pro-active manner. However, RMM Central positions this feature as a procedure to block non-standard executable which are used in your network, It would help you to prevent your network from data leak and other security threats.

You can choose to disable specific applications using the 'Block executable'. This allows you to block only the specific required application. For example, if, you want to block Microsoft Excel you need to do it by mentioning its specific name, excel.exe. This doesn't prevent you from using word.exe. Similarly, Outlook continuous to work unless it is specifically blocked.

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. 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 is used by the RMM application. You will need to open the following 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.

You must open the the following ports to use the Remote Control feature:

By default, the Remote Control feature uses a secure connection. These ports have to be opened on the RMM Central server.

You must open the following ports to use the File Transfer feature during a remote control session:

These ports have to be opened on the computer on which the RMM Central server is installed.

You can use the Remote Control feature on the following browsers:

• Mozilla Firefox
• Google Chrome
• Microsoft Edge Chromium

You can set the compression level to Fast, when using the Remote Control feature, to improve the page-rendering speed. The bandwidth consumption will be comparatively higher when compared to best compression level, however the page-rendering will be comparatively faster.

When you set the compression level to Fast, the compression ratio is lower, resulting in an increase in the speed of the rendering of the UI. This is recommended when the computer that you are connecting remotely to is in the same LAN as the computer you are connecting from.

When you set the compression level to Best, the compression ratio is higher, resulting in a decrease in the consumption of the bandwidth. However, the rendering of the UI will be comparatively slower. This setting is recommended when the computer that you are connecting to remotely is at a different geographical location.

To clear chat history follow the steps mentioned below;

Chat session will fail in the following scenarios:

You will not be able to chat with the user if the user is offline.

The list of user names will be updated in three scenarios as specified below.

You can refer to this document.

You can refer to this document.

You can refer to this document.

You can refer to this document.

You can refer to this document.