Skip to main content

Background Service Management

Background Service Management allows IT administrators to configure applications and background services that should continue running in the background on managed macOS devices and cannot be quit by end users, including users with administrator privileges.

Administrators can configure rules to identify background services using Bundle Identifier, Bundle Identifier Prefix, Label, or Label Prefix. An optional Team Identifier can also be specified to further refine the matching criteria.

note
  • Supported OS Version: macOS 13.0 or later
  • Supported Enrollment Type: Device Enrollment and Automated Device Enrollment
  • Applicable Channel: Device Channel

Steps to Configure Background Service Management Profile​

  1. On the SureMDM Web Console, navigate to Profiles > macOS > Add > Select Device Enrollment and Automated Device Enrollment Type > User Experience & Personalization > Background Service Management > Configure.

  2. Enter a Profile Name and click Configure under Background Service Management.

  3. In the Background Service Management screen, click Add to configure a background service rule.

  4. In the Add App popup, configure the following settings:

    SettingDescription
    Rule TypeSelect the criteria to identify the background service. Available options are:

    - Bundle Identifier: Identifies a background service using its application's Bundle Identifier.
    - Bundle Identifier Prefix: Identifies background services using a specified Bundle Identifier prefix.
    - Label: Identifies a background service using its label.
    - Label Prefix: Identifies background services using a specified label prefix.
    App NameSelect an application from the list of managed applications available in SureMDM. This field is displayed only when Bundle Identifier is selected as the Rule Type. Select Add Custom App to configure an application that is not available in the managed application list. Applicable only if Bundle Identifier is selected as the Rule Type.
    Rule ValueEnter the value corresponding to the selected Rule Type. When a managed application is selected, its Bundle Identifier is automatically populated. For a custom application, manually enter the application's Bundle Identifier. For Bundle Identifier Prefix, Label, and Label Prefix, enter the corresponding value manually.
    Team IdentifierOptionally enter the application's Team Identifier to further refine the matching criteria. A Team Identifier is a 10-character alphanumeric value that identifies the application developer.
**Available Rule Types**

The following rule types are available for identifying background services:

| **Rule Type** | **Description** |
|---|---|
| **Bundle Identifier** | Identifies a background service using the application's Bundle Identifier. For managed applications, the Bundle Identifier is automatically populated when an application is selected. For custom applications, administrators must manually enter the Bundle Identifier. |
| **Bundle Identifier Prefix** | Enter the Bundle Identifier Prefix value. |
| **Label** | Enter the label value. |
| **Label Prefix** | Enter the label prefix value. |
  1. Click Add. The configured background service rule will be added to the table.

  2. Repeat the above steps to add additional background service rules, if required.

  3. Click Save.

    The newly created profile will be listed in the Profiles section.

  4. Go back to the Home tab and select the macOS device(s) or group(s).

  5. Click Apply to launch the Apply Job/Profile To Device prompt.

  6. In the Apply Job/Profile To Device prompt, select the created profile and click Apply.

[Note]
  • The configured rules apply only to applications that support background activity on macOS. If an application does not support background activity, configuring it in this payload will have no effect on the device after deployment.
  • When a Team Identifier is specified, it is used as an additional matching criterion along with the configured Rule Type and Rule Value.

💬 Help us improve this documentation

Was this information useful?

Your feedback helps us keep our documentation accurate, up to date, and useful.