Category filter

Configuration profile to delay software update on tvOS devices

The doc helps administration delay software updates on tvOS devices with the help of a configuration profile.

Device manufacturers regularly release OS updates to support new features, fix bugs, or as security patches, which are usually automatically installed on devices. But, there may be situations where organizations want to delay the updates on managed devices for various reasons. For instance, organizations might prefer to wait for a more convenient day to install updates to ensure the device remains functional while users work on crucial projects. Or, the organization would want to ensure the compatibility of the updates in the workplace before they are deployed widely.

While there are different ways to delay software updates, the method described here uses a custom configuration profile to delay software updates on tvOS devices to a specified number of days. Hexnode’s Deploy Custom Configuration feature allows admins to push configuration profiles to the user’s Apple TV device.


The sample configuration profiles provided below are created using various profile creator applications.


This configuration profile is supported on devices running tvOS 12.2 and above.

Here is a .plist file to delay software updates on your tvOS devices:

The default value to delay the software updates in the above configuration profile is 30 days. The software updates can be delayed for up to 90 days from the date of their release. You can specify the number of days to delay the update between 1 and 90 by changing the integer value specified for the ‘enforcedSoftwareUpdateDelay’ key.


  • To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
  • Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • Use wildcards to fetch key values from the portal.
  • It is recommended to manually validate the configuration profile on a system before executing it in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository