Managed Group Assignment - Error 408

kvnjsu

Hello all,

we just upgraded TeamViewer license to Tensor and we finally have Managed Groups. We kind of had them before, we had one admin account sharing all groups. Anyway.

We are now wanting to migrate all TeamViewer hosts to the Managed Groups and we are following the TeamViewer guide for Windows machines.

This is the script we run as system within KACE K1000:

cmd.exe /c "C:\Program Files (x86)\TeamViewer\TeamViewer.exe" assignment --id 0001XXXXX

We are getting mixed results. On some devices it just works and some report the error "408" back. The search on google and on this forum gave me zero results...

How do we fix this? How do we migrate all devices into Managed Groups?

All Windows, All TeamViewer Hosts, Versions 12-15 different patches.

Thanks

Sven_F

Hi @kvnjsu ,

there is a possibility to import already existing devices (from the shared groups) into the managed groups. See the article https://community.teamviewer.com/English/kb/articles/105379-performance-and-scalability-improvements-for-managed-device-and-managed-groups under the section "Import of already managed devices".

Furthermore the error code you receive means that the assignment was denied by an active policy "preventing the account assignment" on a device. Please disable this policy on the affected devices and it should work.

Here's a list of errors that might come up during deployment and possible solutions to them: https://community.teamviewer.com/English/kb/articles/109373-deploy-teamviewer-host-or-full-client-9-9#error-codes

Best

Sven

kvnjsu

Thanks that helped!

Sven_F

Hi @kvnjsu ,

there is a possibility to import already existing devices (from the shared groups) into the managed groups. See the article https://community.teamviewer.com/English/kb/articles/105379-performance-and-scalability-improvements-for-managed-device-and-managed-groups under the section "Import of already managed devices".

Furthermore the error code you receive means that the assignment was denied by an active policy "preventing the account assignment" on a device. Please disable this policy on the affected devices and it should work.

Here's a list of errors that might come up during deployment and possible solutions to them: https://community.teamviewer.com/English/kb/articles/109373-deploy-teamviewer-host-or-full-client-9-9#error-codes

Best

Sven

kvnjsu

Thanks that helped!

kvnjsu

https://community.teamviewer.com/English/discussion/comment/135637#Comment_135637

This leads me to another question, I have done the import before. However I noticed, when I am using the import from shared groups to managed groups, it is not showing "Assign TeamViewer Policies".

However if I assign a device with the teamviewer.exe --assingment ID xxxxx the device will show up like this, with the option to assign TeamViewer Policies.

Why is it not showing for the migrated one?

JeanK

Hi @kvnjsu,

To be able to assign TeamViewer policies to a device, it must be assigned to your account.

My guess is that these devices (from the shared groups) are not assigned to your account.

You can assign the devices to your account by following the instructions here:

📄 Assign a device via command line

I hope this can help!

/JeanK

Sven_F

@kvnjsu

when migrating a device via the wizard in the Management Console, the manager assigned to the device will not automatically get "policy administration" permissions by default. You need to grant this permissions separately by editing the manager permissions for that device. This permission however is set by default when assigning the device via command line.

Best

Sven