Relution Signet Customer Hub

MS Office Volume License 2024

How to license Microsoft Office LTSC 2024 on macOS devices using the VL Serializer in Relution.

To use Microsoft Office apps on macOS, they must be licensed using the Microsoft_Office_LTSC_2024_VL_Serializer.pkg package.

The challenge here is that the PKG changes its internal package name during installation. Since it is not a standard application, the usual procedure for native apps in Relution fails.

Therefore, additional steps are required to:

  • Properly equip the devices with the PKG.
  • Successfully license the Office apps.
  • Maintain device compliance.

Preparing the VL Serializer

The required PKG can be downloaded from the Microsoft Admin Center →.

Relution Configuration

  1. The PKG is uploaded to the Relution App Store.
  2. In the Detection rules section of the app, a rule of type Package Name is created via Add (the app cannot be saved without a detection rule), and the following value is entered in the Package name field so that Relution can correctly interpret the installation status:
com.microsoft.office.licensingV2.helper

Deploying the PKG

The PKG must be transferred to the endpoints. There are two ways to achieve this:

Manual Installation

The PKG is manually copied to the respective device and executed locally. However, this is not efficient for larger rollouts.

  • Deployment via a Relution script that is created under Scripts → Scripts and executed by the macOS Companion: once via the Execute shell script or Execute on device action, or on a schedule via the Script configuration of a macOS policy.
  • Download of the file to /Users/Shared/.
  • Subsequent silent installation via the terminal.

Download & Installation

This script downloads the serializer from an external source (e.g., a file server) and installs it directly.

#!/bin/bash

# Configuration
URL="https://your-share.com/link/to/file"
PKG="/Users/Shared/Microsoft_Office_LTSC_2024_VL_Serializer.pkg"

echo "Starting download..."
if ! curl -fL "$URL" -o "$PKG"; then
    echo "Error: Download failed."
    exit 1
fi

echo "Serializer found – starting installation..."
/usr/sbin/installer -pkg "$PKG" -target /

if [ $? -eq 0 ]; then
    echo "Installation completed successfully."
    rm "$PKG" # Optional: Delete installer after success
    exit 0
else
    echo "Error: Installation failed."
    exit 1
fi

Installing a Locally Available PKG

If the file has already been placed in the Shared folder, the following script can be used:

#!/bin/bash

PKG="/Users/Shared/Microsoft_Office_LTSC_2024_VL_Serializer.pkg"

if [ -f "$PKG" ]; then
    echo "Serializer found – starting installation..."

    sudo /usr/sbin/installer -pkg "$PKG" -target /

    if [ $? -eq 0 ]; then
        echo "Installation completed successfully."
        exit 0
    else
        echo "Error: Installation failed."
        exit 1
    fi
else
    echo "Error: PKG file not found at $PKG."
    exit 1
fi

Distribution via App Compliance

Once the PKG is uploaded to Relution and the detection rule is stored, it can be managed via the App compliance configuration of a macOS policy:

  1. In the configuration, the app is added under Required apps and the policy is published. If Auto install is enabled for the app, Relution installs the uploaded PKG itself on devices where the identifier is missing; the detection rule prevents repeated installations.
  2. Relution uses the detection rule to check whether the identifier com.microsoft.office.licensingV2.helper is included in the device’s list of installed apps (and, if version check is enabled, its version). Relution does not check whether Office is actually licensed.
  3. Devices without this identifier are marked as Noncompliant, provided the option Add compliance violation when required apps are missing is enabled under Settings → Device Management → Device Management (default). The script can be run again on these devices.