TeamViewer Forum
General Category => Teamviewer for Windows => Topic started by: bjblackmore on April 08, 2015, 03:58:48 AM
-
Hi,
Another question, when I created my MSI to deploy, I selected the option "Automatically add computers to a group in your Computers list", and selected the group "CompanyServiceDesk". This group has a TeamViewer policy applied to it, called 'Workstations'. When I push out the MSI to new workstations, they show up under the "CompanyServiceDesk" group, but they don't appear to have the policy appllied. If I try and connect using my Windows passwor,d it says Windows login has been disabled (the Workstation policy enables this). If I check the properties of the system via the management console, it shows 'TeamViewer Policy - None'. I have to manaually select 'Inheric from group'. Shouldn't group inheritance be the default? If not, how can I enable inheritance by default? When we roll out to 7000+ workstations I can go through each system and switch inheritance on!
Thanks
Ben
-
Ben,
If you haven't already, I'd submit a ticket via official support channels.
Matt
-
did you solve this? I have the same issue and Teamviewer official support says the "do not inherit" is the standard setting for clients..
which is downright stupid!
-
Hi all.
Here's where I am at right now...
I've DELETED the policy settings on teamviewer's website.. so NO policies are active.
I then installed Teamviewer HOST on a VDI without the company customization.
I set all settings as I want them.
I rebooted
I entered the "unattended settings".
I exported the reg settings via teamviewer host->advanced
Now because we only use 64-bit OS I did as follows
I copy pasted each section of the registry pertaining to local machine.. meaning I now have DOUBLE entries in my reg file of all Local Machine settings.
I then added Wow3264Node\ after Software.
so instead of HKLM\SOFTWARE\Teamviewer
I use HKLM\SOFTWARE\Wow3264Node\Teamviewer
so for each section in the registry I now have 1 for \Software\teamviewer and 1 for Software\wow3264Node\Software
Then on a vdi.. install host, run registry, reboot.
This seems to work.
I haven't tried this with company customisation yet.. but will today..