Maybe you develop a protocol of only connecting in the way that prompts the user to confirm you connecting is ok. Just because you have the capability to do something does not mean you will. And even if you had unattended access, if the computer is locked, it's not like you already know the user's password and can login as that user. My recommendation would be to show the user what it looks like if someone remote connected via TeamViewer using unattended access. You could technically still get in with Windows Authentication (assuming you have that enabled in your policy settings). If the user is super concerned, have them change the unattended access password on their machine (only place it can actually be changed from what I understand). They get a rather large popup in their system tray that shows someone has connected (which even shows the name of the person who is connecting). The thing with TeamViewer Host is that an end user is going to know you are connected to their machine.

Use AccessibilityService for more complex use cases.We use TeamViewer Host as well, and I had a user bring up that same concern the other day.

Write a shell script that uses adb for simple, one-off operations.

This answer shows how to automate it, but I have yet to test if it works.

AccessibilityService needs to be enabled manually.

Needs to install your app on the devices.

You will need to write an Android app that has an AccessibilityService and bulk install it on the devices (via adb or any other means).

Quite tedious when your flow is complex (kind of a personal opinion, so take this with a grain of salt).

See Using ADB to access a particular UI control on the screen.Įdit: Culebra GUI seems to make your life a lot easier should you take this approach. Use adb to grab coordinates and simulate touches.

I don't have time to create a detailed solution for you, but I'll suggest these two approaches. So, from your comment, you need to change this setting for quite a lot of devices (around 500).

Teamviewer host