Category filter

Configuration profile to deploy certificates to Apple TV

A digital certificate acts as a security tool that authenticates clients or servers in a network and encrypts information for confidentiality. They are widely used to establish secure connections, prevent unauthorized access, and ensure data integrity. With Hexnode’s custom configuration profile feature, you can deploy certificates to your tvOS devices as per your needs and specifications.

Disclaimer:


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

Notes:


This configuration profile is supported on macOS 10.13 or later.

Deploy PEM certificate

You can refer to the following template to create a configuration profile to deploy a PEM certificate.

Notes:


The supported certificate file extensions are .crt, .cer, .pem, and .key.

Here is an example,

Deploy Root certificate

You can refer to the following template to create a configuration profile to deploy a root certificate.

Notes:


The supported certificate file extensions are .crt, .cer, and .pem.

Here is an example,

Distribute custom configuration profiles

  1. Log in to the Hexnode console.
  2. Navigate to Policies > New Policy.
  3. Provide a policy name and description (optional).
  4. Go to Apple TV > Deploy Custom Configuration > Configure > Choose File.
  5. Choose and upload the custom configuration profile from the device. If the file is already uploaded, you may select it from the list.
  6. Click OK.
  7. Navigate to Policy Targets.
  8. Select devices/device groups/users/user groups/domains to associate the policy. Click OK.
  9. Click Save.

What happens at the device end?

The certificate is deployed to the associated device. You can verify that the certificate has been deployed from Settings > General > Profiles & Device Management > Hexnode MDM > More Details on the device. It will be displayed under Certificates.

Notes:

  • 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.