Command line install of TeamViewer_Host.msi not accepting ASSIGNMENTID= on first pass

Question

Hi, I am following this official TeamViewer KB article on how to "Deploy TeamViewer (Host or full client)"… NB: Last Modified: Mar 19, 2026 https://www.teamviewer.com/en/global/support/knowledge-base/teamviewer-remote/deployment/mass-deployment-user-guide/deploy-teamviewer-host-or-full-client-9-10/ The given example for a Windows TeamViewer Host MSI installation shows the following syntax: start /wait MSIEXEC.EXE /i "PATH_TO_MSI_FILE\TeamViewer_Host.msi" /qn CUSTOMCONFIGID=YOUR_CUSTOM_CONFIG_ID ASSIGNMENTID=YOUR_ASSIGNMENT_ID I am using TeamViewer x64 host, version: 15.81.6.0 Here is my command with the "CUSTOMCONFIGID" and "ASSIGNMENTID" obfuscated. NOTE: I'm using extra switches denoted in the KB article too… start /wait msiexec.exe /i "TeamViewer_Host.msi" /passive ADDLOCAL=ALL CUSTOMCONFIGID=6•••xy ASSIGNMENTID=0001C•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••Qc= INSTALLSECURITYKEYREDIRECTION=1 REMOVE=f.DesktopShortcut The issue is that the TeamViewer host does not appear in my TeamViewer tenant unless I either: (a) run the exact same MSI command the second time around (with zero changes), or (b) run the following command immediately post the first installation run of the TeamViewer host: C:\Program Files\TeamViewer\TeamViewer.exe" assignment --id 0001C•••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••••Qc= NB: The later command is from this official TeamViewer KB article on how to "Assign existing TeamViewer installations via command line" https://www.teamviewer.com/en/global/support/knowledge-base/teamviewer-remote/deployment/mass-deployment-user-guide/assign-a-device-via-command-line-8-10/ I don't see why the MSI installation isn't working as documented? I can't see any issues with my syntax???? Thank you

.Carol.fg. · Answer

Hi@John Fry,

Thanks for reaching out to our Community!

Different reasons could cause the issue, but by the description provided, it's possible that the client doesn't reach our servers quickly enough to do the assignment before the installation finishes, causing the instability to display the devices.

The recommendation is to use the Retries and Timeout parameters as shown in the article Deploy TeamViewer (Host or full client)

Let us know how it goes, and don't hesitate to post again if you need further help.

Best, Carol

John Fry · Answer

web.teamviewer.com | Device(s) showing…

TeamViewer Full-Client

John Fry · Answer

I've raised this as a question with TeamViewer support along with a few other issues which seem strange to me. My latest though is that this is a problem with the TeamViewer Full-Client simply not updating / rendering correctly…

1. I've seen some weird things recently whereby the TeamViewer Full-Client doesn't show my newly installed host(s), but web.teamviewer.com does. A usual killing of the TeamViewer Full-Client process and logging back into it fixes this, but no-one should have to go to that extent.

2. I've also see the TeamViewer Full-Client suggesting I have no users/admins in my tenant, but web.teamviewer.com shows them all sitting there fine.

3. I've seen other object come and go before my very eyes in the TeamViewer Full-Client.

I've checked all the required ports are open and I've tested this on multiple machines in different environments.

There have literally been a few of us watching  the TeamViewer Full-Client GUI at the same time and all of a sudden with zero change the missing objects start appearing again out of the blue.  Whilst on someone else's TeamViewer Full-Client GUI the objects are still missing.

Just smells like the TeamViewer SaaS backend is crawling or perhaps the TeamViewer Full-Client GUI has some weird polling thing going on and at these intervals it needs to clear the GUI and render the objects again.

All in all it serves for a really poor UX!