Agent MacOS MDM deployment

InsightVM
1

Hi,

Im trying to deploy Rapid7 Insight Agent v4.0.12.14 via our MDM (WorkspaceOne) to the enrolled MacOS devices. There is a tool that generated the .plist file for this .pkg. The problem here is that the generated XML file feels like its missing alot of choices, comparing to other pkg files we have uploaded to the MDM. It doesnt include any choice attributes, we are just adding the token key.

Also, running the .pkg on the MacOS gets blocked because Apple cannot verify it. So this is also a blocker. We are downloading the pkg file from our Insight Platform home instance so should be signed and verified.

So, my question here is, has anyone successfully generated a .plist file for the Insight Agent for they MDM for remote deployment? Or in general, successfully enrolled MacOS endpoints remotely?
Any help would be appreciated.

Thanks,

2

Hi,

We had a lot of trouble trying to deploy the agent on macOS too - it seems so much trickier than it needs to be! We did manage it through our MDM eventually though with a lot of trial and error.

For doing a manual install use these instructions - Mac Installation | Insight Agent Documentation
You must use the commands to run the pkg file then activate it using the .sh script. Once it’s installed you have to give it Full Disk Access permissions too (this applies to the MDM install too).

For an MDM install I’m afraid I probably won’t be able to be as much help as I haven’t used WorkspaceOne, but in SimpleMDM we added custom pkginfo that we generated from the following command (run this in the same directory as your installer):
makepkginfo --name=rapid7-insight-agent-4.0.12.14-1.arm64 --displayname=Rapid7 --pkgvers=4.0.12.14 --unattended-install --destinationpath=/ rapid7-insight-agent-4.0.12.14-1.arm64.pkg
(You’ll need to sub in your version number there obviously!)

Then we set a post install script to run the configure_agent.sh script:
#!/bin/bash
/opt/rapid7/ir_agent/components/insight_agent/4.0.9.38/configure_agent.sh --token ADD YOUR TOKEN HERE --start

Fingers crossed that helps!

1 Like
3

Hi, thanks!
This was indeed the solution. The plist being generated by the mdm software was wrong and the command fixed it.
Thank you for your help :slight_smile:

1 Like
4

Hello! Came across your post and also having the same issues with MDM deployment with Mosyle. Just to confirm, did you install the manual installer first, and then grab everything and transfer that information to Mosyle and application push? Any help would be appreciated!

Thank you!

5

Hey, not sure what you mean with install the manual installer first, but what I did is add the installer to the MDM and the post install script that includes the token along with the plist generated from the command
makepkginfo --name=rapid7-insight-agent-4.0.12.14-1.arm64 --displayname=Rapid7 --pkgvers=4.0.12.14 --unattended-install --destinationpath=/ rapid7-insight-agent-4.0.12.14-1.arm64.pkg
then deploying this package on an endpoint just installs it and it connects to our insight instance.