Did you know: Scoping Content and Profiles

Did you know

Jamf School Informational Series:

Scoping Content and Profiles

Overview

The purpose of this informational series is to highlight features of the Jamf School Management System that the Jamf School community may not yet know about. This article covers how to scope a device group to specific profile(s) and content.

Scoping

Scoping is the act of determining the set of devices that will be assigned to specific profile(s) or content.

 

Concept

For efficiency’s sake, it is commonly necessary to scope the same profiles and/or content across a set of devices. This can be accomplished by creating device groups that allow Jamf School to deliver all relevant content and profiles to all the devices assigned to the same group. In order to reduce complexity, it is important to take time to plan out the logical set of device groups that will be used across an organization, defining as few device groups as possible. Otherwise, the number of device groups can quickly grow quite large, resulting in a complex system that is difficult to maintain and troubleshoot. You can find out more about setting up device groups in Support or in the Device Groups article.

In addition to defining as few device groups as possible, it is also important to be sure that no unnecessary content or settings are delivered to any device. The aim is to deliver the least amount of content and settings to each device while maintaining the device’s usability for the intended purpose or user. This keeps each device uncluttered in order to maximize the user experience.

There are two different types of device groups: static groups and smart groups.

  • Static device group: is a set of devices that have been added manually into a group by a systems administrator in Jamf School.
  • Smart device group: is a group defined by a systems administrator in Jamf School and then populated through the use of filtering criteria. A device is automatically included in the group if it meets the filtering criteria, and any content or profiles scoped to the group will be applied to the device. Similarly, a device is automatically excluded from a smart device group if the device no longer meets the filtering criteria, and any content or profiles associated with the group will eventually be removed from the device.

 

Considerations before Scoping

Adding a device group to the scope of a profile or piece of content should take place in the final stages of deployment testing. You should make sure the following is done before considering how to configure scopes (as all of these factors can influence the way you create a device group):

  1. Set up Students, Instructors, Classes, and Locations in ASM
  2. Determine and set up locations in Jamf School
  3. Map out how devices are going to be deployed (1 to 1, shared use, etc.) and assigned (authenticated enrollment, assigned to a cart, etc.)
  4. Read and understand how content will be acquired for the deployment
  5. Map out how system administrators will be created in Jamf School

 

Determining the device groups

Once these tasks are completed, it will give you a strong sense of how to define your device groups and the content and profiles to which each should be scoped. The best way to determine the set of device groups to define is by considering the following criteria:

  1. What is the physical location of the devices?
  2. What deployment model will be used for these devices?
  3. Who is the owner of the device?
  4. Is there similar content that needs to be delivered across a set of devices?
  5. If the devices are location-based, are there location-based admins that can create devicegroups and edit a location-based application’s or profile’s scope?

 

Adding content (Apps, Profiles, Documents)

When adding a piece of content (especially an app) to the scope of a device group, the following must be considered:

  1. How many devices will receive the content? Do I have enough licenses to cover all the devices?
  2. Is the profile or content necessary for all devices in the device group? Will it clutter the device(s) unnecessarily?
  3. Does the device already have a profile on it that will conflict with another profile that the device will be scoped to?
  4. Should the content automatically be installed to the devices, or should the users be given the ability to download the content on demand?
  5. Is there enough storage space on all devices within the group to receive the content?


How to: Set a Scope

When a profile is created or content is added, device group(s) should be added to the scope of the new profile or content. In the case of content, the timing for installation on the device must also be specified. Be sure that the device group(s) that you would like to include in a profile’s or content’s scope exist; if it does not, begin by creating the desired device group(s). (Creating device groups is covered in the Device Groups article.)


To add a device group to the scope of a profile :

  • In Jamf School, navigate to the profile in question by going to Profiles → Profiles and selecting the checkbox(es) next to the profile(s) that you want to add to the device group to. Then click the Edit Scope button.

AddDeviceGroupToProfile.jpg

Locations
Keep in mind that if a profile is created in a specific location, you can only add device groups in that location to the scope of that profile.
  • In the Edit Scope window that opens:
    • Select the desired device group(s) from the Scope menu.

EditScope_profile.jpg

Number of devices

The number in parenthesis indicates the total number of devices in that particular device group at the time.

  • In the menu below the Scope menu, choose whether to add the selected device group(s) to the current scope or whether to replace the existing scope. By adding the selected device group(s) to the current scope, any other device group(s) that are already part of the scope of the selected profile(s) will continue to exist in the scope. By replacing the existing scope, any other device group(s) already assigned to the scope will be removed and the device group(s) that are selected in the Scope menu will take their place in the scope of the selected profile(s).

EditScope_AddOrReplace.jpg

Smart Device Groups
Since adding a device group to a scope generally occurs before a majority of devices are handed out, the number of devices showing in that device group will appear low. However, as additional devices enter that group, they receive the profile they are scoped to receive.

To add a device group to the scope of one or more application(s):

  • Navigate to the application by going to Apps → Apps and selecting the checkbox(es) next to the application(s) that you want to add the group to. Then click the Edit Scope button.

AddContent.jpg

Licenses Remaining
The number of licenses remaining reflects the number of licenses that have not been assigned to devices. The number is the sum of the total number of devices included in the device groups in the scope minus the total number of licenses.
  • In the Edit Scope window that opens
  • Select the desired device group(s) from the Scope menu.

EditScope_apps.jpg

  • In the menu below the Scope menu, choose whether to add the selected device group(s) to the current scope or whether to replace the existing scope. By adding the selected device group(s) to the current scope, any other device group(s) that are already part of the scope of the selected content will continue to exist in the scope. By replacing the existing scope, any other device group(s) already assigned to the scope will be removed and the device group(s) that are selected in the Scope menu will take their place in the scope of the selected application.

EditScope_apps_AddOrReplace.jpg

  • In the Install Type menu, choose whether the content should install automatically or on-demand. On-demand installation will significantly reduce the load on the network when devices are added to the scope; however, users will be forced to install the application themselves before they can use it.

EditScope_apps_InstallType.jpg

Critical Apps
If there are apps that are critical for users to have on the first day or a soon as acquired, make sure to install those applications automatically. Non-critical apps or apps that are needed later can be set to on-demand and changed to automatic installation later if necessary.
  • In the VPP Assign Method menu, choose whether to assign the VPP license to the device or to the AppleID of the user. Except under special circumstances, choose to assign the VPP license to the device.

EditScope_apps_VPPAssignMethod.jpg

To add device groups to the scope of a document:

  • In Jamf School, navigate to the application in question by going to Documents → Documents and selecting the checkbox(es) next to the documents(s) that you want to add the device group to. Then click the Edit Scope button.

EditScope_Documents.jpg

  • In the Edit Scope window that opens, select the desired device group(s) from the Scope menu.

EditScope_docs_AddGroup.jpg

  • In the menu below the Scope menu, choose whether to add the selected device group(s) to the current scope or whether to replace the existing scope. By adding the selected device group(s) to the current scope, any other device group(s) that are already part of the scope of the selected content will continue to exist in the scope. By replacing the existing scope, any other device group(s) already assigned to the scope will be removed and the device group(s) that are selected in the Scope menu will take their place in the scope of the selected document.

EditScope_docs_AddOrReplace.jpg

  • In the Install Type menu, choose whether the content should install automatically or on-demand. On-demand installation will significantly reduce the load on the network when devices are added to the scope; however, users will be forced to install the document themselves before they can view it.

EditScope_docs_InstallType.jpg

Removing content or profile(s) from a device:

If a device is removed out of device group or no longer meets the filter criteria for smart device group, the profile or content will be removed. When that happens, different items will react in different ways. For instance, when a profile should no longer should be on a device, then the profile will be removed immediately. However, when the same occurs with an app, the removal will be deferred for two weeks, meaning the app will remain on the device for two weeks after the removal request is sent. This gives the user two weeks to back up their data. In addition, if an app is removed accidentally, the two week deferral allows time for the mistake to be corrected before the user and their data are affected. In the case of books purchased through ASM, the ownership of the license passes to the user. If a book is removed, the user can go to iBooks and reinstall the book.

Options

ZuluDesk Teacher

If a teacher has requested an application but it is unclear which devices the app is needed on or when the app is needed, the application can be made available to ZuluDesk Teacher. That allows a teacher to install the application when and where it’s needed. No scoping is necessary. You can find out more about ZuluDesk Teacher in Support or in the ZuluDesk Teacher article.

Adding an Individual Application to a Device

The last way to get an application, and the newest way, is to add it to the device individually. This can be accomplished by finding the individual device and adding the managed application to it.

To do this:

  • Go to Devices → Overview and search for the desired device. In the Search Results, click on the device name.

Location_AuthEnroll.jpg

  • In the Device Details screen that opens, click Managed Apps.

ManagedApps.jpg

  • Click the Add apps button.

ManagedApps_AddApps.jpg

  • In the Add Apps to Device window that opens, click the Add button in the row of each of the desired apps. When all desired apps have been selected, click the Close button

ManagedApps_AddAppsWindow.jpg

Have more questions? Submit a request

0 Comments

Article is closed for comments.