This article explains how to configure and deploy multiple playlists in Vibe so that different users or devices automatically receive the correct content based on attributes such as location, department, or brand.

Overview

Vibe allows you to dynamically assign playlists to devices by using a unique Auth Code. Each Auth Code corresponds to a specific playlist. By managing this code at the device level, you can control which playlist is displayed without needing manual intervention.

This approach is ideal for organisations with multiple offices, departments, or branding requirements.

How It Works

The playlist assignment is controlled through a Windows registry value:

HKEY_LOCAL_MACHINE\Software\WOW6432Node\VibeDesktopPlayer\ApiAuthCode

• This registry key stores the Vibe Auth Code
• The Auth Code determines which playlist the device connects to
• The Vibe Desktop Player reads this value and assigns the appropriate playlist

Default Deployment

When deploying the Vibe Desktop Player using the MSI package:

• A default Auth Code is configured during installation
• This ensures all devices are initially assigned to a default playlist

This provides a simple baseline setup before applying any customization.

Customising Playlist Assignments

To deliver personalised playlist experiences, the Auth Code can be dynamically updated based on user or device attributes.

Common attributes include:

• Location
• Department
• Brand

This customization is handled through your organisation’s endpoint management or scripting logic.

Example Implementation

A typical implementation might look like this:

1. A PowerShell login script runs when a user signs in
2. The script retrieves user attributes (e.g., location and brand)
3. Based on predefined mapping logic, it selects the correct Auth Code
4. The script writes the Auth Code to the registry key
5. The Vibe Desktop Player reads the updated value and assigns the correct playlist

Management Options

You can control and update the Auth Code using various tools, depending on your environment:

• Microsoft Intune
• Group Policy (GPO)
• Login scripts (PowerShell)
• Other endpoint management tools

This flexibility allows you to integrate Vibe into your existing IT management processes.

End-to-End Flow

The complete workflow is as follows:

1. Vibe provides a list of Auth Codes mapped to playlists

2. Your organisation determines user attributes (location, department, brand)

3. A script, policy, or management rule maps those attributes to the correct Auth Code

4. The Auth Code is written to screen saver Authcode:

   HKEY_LOCAL_MACHINE\Software\WOW6432Node\VibeDesktopPlayer\ApiAuthCode
   

5. The Vibe Desktop Player uses this Auth Code to connect to the correct playlist

6. If user attributes change, the Auth Code is updated automatically at the next login

Key Benefits

• Automated playlist assignment
• Scalable across multiple locations and teams
• Centralised control using existing IT tools
• Dynamic updates based on user changes

By leveraging registry-based Auth Code management, you can efficiently deliver targeted and relevant playlist content across your organisation with minimal manual effort.