Skip to content
English
  • There are no suggestions because the search field is empty.

Distributing Kitcast builds using MDM Providers

This guide will walk you through setting up Mobile Device Management (MDM) for the first time with Kitcast V2, using platforms like JAMF. We'll cover various scenarios, provide examples, and ensure you have all the information needed for a smooth setup.

Table of Contents

  1. Prerequisites
  2. Understanding Key Terms
  3. Step 1: Install the Kitcast tvOS App
  4. Step 2: Retrieve Your Secret Key and Configuration Format
  5. Step 3: Choose Your Configuration Scenario
    • Scenario 1: Automatic Group Creation via MDM (Workspace-Based)
    • Scenario 2: Adding Devices to a Specific Group (Group-Based)
    • Scenario 3: App Distribution via MDM Without Config (Manual Linking)
  6. Step 4: Update Your MDM Provider with the Configuration
  7. Step 5: Verify Device Linking and Content Playback
  8. Additional Notes
  9. Troubleshooting
  10. Support

Prerequisites

  • MDM Provider Access: Ensure you have administrative access to your MDM provider (e.g., JAMF).
  • Kitcast V2 Account: Sign up for an account on Kitcast.tv V2 and have administrative privileges.
  • Compatible Devices: Apple TV devices compatible with the Kitcast tvOS App.

Understanding Key Terms

  • MDM (Mobile Device Management): A platform that allows you to manage and configure devices remotely.
  • Groups: In Kitcast V2, devices are organized into Groups (previously called "Locations" in V1).
  • Secret Key: A unique key used to authenticate and link your devices to your Kitcast account.
  • Plist Configuration: A property list file used by MDM providers to configure apps on devices.

Step 1: Install the Kitcast tvOS App

Before configuring MDM settings, ensure that the Kitcast tvOS App is installed on all your devices.

  • Via MDM: Deploy the Kitcast tvOS App to your devices using your MDM provider.
  • Manually: If not using MDM for app deployment, download and install the app directly from the App Store on each device.

Step 2: Retrieve Your Secret Key and Configuration Format

  1. Log into Kitcast V2: Access your account dashboard.
  2. Navigate to Preferences:
    • Click on your profile icon or account settings.
    • Select Preferences from the dropdown menu.
  3. Copy the Secret Key:
    • Locate the Secret Key section.
    • Click Copy to retrieve your unique secret key.
  4. Download Configuration Templates:
    • Access the Configuration Templates section.
    • Download the plist templates for both Workspace-Based and Group-Based configurations.

Step 3: Choose Your Configuration Scenario

Select the scenario that best fits your organization's needs.

Scenario 1: Automatic Group Creation via MDM (Workspace-Based)

  • Use Case: Ideal if you want MDM to automatically create groups in Kitcast V2 based on your MDM's organizational structure.
  • Variables Used:
    • $UDID: Device Unique Identifier.
    • $DEVICENAME: Name of the device.
    • $SITEID: MDM's location or site ID (maps to Group ID in Kitcast V2).
    • $SITENAME: MDM's location or site name (maps to Group Name in Kitcast V2).

Scenario 2: Adding Devices to a Specific Group (Group-Based)

  • Use Case: Best if you have predefined groups in Kitcast V2 and want to assign devices directly to them.
  • Variables Used:
    • $UDID: Screen Unique Identifier.
    • $DEVICENAME: Name of the screen.
    • Group ID: Specific ID of the group in Kitcast V2.

Scenario 3: App Distribution via MDM Without Config (Manual Linking)

  • Use Case: Suitable if you prefer to link devices manually using codes displayed on the screen.
  • Action: Deploy the app via MDM without a configuration profile (please ensure no profile or any values such as deviceName, externalDeviceId, or secret are set if you want to proceed with this scenario). You will manually assign the screens to the necessary groups.

Step 4: Update Your MDM Provider with the Configuration

For JAMF Users:

  1. Access JAMF Management Console:
    • Log in to your JAMF administrator account.
  2. Navigate to Configuration Profiles:
    • Go to Devices > Configuration Profiles.
  3. Create a New Profile or Edit Existing:
    • New: Click on New to create a new profile.
    • Existing: Select the profile associated with Kitcast and click Edit.
  4. Add or Update the Plist Configuration:
    • Application & Custom Settings: Add a new payload.
    • Upload Plist: Upload the plist file corresponding to your chosen scenario.
    • Variables: Ensure the variables match those used in your MDM (e.g., $UDID, $DEVICENAME).
  5. Assign the Profile to Devices:
    • Under Scope, select the devices or groups you wish to apply the profile to.
  6. Save and Distribute:
    • Click Save to apply the changes.
    • The MDM will push the updated configuration to the selected screens.

Example Configurations:

Workspace-Based Configuration Plist Example:

<dict>

<key>secret</key>

<string>BcjGlIwoQTFHNFlvm7cxyXJMKuC8ETHf</string>

<key>externalDeviceId</key>

<string>$UDID</string>

<key>deviceName</key>

<string>$DEVICENAME</string>

<key>groupId</key>

<string>e22d8abd-5f97-4672-a113-3f9524adef80</string>

</dict>


Group-Based Configuration Plist Example:

<dict>

<key>secret</key>

<string>BcjGlIwoQTFHNFlvm7cxyXJMKuC8ETHf</string> 

<key>externalDeviceId</key>

<string>$UDID</string>

<key>deviceName</key>

<string>$DEVICENAME</string>

<key>externalGroupId</key>

<string>$SITEID</string>

<key>groupName</key>

<string>$SITENAME</string>

</dict>

Step 5: Verify Screen Linking and Content Playback

  1. Check Screen Status in Kitcast V2:
    • Navigate to Screens in your Kitcast Dashboard.
    • Confirm that all screens are listed and linked.
  2. Assign Content to Groups:
    • Go to Content Management.
    • Assign playlists or content to the relevant groups.
  3. Verify on Devices:
    • Ensure that screens are displaying the assigned content.
    • Check for any error messages or issues on the screens.

Additional Notes

  • Custom Values:
    • Instead of MDM variables like $SITEID and $SITENAME, you can use custom values if your MDM doesn't support these variables.
    • Example: Replace $SITENAME with the actual group name you want in Kitcast V2.
  • Group IDs:
    • In Kitcast V2, you can find the Group ID by navigating to the group in your dashboard and copying the ID from the URL or group settings.
  • Device Identifiers (Screens):
    • External Device ID is crucial for matching the device between your MDM and Kitcast screen.
    • Consistency in IDs ensures seamless management and tracking.

Troubleshooting

  • Screens Not Appearing:
    • Ensure that the plist configuration is correctly formatted and uploaded.
    • Verify that the Secret Key matches the one in your Kitcast V2 account.
  • Content Not Playing:
    • Check that content is assigned to the correct group.
    • Confirm that the screens are online and have internet access.
  • MDM Variables Not Substituting:
    • Verify that your MDM supports the variables used.
    • Replace variables with static values if necessary.

Support

If you encounter any issues or have questions:

Congratulations! You have successfully set up MDM for Kitcast V2. Enjoy seamless digital signage management across all your devices.