There are 3 layers of enablement
- RMM
- Client
- Agent
Each one always relies on the layer above it. RMM is the top layer and effects all clients and all agents. Client’s layer manages any agent under the client’s management, and the Agent’s layer controls a single agent. Generally and for each tool you can enable or disable an agent or client which will effect any agent under that client.
Example:
- Must have Enable Daily RMM Sync enabled to communicate with RMM at any level.
- Must have Allow Tool Automation enabled to allow tools data collection and management to be allowed at any level.
- Must have Client General enabled before any agent layers will be allowed to operate.
- Must Client Enable any tool before that tool will work on agents under client.
- Must Agent Enable generally for tools to work.
- Must Agent Enable each tool that you want agent to use.
This allows you to:
- Disable entire service with one click (Enable Daily RMM Sync)
- Disable all Tools with one click (Allow Tool Automation), but keep basic sync of environment running
- Disable all actions across the client for everything (Disable Client General) with one click
- Disable any tool across the client for all enabled agents (Disable Client Tool) with one click
- Disable all actions on an agent (Disable Agent General) with one click
- Disable any tool on an agent (Disable Agent Tool) with one click.
By following these guidelines you can control each agents ability to scan for tool data status and commands. If you are having problems with agents not displaying accurate or current dates are not reflected in views then you may have one of these layers disabled.
Things to check first:
Is the RMM Layer Enabled?
Check the RMM Environment to see if your set to communicate with the RMM.


Check The Client:
Check that the client is enabled generally and for each tool you want to deploy. Select any client from the client list then select the different tabs verifying that they are in fact enabled for the tools you want to use.





Software Manger is a little different at the client level. You can enable 3 different OS types within the Software Manager, Windows, Mac, and Linux.

To enable “Windows” on the client you need to configure the scans, auto install and auto update settings and provide a schedule for updates if auto update is selected.


To enable “Linux” on the client you need to configure the scans, auto install and auto update settings and provide a schedule for updates if auto update is selected.


To enable “Mac” on the client you need to configure the scans, auto install and auto update settings and provide a schedule for updates if auto update is selected. You can use the Set Sudo menu to provide permissions for Mac deployment of HomeBrew package manager.


Check The Agent:
Select the agent you want to validate configurations on. This will load the agent tool view. Select each tab starting with the general tab. Each tab will have a settings menu with a (Enable / Disable) menu item. this will enable or disable the agent for the tool selected.


