Policies not applying to all new TeamViewer Host installations

Ian_Bowden

We have removed TeamViewer Host across all machines and re-deployed via InTune using the following command:

/qn APITOKEN=XXXXXXXX-XXXXXXXXXXXXXXXXX CUSTOMCONFIGID=XXXXXXX ASSIGNMENTOPTIONS=--grant-easy-access

We've found that most devices are being assigned the 'Servicedesk' policy we've created, but some machines don't have anything assigned at all. The workaround is to uninstall and re-install via the Company Portal, which seems to fix the issue, but there are too many to do this to and I just want it to work automatically.

What might be causing the policy to assign to most but not all new TeamViewer Host installations?

JeanK

Hi @Ian_Bowden, hi @TVMB,

Thank you for posting here. 🙌

I asked our engineers about the issue you reported regarding policies not being applied on all devices.

It seems that the modules you are using might be broken. Therefore, the best option would be to create a new module and redeploy it with the new module's values (API token and customconfigid)

Furthermore, we do have a complete deployment user guide that you can follow here:

📄 Mass deployment on Windows - Overview

Let me know if deploying with a new module fixed the issue.

/JeanK

TVMB

Hi,

we're having issues with the policy created for a group of computers not applying. How long time after applied should it take for the changes to be pushed to computers?

If you hover above a policy it also says "Policy not applied" - why?

Ian_Bowden

Thanks for you support everyone. You all nailed it.

TVMB

https://community.teamviewer.com/English/discussion/comment/135237#Comment_135237

Hi,

I can't see any support at all? I'm facing the same issue with a customer here. How did you solve it?

/Best regards Mattias

JeanK

Hi @Ian_Bowden, hi @TVMB,

Thank you for posting here. 🙌

I asked our engineers about the issue you reported regarding policies not being applied on all devices.

It seems that the modules you are using might be broken. Therefore, the best option would be to create a new module and redeploy it with the new module's values (API token and customconfigid)

Furthermore, we do have a complete deployment user guide that you can follow here:

📄 Mass deployment on Windows - Overview

Let me know if deploying with a new module fixed the issue.

/JeanK

BBSRBK

We've exact the same problem! I try to redownload the module or do I have to recreate a module with new API token?

My command:

msiexec.exe /i "TeamViewer_Host.msi" /qn SETTINGSFILE="%~dp0TeamViewer_Settings.tvopt" CUSTOMCONFIGID=xxx APITOKEN=xxxx

Update:

I redownload msi module and reinstalled the teamviewer host via above command line. Only the settings via Settings.tvopt will be accepted (its only the password). My policy will not be applied!!

JeanK

Hi @BBSRBK,

Thank you for your message and welcome to the TeamViewer Community! 🙌

Redownloading the module and installing the Host won't fix the issue.

You must recreate a new module with a new API token.

Let me know if this has worked for you!

/JeanK

BBSRBK

It works, thanks. But what is the problem?

JeanK

I'm happy it helped! ⭐

I am unable to share the technical explanation for this issue.

However, I'm sure our customer support will be happy to share details with you via ticket.

Have a great day,

/JeanK

TVMB

Hi,

thanks for answer!

The usage were above our total licenses... That's why the policy wasn't applied, thanks anyway!

/Best regards Mattias

auratkachakkar

Thanks for you support everyone.