Category filter

How to deploy a custom configuration profile to enforce conference room display on tvOS devices

When managing a fleet of Apple TV devices, it’s necessary to enforce certain configurations and policies to ensure seamless and secure use of the devices. One such policy is the conference display mode, which sets the display to a specific layout during meetings and presentations. Easily enable the conference room display on your Apple TV with a customized message by deploying a custom configuration profile through the Deploy Custom Configuration feature provided by Hexnode UEM.


The sample configuration profile provided below is adapted from third-party open-source sites.

Configuration profile to enforce Conference room display on tvOS devices


The Apple TV should be running on tvOS12.0 or later for the configuration profile to work.

Type the message that you wish to show on the tvOS device by replacing the “Enter your message here” string in the code.

Associating Policies with tvOS devices

To enforce Conference room display on tvOS devices,

  1. Log in to Hexnode UEM.
  2. Navigate to Policies > New Policy.
  3. Provide a policy name and description.
  4. Go to Apple TV > Deploy Custom Configuration.
  5. Click on Configure > Choose File. You may choose the configuration profiles from the device or select profiles which are already added to the portal.
  6. Click OK.
  7. Go to Policy Targets.
  8. Choose the target devices and click OK. You can also choose to associate the policy with device groups, users, user groups, or domains from the left pane of the Policy Targets tab.
  9. Click Save.

If the policy is saved,

  1. Choose the desired policy from the Policies tab.
  2. Click on the Manage drop-down and select Associate Targets.
  3. Choose the target devices, device groups, users, user groups, or domains and click Associate.

  • 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