Read this article in: ChineseFrenchGerman | Japanese | Spanish


With the latest updates to our TeamViewer Management Console, it is now possible to easily check for devices which are not compliant with your policy setting and find important information to identify problems on policy assignment and decide how to react.

Requirements

To be able to use this feature, you must meet the following requirements:

  • The device that you want to assign a policy to has installed TeamViewer 10 (or later)
    • With older versions of TeamViewer, setting policies were not available at all.
  • You own a TeamViewer 12 Business license (or higher)
  • You have a TeamViewer account
Note: Assigning and using TeamViewer setting policies is only available for managed devices. Please make sure you assign all devices to your account beforehand.

 

Monitor the assignment for all your devices

The assignment status of a TeamViewer Setting Policy is displayed within the Computers & Contacts list of the TeamViewer Management Console.

  1. Open the TeamViewer Management Console.
  2. Go to a group of contacts and devices.
  3. A column Policy is displayed by default
    1. You will see the status of the assignment in the columns of each device.
      policy.png
    2. You can hide the column if wanted via the Views menu.
      view-menu.png

Which different status are available?

The status of the assignment differs depending on the precondition of the device, the policy is assigned to.

Status Meaning Reason Solution
<policy name> Policy was successfully applied on the device Device successfully requested and applied the policy. -
Not applied (<policy name>) Please check that the device is online to apply the policy Device was not online yet since the policy was assigned. Make sure, TeamViewer 12 is running and ready to connect on the remote device.
Not applied (<policy name>) A problem occurred. Policy could not be received by the device. TeamViewer 10 (or later) is running but assigned policy was not requested. If you are using version 11 or older, update to TeamViewer 12 if possible. If not, reassign the account (remove account assignment and assign again), and/or reassign policy (select "None", save, then select a policy again and save).
Not applied (<policy name>) A problem occurred. Policy could not be applied on the device. TeamViewer 12 is running and the assigned policy was requested but not applied. Reassign the account (remove account assignment and assign again), and/or reassign policy (select "None", save, then select a policy again and save).
Not removed (<policy name>)
Not removed (deleted policy)*
Please check that the device is online to remove the policy TeamViewer 12 is running and the device is offline and has not yet acknowledged the removal of the policy. Make sure, TeamViewer is running and ready to connect on the remote device.
Not removed (<policy name>)
Not removed (deleted policy)*
A problem occurred. Policy could not be removed on the device. TeamViewer 12 is running and the device is online and has not yet acknowledged the removal of the policy. Reassign the account (remove account assignment and assign again), or set policy to "None" again (first select a random policy, save, then select "None" again and save).
Policies not supported (<policy name>) The TeamViewer version on this device does not support policies. Please update. ‘<policy name>‘ was assigned while the device was offline; After being online again, it is recognized as version 9 or older. Update the remote client to TeamViewer 10 (or later).
Check not supported (<policy name>) The TeamViewer version on this device does not support policy check. Please update.  ‘<policy name>‘ was assigned but the device runs TeamViewer 11 or older and does not support policy check. Update the remote client to TeamViewer 12 with policy check support.
No entry No policy has been assigned so far or removal was correctly applied. - -


*If the policy was deleted in the meantime, its name is no longer available.

Version history
Revision #:
6 of 6
Last update:
‎04 Jun 2019, 12:58 PM
Updated by:
 
Labels (1)