Skip to content
  • There are no suggestions because the search field is empty.

Deploy Share911 Desktop with Jamf Pro

Deploy Share911 Desktop to your organization's Macs with Jamf Pro, using the Share911 installer package. Share911 Desktop needs macOS 13 Ventura or later.

Download the Share911 installer package (.pkg). For what the package does on each Mac, see Deploy Share911 Desktop with an MDM.

Settings you can push

Push these with a configuration profile. In Jamf Pro: Configuration Profiles -> Application & Custom Settings -> Upload, with the preference domain com.share911.desktop.

  • Turn off automatic updates. Without this setting Share911 updates itself, and because the package installs it for all users, macOS asks for an administrator password each time it does. To deliver new versions through your MDM instead, push:

    <dict>
    <key>AutoUpdate</key>
    <false/>
    </dict>

    Push the profile before the package: Share911 reads the setting when it starts. To confirm it took effect, the Share911 menu in the menu bar shows "Updates are managed by your organization". Versions of Share911 released before this setting existed ignore it.

  • Do not open Share911 after the install, when it was not already running. Share911 still starts at the next login, and an app that was running before the install is still reopened. Push:

    <dict>
    <key>LaunchAfterInstall</key>
    <false/>
    </dict>
  • Keep Share911 from being switched off at login, and hide the "Background Items Added" notification. Before the package, push a Managed Login Items payload with a rule of type Team Identifier and value 4BYFGX4S73, or of type Label and value com.share911.desktop.agent.

Checking which version is installed

Read the app's own version, for example in a Jamf extension attribute:

defaults read /Applications/Share911.app/Contents/Info.plist CFBundleShortVersionString

The package receipt (pkgutil --pkg-info com.share911.desktop) shows the last package installed, which is not always the version of the app: Share911 may have updated itself, or a package older than the installed app changed nothing.

Other copies of Share911

The package does not touch copies outside the Applications folder (for example in a user's Downloads or ~/Applications folder). Those copies keep updating themselves, so remove them with your MDM. To list every copy on a Mac:

mdfind "kMDItemCFBundleIdentifier == 'com.share911.desktop'"

Opening Share911 from a policy script

To open Share911 for the logged-in user from a policy script (it does nothing when nobody is logged in or Share911 is already running):

user=$(stat -f %Su /dev/console)
case "$user" in
'' | root | loginwindow | _mbsetupuser) ;;
*) pgrep -x -u "$user" Share911 >/dev/null ||
launchctl asuser "$(id -u "$user")" sudo -u "$user" open -g /Applications/Share911.app ;;
esac

Removing Share911

To remove Share911 from Macs with your MDM, use the script in Remove Share911 Desktop from a Mac.