QuickSupport Restrictions

SteveRoachStrata

Hi All,

I know there is a way to customise the QuickSupport app that is installed on devices. However, Is there a way to restrict who can connect to those endpoints? I'd like to prevent a situation where any one could call an end user and 'convince' them to open our teamviewer and get the details to allow them to remote on to the users machine and gain control.

I'm sure there must be something to block all connections except from a trusted source/ip address/internal to the network etc.

I see there are policies in the management console but can't tell if these apply to the QuickSupport app or only the full app.

Thanks

JoshP

Hello @SteveRoachStrata

Thank you for your post, and welcome to the TeamViewer community!

Please know that TeamViewer QuickSupport is a run-only executable; this module is great for instances where you need to connect infrequently, or only one time, without having the remote user go through an installation process first.

However, as the module is not installed, it does not have the same capabilities as the Full Version and TeamViewer Host. This includes the same settings, such as Block and Allowlists.

That being said, it is not all bad news!

• As the module is not installed, once the connection is complete the module can be closed out or deleted. QuickSupport cannot run in the background, like the Host and Full version can
• While the standard method of connection via QuickSupport is using the ID and Password, custom QuickSupport modules can instead use a session code - whenever the module is opened using this, a service case is created in your designated group within your Computers & Contacts list.
  • Instead of the remote user providing the ID/Password to the supporter, the supporter instead sends a confirmation request, which the remote user must accept. This means that only users in your Company Profile that support these groups have the ability to connect to your custom QuickSupport module

The above options can help if the usage of the QuickSupport module is integral to your team's support structure. If usage of other modules is possible, I would suggest creating a custom Host module. Similar to QuickSupport, the Host only accepts incoming connections. It is possible, unlike the QuickSupport, to set block and allowlists and implement other security measures, such as the TeamViewer Policies that you mentioned in your post.

The Host module can also be installed while connected through your custom QuickSupport module:

https://community.teamviewer.com/English/kb/articles/13004-install-teamviewer-host-via-the-quick-support-module

I hope this helps! Let us know if you have any other questions 😁