Windows 10 - Policy not applied

tuomasrFIN

Hello all,

I have been demoing the customized Teamviewer 12 Host MSI installation and it has been working very well. However there are some problems with the policy that I have set to the customized Host -package; It does not apply to two Windows 10 test machines, to a Windows 7 machine it does apply.

I can see that it does not apply since there is no password field when opening the Host mode of Teamviewer 12. And when I go to settings there are no customizations that should be there via the policy.

Any ideas? I Know I can push the policies from the list at login.teamviewer.com but that kills the purpose of automatically assigning the policies.

 

Best regards,

Tuomas

tuomasrFIN

Hello,

I created a support ticket to Teamviewer support also and via log files they managed to find the cause of the problem. The problem was that I was using SCP in my AD infrastructure and I had also checked the box: "Allow account assignment via the assignment tool" in the customized module. 

After removing that check box and downloading a new version of the customized module it began correctly getting the policy.

Chiron

Mine are working.

My automated deployments are set to join a group, and inherit the policy from the group.

tuomasrFIN

Hello,

I also tried to set the option "inherit from group" instead of assigning the policy straight to customized module but it did not change the situation.

Chiron

I have nothing to back this up, but maybe your Win 10 computers have something different in the local firewall\network settings.

I have a subnet that is blocked from the Internet, but we have ports open for TeamViewer. Auto deployments on that subnet do not download the custom branding for the host. We have just started to investigate, but we are convinced it is something in the firewall.

Please let us know if you find a solution!

tuomasrFIN

Hello,

I created a support ticket to Teamviewer support also and via log files they managed to find the cause of the problem. The problem was that I was using SCP in my AD infrastructure and I had also checked the box: "Allow account assignment via the assignment tool" in the customized module. 

After removing that check box and downloading a new version of the customized module it began correctly getting the policy.