Hi @JeanK Thank you for welcoming and your competent answer. So if i get you.. you mean I should create two groups with two diffrent policies (incoming rules) and apply them to groups. In my situation that would work for group A (internal Hosts) but not for "group B". My problem is we don't know the computers in group B. We connect to any computer of our customers to support our software... The customer uses maybe the FullClient (whitout any connection to our pool) or maybe our QuickSupport. That's the reason why we apply the Access Controll (outgoing connections) 'confirm all' to all of our clients. And this setting dominates the full access incoming rule on group A.. So.. is it possible to combine the incoming rule (on internal clients in group A / whitelisting..) and the outgoing restrictive rule (to any TeamViewer-Client on this world)? Thank you in advance!
... View more
Hi Guys. Unfortunately I could not find an answer to my question yet. Here's the situation: Our supporters are not allowed to automatically take over remote control when connecting to customers. Therefore, the local settings on the devices are 'confirm all' when connecting to other devices. But now there are internal unattended devices on which TeamViewer Host is installed, where our supporters should have direct 'full access'. The TeamViewer Host is configured with full access and our company pool is entered on the whitelist. A company member is also registered there. >> When you connect to the host, you don't have full access, but the 'confirm all' settings of the client are applied. Is there a clean solution for this? Possibly via policies/groups? Several policies, depending on whether you are operating within the company pool? Thanks for the answers!
... View more