Additional information on agent groups can be found here. Therefore, it is necessary to create the desired group on the manager before using the group parameter.
The agent enrollment will fail if a non-existent group is specified. This allows the manager to push configuration settings to a set of agents that belong to the same group.
An agent group is a collection of agents that would share the same configuration. GROUP1,GROUP2,GROUP3: This specifies the group(s) that the agent should be added to. When this is not specified, it defaults to the endpoint hostname. Some common enrollment parameters are below:ĮXAMPLE_NAME: This specifies the name the endpoint should be enrolled as. The enrollment dialog does not current display in 10.15 (Catalina).These agent enrollment parameters are optional and they provide the agent with specific information that should be used during enrollment.
When installed on a Mac running Mojave or later, the Mac Agent honors the Dark Mode settings where enabled on the computer. Our installer determines the correct package to install. If you use Migration Assistant to transfer from an Intel Mac to an Apple Silicon Mac, you must reinstall the RMM Agent to ensure the native version is used. We expect to have those ready in the near future, but the core Agent is ready today.įor technical reasons, the Agent is not a Universal 2 binary. Some add-on features, like AV, will run in Rosetta 2 compatibility. Mac Agent support for Apple M1 processorsīeginning with Mac Agent v3.6.0 RC and macOS 11 Big Sur, there is native support for Macs with new Apple M1 processors. If you no longer require the automatic deployment of these Automated Tasks for your account, please contact support.
Visit the Apple Device Management section for further information.ĭepending on your company's security policy, a firewall or other web monitoring software may be deployed to filter internet connections to avoid potential Agent communication issues. Once the certificate association is in place, we will prompt the end-user to enroll in our Mac Device Management service and apply the related profile when the Agent updates to version 3.4.0 RC or later. To use this functionality, you must first request an Apple Push Notification certificate and upload this to your Dashboard. To reduce the volume of notification displayed to the end-user from our software and ensure all our installed applications have the required permissions, from Mac Monitoring Agent 3.4.0 RC we utilize Apple’s Mobile Device Management (MDM) framework.
Monitoring Agent Push: Push a Monitoring Agent to an unmonitored device when it is discovered as part of an Network Discovery scan.
A Remote Worker download is also available through the Add Device option of the Graphical Dashboard.