What is Items suppose to control in the InstalledApplicationListCommand? Items [string] Possible values: AdHocCodeSigned, AppStoreVendable, BetaApp, BundleSize, DeviceBasedVPP, DynamicSize, ExternalVersionIdentifier, HasUpdateAvailable, Identifier, Installing, IsValidated, Name, ShortVersion, Version The results are the same response https://developer.apple.com/documentation/devicemanagement/installedapplicationlistresponse/installedapplicationlistitem regardless of what strings in included in the Items string of the request.

What is the format of the Timezone in the new SettingsCommand.Command.Settings.TimeZone setting? The current docs are vague. TimeZone string https://developer.apple.com/documentation/devicemanagement/settingscommand/command/settings/timezone?changes=latest_minor Would it be the same as the setting in the TimeServer profile setting timeZone string The time zone path location string in /usr/share/zoneinfo/; for example, America/Denver or Zulu.  https://developer.apple.com/documentation/devicemanagement/timeserver?changes=latest_minor or a different format entirely? Speaking of which if a Timeserver profile is applied and the new SettingsCommand is sent with a different Timezone which takes precedence or will that be an error?

Hi - Is the new IOS 14 restrictions allowAppClips for all devices? The docs at https://developer.apple.com/documentation/devicemanagement/restrictions state allowAppClips boolean If false, prevents a user from adding any App Clips, and removes any existing App Clips on the device. Available in iOS 14.0 and later. Default: true BUT the latest Apple Configurator beta has text that indicates this restriction is only for IOS 14 and later supervised devices. Which is correct? Apple Configurator or the docs?

Hi Our testing of the new DisableAssociationMACRandomizatio n attribute on the Wi-Fi payload for IOS 14 devices shows that when the attribute is set to false, the device will report the actual value of the MAC address to the router, but we were surprised to see that the end user can enable Private address from the device for that Wi-Fi. Doesn't this defeat the purpose of the MDM requesting that the DisableAssociationMACRandomization be enabled? Is this the correct behavior? Our mutual customers who use products like Cisco ICE need the actual MAC address which I assume is why Apple provided the new attribute DisableAssociationMACRandomization to disable the randomization feature in the first place. But if the end user can just reenable it themselves this new attribute is only marginally helpful. Are there plans to allow MDM to lock this setting?