iOS MDM Sample Schedule

iOS MDM Sample Schedule

When enrolled in AirWatch, iOS devices are scheduled to send data samples to AirWatch based on the MDM Sample Schedule. This schedule is accessible through the AirWatch Admin Console by navigating to Settings -> Devices & Users -> Apple -> MDM Sample Schedule.  

95647427_-_MDM_sample_schedule.png

The information received from iOS devices is broken into multiple different sample types, which are shown in the preceding image.  For example, the Device Information Sample will return basic information about the device itself, such as the friendly name.  Likewise, the Application List Sample will return a list of all applications that are installed on the device, and Security Information Sample will return some basic security information, such as the type of passcode configured on the device.  

On SaaS environments, devices are scheduled to send an updated data sample every 12 hours, with the exception of the Device Information Sample, which is updated every 4 hours.  These values are chosen to maximize both the battery-life of each iOS device as well as the performance of the AirWatch environment itself.  In some cases, certain samples being sent from devices can be quite large, and updating them too frequently can impact the overall data usage of the device as well.  For example, the Certificate List Sample of a device that has many certificates installed will be significantly larger than a sample from a device with very few certificates installed.

Devices that have been found non-compliant of a configured policy will send device samples at a faster rate, as configured in the Non-Compliance Device Sample.  This will ensure a quicker turnaround of that device being marked compliant again after becoming in-line with all configured policies.

MDM Agent Sample

Of special note is the MDM Agent Sample.  This scheduled sample is used to update information that can only be gathered through the use of an AirWatch SDK-enabled application, such as the MDM Agent, Content Locker, Browser, or Inbox. Additionally, this will support internally developed applications that utilize the AirWatch SDK.  This type of information includes compromised status, GPS coordinates, as well as telecom data.  If an SDK-enabled application is active or in the background, this information will continue to update based on this frequency.  However, if the application has been force quit (by double-clicking the home button and swiping up) or it has never been launched since last rebooting, this information will not update until and SDK-enabled application has been opened.

App Refresh Interval

Additionally, AirWatch utilizes the Background App Refresh functionality available in iOS for automated sample updates.  A Minimum Refresh Interval is configurable in the AirWatch Admin Console by navigating to Settings -> Devices & Users -> Apple -> Apple iOS -> Agent Settings.  This setting is applicable to information gathered through SDK-enabled applications, as discussed in the previous section.

As long as a supported application is currently active or in the background, it will attempt to send a beacon back to AirWatch containing the relevant data samples at the specified interval.  However, iOS automatically leverages device usage patterns which may affect the overall app refresh rates.  As such, you may notice refresh intervals on some devices that do not exactly match the configured values.

95647427_-_refresh_interval.png

Have more questions? Submit a request

0 Comments

Article is closed for comments.