Introduction
This article will walk you through installing the endpoint agent via Microsoft Intune and has multiple steps.
Table of contents
Overview
When deploying the installer package file (.pkg), the license needs to be distributed prior to installing the endpoint agent using a device configuration profile.
Additionally, you’ll need two other MDM configuration profiles: one for explicitly allowing the system extension, and one to provide it with the TCC Full Disk Access permission.
Refer to the official Jamf documentation for an in-depth workflow.
For convenience, the following sample configuration profiles (.mobileconfig) have been included with the endpoint agent installer bundle (.zip package):
- .\mdm\macos\generic\covalence_license.mobileconfig
- .\mdm\macos\generic\covalence_sysext.mobileconfig
- .\mdm\macos\generic\convalence_ttc.mobileconfig
Deploying the Endpoint Agent via Jamf
Add the Covalence License
Use the following manuals steps. A Jamf-specific covalence_license.mobileconfig can alternatively be provided.
- Go to Configuration Profiles.
- Select New.
- Set the Name to Covalence macOS License.
- Go to Applications & Custom Settings > Upload.
- At the Upload screen press the Add button and:
- Set Preference Domain to com.fieldeffect.covalence
- Set the Property List to where [license] is replaced with your license string:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>License</key>
<string>[license]</string>
</dict>
</plist>
Press the Save button in the bottom right corner.
Add explicit system extension approval
If there is an issue with the covalence_sysext.mobileconfig not uploading properly, use the following manual steps in the interim:
- Go to Configuration Profiles.
- Select New.
- Set the Name to Covalence macOS System Extensions.
- Go to System Extensions.
- At the Configure System Extensions screen click the Configure button.
- Unselect the Allow users to approve system extensions if you don't want users installing agents.
- Under Allowed Team IDs and System Extensions:
- Set the Display Name to Field Effect Software Inc.
- Set the System Extension Types to Allowed System Extensions.
- Set the Team Identifier to KSBE8M6M6F.
- Under ALLOWED SYSTEM EXTENSIONS click the Add button and:
- Set the empty field to com.fieldeffect.covalence.esext
- Press the Save on the adjacent line
Press the Save button in the bottom right corner.
Add explicit TCC approvals
- Go to Configuration Profiles.
- Select New.
- Set the Name to Covalence macOS Privacy Policies.
- Go to Privacy Preferences Policy Control.
- At the Configure Privacy Preferences Policy Control screen press the Configure button.
- If an App Access group doesn't exist press the “+” button to add one.
- Under App Access:
- Set the Identifier to com.fieldeffect.covalence
- Set the Identifier Type to Bundle ID
- Set the Code Requirement to:
identifier "com.fieldeffect.covalence" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] and certificate leaf[field.1.2.840.113635.100.6.1.13] and certificate leaf[subject.OU] = KSBE8M6M6F
- Unselect Validate the Static Code Requirement if selected.
- Click the Add button adjacent to APP OR SERVICE.
- Under APP OR SERVICE select SystemPolicyAllFiles.
- Under ACCESS select Allow.
- Click the Save button on the adjacent line.
- Add another App Access group.
- Set the Identifier to com.fieldeffect.covalence.esext.
- Set the Identifier Type to Bundle ID.
- Set the Code Requirement to:
identifier "com.fieldeffect.covalence.esext" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] and certificate leaf[field.1.2.840.113635.100.6.1.13] and certificate leaf[subject.OU] = KSBE8M6M6F
- Unselect Validate the Static Code Requirement if selected.
- Click the Add button adjacent to APP OR SERVICE.
- Under APP OR SERVICE select SystemPolicyAllFiles.
- Under ACCESS select Allow.
- Click the Save button on the adjacent line.
- Press the Save button in the bottom right corner.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article