The TeamViewer Community will undergo scheduled maintenance on Wednesday, Nov. 18, from 2:00-5:00 AM CET.
The Community may be temporarily unavailable during this time. We apologize for the inconvenience. For more information, visit our Status page.
Machines are not being added automatically to specified TeamViewer Group created for new machine deployments. we are currently deploying TeamViewer_Host.msi version 15.35.9.0. this issue just started was wonder what gives? the config id has not changed, the API token has not changed the command being used has not changed just the packaged version.
Regards,
Gabriel
Hello @DesktopSupportTeam,
Welcome to the TeamViewer Community! 🚀
You could test our recommended script using the group-id parameter:
msiexec.exe /i "Path\To\TeamViewer_Host.msi" /qn CUSTOMCONFIGID=xxxxxx ping -n 31 127.0.0.1>nul "Path\To\TeamViewer.exe" assign --api-token xxxxxx --grant-easy-access --group-id gxxxxxx
Adding the group-id is always good for troubleshooting group assignment issues.
You will also find all the recommended steps for the deployment here:
Let me know if you have any further questions! I'll be happy to assist.
/JeanK
Be part of the conversations shaping TeamViewer
Learn more about the latest feature we’ve released.
Discover quick, practical tips to get more out of TeamViewer each month.