Introduction
The Field Effect endpoint agent for macOS can be installed using any MDM that can push an installer package (.pkg) and custom configuration profiles (.mobileconfig), such as Jamf Pro, Addigy, JumpCloud, Kandji, Mosyle or Microsoft Intune.
The process is the generally the same for every MDM on every MDM; you deliver a set of configuration profiles, then install the agent package. The only real difference are the interaces and terminology used by the different tools.
This article uses Jamf Pro as a step-by-step example. If you use a different MDM, follow the same steps using its equivalent settings.
Note on Deployment Order:
Deploy the configuration profiles, especially the license profile, before you install the agent package.
What every MDM deployment needs
You will need to provide the following within your MDM system:
| Profile / item | Purpose | Sample file | Required? |
|---|---|---|---|
| License | Delivers your license as a managed preference for the com.fieldeffect.covalence domain | covalence_license.mobileconfig | Required |
| System Extensions | Allows Team ID KSBE8M6M6F and the com.fieldeffect.covalence.esext, .hbns and .dnsproxy extensions | covalence_sysext.mobileconfig | Required |
| Privacy (TCC) | Grants Full Disk Access ( SystemPolicyAllFiles) to com.fieldeffect.covalence and com.fieldeffect.covalence.esext | covalence_tcc.mobileconfig | Required |
| Host-Based Network Sensor (HBNS) | Network Content Filter payload for HBNS | Field-Effect-HBNS.mobileconfig | Required (Agent 4.1+) |
| DNS Proxy | Enables Roaming DNS Firewall, DNS telemetry and DNS Firewall reporting | Field-Effect-DNS-Proxy.mobileconfig | Optional |
| Agent installer (.pkg) | Installs the endpoint agent | n/a | Required (deploy last) |
Sample configuration profiles
For convenience, the endpoint agent installer bundle (.zip package) includes the following sample configuration profiles (.mobileconfig):
.\mdm\macos\generic\covalence_license.mobileconfig.\mdm\macos\generic\covalence_sysext.mobileconfig.\mdm\macos\generic\covalence_tcc.mobileconfig
These profiles don't depend on any specific MDM. On most platforms, the fastest approach is to upload them as custom configuration profiles.
Using Another MDM
The profiles described above are required for every MDM. To deploy the installer with a platform other than Jamf:
- Upload each sample .mobileconfig as a custom configuration profile.
- Scope the profiles to the target Macs and confirm they've installed.
- Deploy the agent .pkg.
For more detailes surrounding Microsoft Intune, see Intune Agent Installation: macOS.
Example: Deploying the Endpoint Agent with Jamf Pro
Refer to the official Jamf documentation for an in-depth workflow.
Step 1: Add the Covalence License
Every MDM: Deliver the license as a managed preference (custom settings) for the com.fieldeffect.covalence domain.
In Jamf: Use the following manual steps. Alternatively, Field Effect can provide a Jamf-specific covalence_license.mobileconfig.
- Go to Computers > Configuration Profiles.
- Select New.
- Set the Name to
Covalence macOS License. - Go to Applications & Custom Settings > Upload.
- At the Upload screen press the Addbutton and:
- Set Preference Domain to
com.fieldeffect.covalence - Set the Property List as follows, replacing
[license]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>
- Set Preference Domain to
- Press the Save button in the bottom right corner.
Step 2: Approve the System Extensions
Every MDM: Allow the Field Effect Team ID KSBE8M6M6F and its system extensions.
In Jamf: Upload covalence_sysext.mobileconfig.
If it doesn't upload properly, use the following manual steps in the meantime:
- Go to Computers > Configuration Profiles.
- Select New or select your existing Covalence macOS System Extensions profile.
- Set the Name to
Covalence macOS System Extensions. - Go to System Extensions.
- At the Configure System Extensions screen click the Configure button.
- Deselect 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 Addbutton and ensure the following system extensions are approved:
com.fieldeffect.covalence.esextcom.fieldeffect.covalence.hbnscom.fieldeffect.covalence.dnsproxy
- Set the Display Name to
- Press the Save button in the bottom right corner and distribute the update.
Step 3: Add Explicit TCC Approvals
Every MDM: Use a Privacy Preferences Policy Control (PPPC) payload to grant Full Disk Access (SystemPolicyAllFiles) to both Field Effect bundle IDs.
In Jamf:
- Go to Computers > 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
- Deselect 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.
- Set the Identifier to
- 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 - Deselect 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.
- Set the Identifier to
- Press the Save button in the bottom right corner.
Step 4: Add the Host-Based Network Sensor (HBNS) Profile
Every MDM: Agent 4.1 introduces the Host-Based Network Sensor (HBNS), which needs its own Network Content Filter payload. Upload the supplied profile at the device or computer level.
In Jamf:
- Go to Computers > Configuration Profiles.
- Select Upload.
- Upload the supplied
Field-Effect-HBNS.mobileconfig. - Set the profile level to Computer level.
- Assign the profile to devices running the Field Effect agent.
The HBNS profile configures the network content filter used by the Host-Based Network Sensor.
Step 5: Add the DNS Proxy Profile (Optional)
Every MDM: Deploy this profile only if you intend to use:
- Roaming DNS Firewall
- DNS telemetry
- DNS Firewall reporting
If another DNS filtering product already installs a DNS Proxy (for example Cisco Umbrella, DNSFilter, Cloudflare Gateway or Zscaler), don't deploy the Field Effect DNS Proxy profile.
In Jamf:
- Go to Computers > Configuration Profiles.
- Select Upload.
- Upload the supplied
Field-Effect-DNS-Proxy.mobileconfig. - Set the profile level to Computer level.
- Assign the profile to devices using the Field Effect DNS Firewall.
Use the supplied .mobileconfig file instead of building a DNS Proxy payload by hand in Jamf or any other MDM. The file includes the required ProviderDesignatedRequirement setting, which Jamf's UI and many other MDM consoles don't expose.
Step 6: Deploy the Agent Package
Every MDM: Once the profiles above are installed on target devices, deploy the endpoint agent .pkg.
In Jamf: Upload the .pkg under Settings > Computer Management > Packages, then deploy it to the same devices with a policy.
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