Distributing via MDM Tools Last updated June 2, 2026 · Desktop Connect

Many Mac environments use Mobile Device Management (MDM) tools like Jamf Pro or Addigy to manage applications and settings. Desktop Connect can be distributed via these tools.

Supported MDM Tools

Jamf Pro: Fully supported. See Deploying via Jamf Pro for detailed steps. (Note: Jamf Now is NOT supported — Jamf Pro required)

Addigy: Supported. Use Addigy's native package distribution and configuration profile features.

Other MDM tools: If your MDM tool supports macOS app distribution via PKG files, it can likely deploy Desktop Connect. Contact Prodoscore support for specific guidance.

Key Considerations for Mac MDM Deployment

Apple's Permissions Model: macOS restricts certain capabilities (Accessibility, Screen Recording, etc.) and requires explicit user approval or MDM pre-approval. Key points:

  • MDM tools CAN install the application without user interaction
  • MDM tools CANNOT automatically grant all permissions — Apple's security model prevents that
  • If not using configuration profiles to pre-approve, users must manually grant permissions in System Settings
  • Configuration profiles (provided by Prodoscore) can pre-approve permissions silently, eliminating user prompts

Installation Locations (Mac)

When deployed via MDM, Desktop Connect installs to:

  • /Applications/MyZenV2.app — Standard mode
  • /usr/local/zs/zs.app — Stealth mode
  • /library/launchagents/launcher.ai.prodoscore.myzenv2.plist — LaunchAgent file (auto-starts the agent)

Bundle ID: com.prodoscore.com.myzenv2

The LaunchAgent file ensures Desktop Connect starts automatically each time the user logs in.

Permissions Pre-Approval via Configuration Profiles

To avoid user prompts during deployment, Prodoscore provides two configuration profiles. Contact support@prodoscore.com to request:

Profile 1: Accessibility Permission

Pre-grants Accessibility access for MyZenV2. Without this, users see a prompt: "System Preferences > Security & Privacy > Accessibility > enable MyZenV2".

Profile 2: Screen Recording Permission

Pre-grants Screen Recording access (required for Screenshots feature if enabled). Without this, users see a prompt: "System Preferences > Privacy & Security > Screen Recording > enable MyZenV2".

Deploy both profiles BEFORE installing Desktop Connect. After profiles sync (typically 5-15 minutes), permissions are pre-approved and no user action is needed.

Recommended MDM Deployment Workflow

1 Request configuration profiles from Prodoscore support

2 Upload and deploy configuration profiles via your MDM tool to target device groups

3 Wait 15-30 minutes for profiles to sync to devices

4 Download Desktop Connect PKG file from Prodoscore admin portal (do not rename)

5 Upload PKG to your MDM distribution point

6 Create deployment policy specifying the PKG and target device group

7 Deploy with "Required" or "Available" based on your needs

8 Monitor deployment status in your MDM tool

Troubleshooting MDM Deployments

Installation fails: Ensure the PKG filename has not been modified (the filename contains your license token). Verify the target device group is correct and devices are actually managed by your MDM tool.
Users see permission prompts after installation: The configuration profiles may not have deployed before the app. Configuration profiles can take 15+ minutes to sync. Redeploy the profiles or have users manually grant permissions in System Settings.

For detailed steps for your specific MDM tool, refer to that tool's documentation or contact Prodoscore support at support@prodoscore.com for assistance.