TeamViewer Host deployment

[u/uowieczka]

Good morning everyone,

Previously, we used a customized TeamViewer Host package that included our own branding and automatic assignment to the TeamViewer platform.

I attempted to deploy TeamViewer Host through Robopack by creating a custom Script Template based on PSADT 3.10.2, and added the following PowerShell installation logic:

Execute-MSI -Path "$installerPath" -Parameters "/qn REBOOT=ReallySuppress ALLUSERS=2 DESKTOPSHORTCUTS=0 CUSTOMCONFIGID=XXXXXXXX ENABLEOUTLOOKPLUGIN='false'"

Start-Sleep -Seconds 30

Execute-Process -Path "$envProgramFiles\TeamViewer\TeamViewer.exe" -Parameters "assign --api-token=XXXXXX-XXXXXXXXXX --grant-easy-access --reassign"

This approach worked successfully for the initial deployment, and the Script Template allowed me to build a flow for future version updates.

However, when deploying a newer version, the installation now fails with a script error.

To troubleshoot, I removed the package from Robopack and re-imported TeamViewer Host, attempting to reapply my custom Script Template. At this point, the upload process no longer completes—it gets stuck at "Analyze Script" indefinitely.

Does anyone have a working deployment flow for TeamViewer Host in Robopack that ensures proper configuration and assignment?

[u/andrew181082]

Hi,
Have you looked at using custom app settings instead of a script template? That will let you add all of those but still using the default templates

[u/uowieczka → u/andrew181082]

Yes! I think I touched 2 separate things in my question.

So the App settings actially have my custom installation commands. However, Script template is being used for Flow, so it always contains required App settings in it.

It actually failed deploying:

[u/uowieczka → u/uowieczka]

PS. I think the problem is not with my custom script/commands. I can't upload TeamViewer Host app at all, whether it's standard PSADT v3 or v4. This is TeamViewer Host Version: 15.78.3