Category filter

Custom configuration profile to set date and time automatically on tvOS devices

Accurate date and time settings are critical to the effective operation of any device, including Apple TV. Setting the wrong date and time on a tvOS device might result in incorrect content availability (updates, apps, streaming services), app functionality issues, or compromise security features like certificate validation and secure connections. It can also cause syncing issues with other devices, such as iPhones, iPads, or Macs, disrupting features like AirPlay, HomeKit, and iCloud syncing. To ensure that the tvOS device sets the date and time automatically based on its current location, users can manually enable the ‘Set Automatically’ feature under Date & Time settings. As an administrator, you can also use a custom configuration profile to achieve the same. Hexnode allows IT admins to remotely deploy this configuration profile to multiple tvOS devices enrolled in the UEM via the Deploy Custom Configuration feature.

Note:


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

Disclaimer:


The configuration profile provided below is adapted from a third-party open-source site.

Configuration profile to set date and time automatically

Set the value of the forceAutomaticDateAndTime key to true in the configuration profile to set the date and time of the tvOS device automatically based on the current location.

What happens at the device end?

Once the policy and custom configuration are associated, you can navigate to Settings > General > DATE AND TIME to see the Set Automatically feature turned on. The feature can no longer be manually disabled by the user.

Notes:

  • The Apple TV’s time zone is automatically updated depending on location information provided by the Wi-Fi network to which it is connected or by location services.
  • 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 tvOS devices.
  • Ensure that you do not associate conflicting configurations with the devices.
  • It is recommended to manually validate the configuration profile execution on a system before executing the action in bulk.
  • Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

  • Configuration Profile Repository