Remove Assignment Prompt when installing Host via Mass Deployment
Currently, when Host config is set to use Managed Groups, you will receive a prompt when running the Mass Deployment command line to install a Host client.
As a large organization trying to deploy this to ~1000 devices via SCCM we need this to not prompt. This prevents Host deployment to unattended devices, requires a firmwide
communication for something that in the past we've done behind the scenes and adds in a point of failure for those users that always click the wrong thing.
I understand the security concerns but this currently makes the Managed Groups feature completely unusable. We would love to be using the Managed groups as it adds more granular control with who can access what, but we cannot with the prompt.
Best Answer
-
Thank you for asking this here. I allowed myself to merge both of your posts.
The reason why a prompt is showing after the installation is that the parameter Use Managed Group assignment of your Host is enabled.
To solve your issue, you need to disable this parameter like in this video:
You can also follow these steps:
- Sign in to https://login.teamviewer.com/.
- Go to Design & Deploy.
- Edit your custom Host.
- Untick the Use Managed Group assignment parameter and save.
- Redeploy your custom Host on your devices.
You will see that no prompt will show to confirm the group assignment.
For your deployment, I recommend following our user guide here:
Mass deployment - Overview
Let me know if this has worked for you!
/JeanK
Community Manager
0
Answers
-
Will a new version address the problem that you cannot use Use Managed Group assignment when mass deploying Host versions due to the prompt asking if its ok to assign to the group? It makes the new Managed Group feature completely unusable when deploying this to unattended machines or without firmwide communication and instructions.
2 -
Thank you for asking this here. I allowed myself to merge both of your posts.
The reason why a prompt is showing after the installation is that the parameter Use Managed Group assignment of your Host is enabled.
To solve your issue, you need to disable this parameter like in this video:
You can also follow these steps:
- Sign in to https://login.teamviewer.com/.
- Go to Design & Deploy.
- Edit your custom Host.
- Untick the Use Managed Group assignment parameter and save.
- Redeploy your custom Host on your devices.
You will see that no prompt will show to confirm the group assignment.
For your deployment, I recommend following our user guide here:
Mass deployment - Overview
Let me know if this has worked for you!
/JeanK
Community Manager
0 -
Same Here, please fix it ! it's impossible to use management group with this configuration
0 -
I am having the same issue. I am using the new web.teamviewer.com site...i do not see an option to turn that group assignment off. Why are there two web interfaces? Cant you just provide simple deployment directions for SCCM that instal silently with no user interaction?
0 -
Hi @WCSD_DOT1,
Thank you for asking!
If you are using the new interface, the solution is to use the rollout configuration.
We explain how to proceed in our deployment guide: 📄Create a rollout configuration - 6/10
With the rollout configuration, you can define the groups and the managers of the devices you are rolling out.
Hope this helps!
/JeanK
Community Manager
0 -
Hi @JeanK
I am using the new interface, and have followed you guidance.
But I don't see any solution for the Account Assignment prompt.
I would like to deploy TeamViewer without any user interaction. Please let me know what to do.
0 -
Hi @LasseHansen,
I've talked with our engineers and come back with (hopefully) the solution. 🙂
When using the new interface and deploying TeamViewer via script, it is important that the rollout configuration in the module's settings is set to None.
Please give it a try. You shouldn't see the pop-up; the installation should occur without user interaction.
Looking forward to hearing from you.
/JeanK
Community Manager
0 -
I am going through this process now. I noticed the popup and didn't like that. Here's the script I am currently using:
start /wait MSIEXEC.EXE /i "%~dp0\TeamViewer_Host.msi" /qn CUSTOMCONFIGID=<custom module ID>
timeout /t 30 /nobreak
"C:\Program Files\TeamViewer\TeamViewer.exe" assignment --id <rollout config ID>When you run the first command, it installs TeamViewer Host with no input… quiet and easy… but, it doesn't put it into the correct group like the Custom Module with Rollout Configuration set.
The Custom Module seems to be for systems that might not be immediately managed (BYOD, remote, etc). You can give the end user a quick link and have them install what comes up. Basically, you want these users to accept the requirements manually because it's not a company device. If you turn off the rollout option as @JeanK suggested, you won't get the device added into the group automatically, but it won't prompt the user with a popup either. You still get to customize the app window's logo, colors, etc. along with any future service desk stuff they add in the future.
The third line is where the magic happens… when you (re)launch the host, you put the rollout ID in the command line. THAT is what puts it into the correct group. You only need to run it this way one time. Future launches, unless something changes, should be the normal command.
I've had good luck with using the custom module on the install, but with no rollout selected. Then, after the built in script wait, it will relaunch the app with the rollout configuration settings. At that point, it immediately shows up in the support app / website with the correct group set. Unattended access works as expected, no input from the end user.
2
