How do we force a policy to be applied?

mcrawford_carten · 2022-05-05T13:21:33+00:00

There was an error rendering this rich post.

Policies seem to be applied at a seemingly random time, if at all, and the strategies of applying policies I've read in this forum and online have not yet done the trick. Every once in a while a PC picks up a policy quickly, but sometimes it remains as "not applied" for weeks.

An example, which represents most of the PC's we've added in the past two years:

We have a group called Sales, with a Sales Teamviewer policy.
Computer salesRep3 is added to account by activating the license, then adding it to a the group Sales, then once that is saved, telling it to inherit policy from its group.
Teamviewer shows "Not applied (Sales teamviewer policy)
Additional steps we've then taken:
Reboot
Set policy to "none" at the computer level, save, reboot, set policy to "inherit from group", reboot
Set policy to "none" at the computer level, save, reboot, set policy to "Sales teamviewer policy", reboot, set policy to "inherit from group"
Remove the policy at the computer level, setting it to "non", then applying policy to the PC via Design & Deploy / Apply teamviewer policy
Also the same steps (remove policy, re-add) using Design & Deploy

And yet the computer stubbornly shows as "not applied".

There must be a way to force that computer to apply its policy...

Find more posts tagged with

Accepted answers

JeanK

I see... Thank for the details.

If it is just not working with one specific device, I would recommend trying the following:

Unassign the policy from the device
Delete the device from your Computers and Contacts list
Add the device back to your Computers and Contacts list
Assign the policy again

Let me know if this has worked.

/JeanK

All comments

mcrawford_carten

Jean,

It worked!

I didn't even think to try this because we have such a long delay on our account confirmation emails -- sometimes it can be up to 20 minutes -- but confirmation was a complete not issue. TeamViewer didn't even ask, I'm guessing because the client side remembered the connection as having already been confirmed.

And the whole process took less than a minute. Go figure.

Thank you very much.

JeanK

Hello @mcrawford_carten,

Just wondering... is the device turned on and connected to the internet?

I'm just asking... because a policy can only be successfully applied if the device goes online.

All the best,

/JeanK

mcrawford_carten

Note: we've also tried moving the computer to another group that has no policy, rebooting, moving it back to the group with a policy, then setting it to inherit the policy (both at the PC level and via Design & Deploy), then rebooting. The group-move trick didn't appear to help.

mcrawford_carten

Jean,

Yes it is connected. 🙂

I'm in Maine and the device is in CT, and I can both RDP into the device and also useTeamViewer for remote control.

I can run the TeamViewer Management Console either here from Maine or from a server in CT, but the location makes no difference (which is hopefully to be expected).

JeanK

I'm glad I could help!

Sometimes, we are so deeply stuck in an issue that we forget the most basic troubleshooting methods. 😀

Hope to see you soon posting here.

/JeanK

JeanK

I see... Thank for the details.

If it is just not working with one specific device, I would recommend trying the following:

Unassign the policy from the device
Delete the device from your Computers and Contacts list
Add the device back to your Computers and Contacts list
Assign the policy again

Let me know if this has worked.

/JeanK