nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

CUSTOMCONFIGID no longer applies custom Host configuration, assignment still works

Maximilian Sieber

Hello TeamViewer Community,

We have a TeamViewer Corporate license and are currently deploying TeamViewer Host through Microsoft Intune.

Previously, we deployed TeamViewer Host as a Line-of-Business (LOB) MSI application in Intune using the following MSI parameters:

CUSTOMCONFIGID=XXXXXX
ASSIGNMENTID=
DESKTOPSHORTCUTS=0

This worked correctly:

The device was assigned to our company.
The Host module was fully customized (branding, settings, policies, etc.).
The desktop shortcut was removed.

However, we wanted to migrate away from the LOB app deployment method and switch to a Win32 application because Intune frequently failed to correctly detect successful MSI installations. This caused deployment issues and occasionally problems during Autopilot enrollment.

While preparing the Win32 package, I followed the official TeamViewer documentation:

https://www.teamviewer.com/de/global/support/knowledge-base/teamviewer-remote/deployment/mass-deployment-user-guide/create-a-package-in-microsoft-endpoint-manager-via-intune--win32/

I downloaded the latest TeamViewer Host MSI and started testing both locally and through Intune.

Now, using the exact same MSI parameters as before:

The device assignment still works correctly.
The Host installs successfully.
The device appears in our company account.
But the custom Host configuration is no longer applied.

The installation always results in a standard TeamViewer Host installation without our custom branding and settings.

I also tested locally outside of Intune using:

msiexec.exe /i TeamViewer_Host.msi /qn CUSTOMCONFIGID=XXXXX ASSIGNMENTID=XXXX DESKTOPSHORTCUTS=0

The result is identical:

Assignment works.
Customization does not.

Questions:

Has the behavior of CUSTOMCONFIGID changed in recent TeamViewer Host versions?
Does the latest TeamViewer Host MSI still support CUSTOMCONFIGID during deployment?
Is there now an additional step required to apply a custom Host configuration?
Is a command such as TeamViewer.exe customize --id ... required after installation?
Could this be related to changes in the new TeamViewer deployment framework or UI?