RMM Central configurations

Introduction to configurations

RMM Central offers configurations that help administrators manage applications, system settings, desktop settings, and security policies. These are extremely helpful in baselining systems and targets can be selected at user or system level. A group of configurations can also be applied together using the collection feature. The selected settings comes into action either during user logon or computer startup (depending on the type of configuration applied) to minimise the loss of productivity. Status of the applied configurations can also be tracked anytime.

Defining Configurations

Configurations can be defined for computers or users. You can define a configuration from scratch or use predefined configuration templates. You can also create a group of configurations and deploy them as a collection.

Defining configurations is a four-step process. It comprises of the following steps:

1. Enter a name and description for the configuration
2. Defining the configuration includes the following:
   • Package settings
   • Deployment settings
3. Define a target
4. Configure execution settings

After you define a configuration, you must apply it to specific targets (computers/users) in your network.

Applying Configurations

When you deploy a configuration using RMM Central, the configuration settings along with the required files will be stored in the RMM Central server. RMM Central agents, which are installed in the client computers in your network, will contact the server to collect this information and apply the configurations to specific client computers. The agents will contact the server during the following intervals to collect the required information:

• User-specific configurations: When a user logs on and every 90 minutes thereafter till the user logs out of the domain
• Computer-specific configurations: When a computer is started and every 90 minutes thereafter till the system is shut down

Re-applying Failed Configurations

When you deploy a configuration to client computers, the deployment could fail in a few computers due to various reasons. In such cases, you can re-deploy the configuration. RMM Central enables you to automate the redeployment process through the Execution Settings option. This option enables you to do the following:

• Specify whether you want the agent to retry applying this configuration in the computers in which the deployment of the configuration failed
• Choose the number of times you want the agent to try deploying a configuration. You can also specify how many times, out of the number of times that you have specified, you want the configuration to be deployed when:
  • Users log on
  • Computers complete the 90-minute refresh cycle

Based on the specified input, configurations will be re-deployed on the computers on which the deployment failed till  either of the following takes place:

• Deployment is successful
• Maximum retry count is reached

Reverting Configurations

RMM Central does not take backup of the settings that you make when you create configurations. Therefore, it is very important that you remember the settings you have made. In most cases, you cannot revert the configuration. However, you can modify the settings that you had made earlier and re-deploy the configuration.

Examples

You can modify configurations and re-deploy them in the following scenarios:

• Assume that you have deployed a configuration to install a software application. You can revert and change it to enable uninstallation of the software application. You must modify the configuration by changing the following:
• Operation type from Install to Uninstall
• Type of package

• When you want to revert a configuration related to a security policy, you can modify the policy and change the settings as required. For example, assume that you have created a configuration to disable the option to change the wallpaper on the desktop of a computer. You can modify the configuration and change the policy to enable the option to change the wall paper, before re-deploying the policy.