Deploying ProdCom with an MDM

IT teams can install ProdCom on the Macs they manage with an MDM such as Mosyle, Jamf Pro, Kandji or Microsoft Intune. You add two things to your MDM, the ProdCom installer package and one deployment profile, and assign both to your Macs. Each Mac then registers itself with your ProdCom organization and uses one of its device seats. Nobody on those Macs needs to sign in or enter a license.

Before You Start

MDM is available through our Professional Features Preview, subject to approval. In your account's MDM section, choose Request Early Access and tell us your approximate device count and intended use. ProdCom will review your organization and contact you to discuss your needs; submitting a request does not enable access automatically.

Complimentary preview access is temporary and does not establish a permanent free entitlement. Professional capabilities are expected to require a paid subscription in a future release, with pricing and timing communicated in advance. You will never be automatically charged or upgraded without your agreement.

  • MDM early access enabled for your organization by ProdCom.
  • A ProdCom organization with device seats, bought at account.prodcom.io under Billing.
  • You are the organization's owner or an administrator, or a member who can manage devices.
  • An MDM that can install a package and deploy a custom configuration profile.

1. Download the ProdCom Package

In your account, open Devices and, under MDM enrollment, choose Download ProdCom package (.pkg). MDMs that install from a link can use https://api.prodcom.io/functions/v1/direct_download?platform=macos&format=pkg, which always serves the latest release. The package installs /Applications/ProdCom.app and updates an existing copy in place.

2. Create a Deployment Profile

  1. In Devices, under MDM enrollment, choose Create deployment profile.
  2. Give it a name, such as All Macs or Broadcast suite. You can also set a device limit so this profile never registers more Macs than you expect.
  3. Choose Create and download profile. Your browser saves a .mobileconfig file.

Keep the file safe. It can only be downloaded when it is created, because ProdCom stores only a fingerprint of the key inside it. If you lose it, revoke the profile in Devices and create another. One profile serves every Mac: you do not need a new one per Mac.

3. Add Both to Your MDM

Upload the configuration profile unchanged, as a custom profile. Do not rebuild it from your MDM's settings forms, and turn off any option that substitutes variables into it.

Mosyle

  1. Open Management and choose Install PKG. Add a profile, upload the ProdCom package, assign your Macs or device groups and save.
  2. Open Certificates / Custom Profiles and choose New. Name it ProdCom, upload the .mobileconfig file as the configuration file, leave Enable Variables for this profile unchecked, keep the profile scope at System, assign the same Macs and save.
  3. Optional: to register Macs before anyone opens ProdCom, add the script below under Custom Commands, assign it to the same Macs and save. Its output appears under View results.

Jamf Pro

  1. Upload the package under Settings > Computer Management > Packages, then create a policy that installs it, scoped to your Macs.
  2. Under Computers > Configuration Profiles, choose Upload, select the .mobileconfig file, keep it at computer level and scope it to the same Macs.
  3. Optional: add the script below to a policy with a login trigger to register Macs before anyone opens ProdCom.

Other MDMs

Install the package however your MDM deploys apps, and deploy the .mobileconfig file as a custom macOS configuration profile at the device (system) level.

4. Macs Register Themselves

A Mac with ProdCom and the profile registers the first time someone opens ProdCom. Registered Macs appear under Devices with their computer name and the macOS user, such as Studio Mac (crew), so name your Macs in your MDM (or in System Settings > General > Sharing) before ProdCom first opens.

To register a Mac before anyone opens ProdCom, run this script from your MDM. Someone must be logged in to the Mac, because ProdCom keeps its registration in that person's keychain:

#!/bin/bash
user=$(/usr/bin/stat -f%Su /dev/console)
case "$user" in
  "" | root | _mbsetupuser | loginwindow)
    echo "No one is logged in yet; run again after login"; exit 1 ;;
esac
uid=$(/usr/bin/id -u "$user")
/bin/launchctl asuser "$uid" /usr/bin/sudo -u "$user" \
  /Applications/ProdCom.app/Contents/MacOS/ProdCom --managed-register

It prints one line of JSON. "offline_authorized": true means the Mac is registered and ready. device_busy means ProdCom is open; it registers on its own in that case.

Each macOS user account on a shared Mac registers separately and uses its own seat.

When You Run Out of Seats

If no seat is free when a Mac tries to register, it appears under Waiting for a seat in Devices. In ProdCom, Settings > Account tells the person at that Mac that it is waiting. The Mac retries every 15 minutes while ProdCom is open, and each time it starts. Add seats under Billing or remove Macs you no longer use, and waiting Macs register on their next try. A Mac also waits when its profile's device limit is reached.

Updates

ProdCom deployed with a deployment profile never checks for or offers updates; its Settings explain that your organization manages them. Deploy new versions through your MDM. The download link above always serves the latest release.

Microphone and Speech Recognition

macOS asks each person to allow ProdCom's microphone and speech recognition access the first time it listens. An MDM privacy profile cannot grant microphone access, so plan for that approval at first use.

Removing a Mac

Unassign the ProdCom profile from the Mac in your MDM, then remove the Mac under Devices to free its seat. It stops working the next time ProdCom reaches your account, or once its offline grant ends. Uninstalling ProdCom alone does not free the seat.

Keeping the Profile Secure

The profile contains your organization's deployment key. Anyone who can read the profile on a managed Mac could use it to register other Macs, up to your free seats or the profile's device limit. Every registered Mac appears under Devices. If you see a Mac you don't recognize, remove it and revoke the profile: revoking stops new registrations, while Macs already registered keep working until you remove them. Then create a new profile and replace it in your MDM.

A profile acts for the person who created it. If that person leaves the organization or can no longer manage devices, Devices marks the profile Inactive. Create a new one and replace it in your MDM; Macs already registered are not affected.

One Mac at a Time

If your MDM cannot keep one profile for every Mac, use Enroll one Mac with a code in Devices instead. You download a profile for one Mac along with a single-use code, deploy the profile and pass the code to ProdCom --managed-enroll on that Mac within 10 minutes. Contact us for the script.

Troubleshooting

What you see What to do
The Mac is not under Devices Open ProdCom on it once, or run the script above. Check the profile is installed with /Applications/ProdCom.app/Contents/MacOS/ProdCom --managed-settings, which should show "configured": true.
The Mac is under Waiting for a seat Add seats or remove unused Macs. It registers on its next try.
The profile is marked Inactive Create a new deployment profile and replace the old one in your MDM.
The script prints managed_settings_missing The profile has not reached that Mac yet. Check its assignment in your MDM.

Need Help?

Contact support@prodcom.io with your MDM's name and what you see, and we'll help you finish the deployment.