In addition, if your organization relies a lot on collaboration and team cooperation, it is well suited for that. It is also helpful that TeamViewer recently started supporting iOS devices. Their customer service and support have always been responsive and have met my expectations so far. In terms of scalability, TeamViewer has great potential. Moreso, I have found that TeamViewer is able to handle slow internet connections better than other alternatives can. I can control someone else’s computer, show or teach them how to do something, or fix any problems they are having. By far, one of its best features is the remote access it provides.

Random password disabled on host modules, enforcedĭoes this setup look like it's secure enough to let those host modules run on computers so that the admin can take unattended access whenever needed? If not, please include reasons for it and/or tips and tricks to make it more secure.The number one advantage of TeamViewer for me is its ease of use, specifically as it relates to the client side.Any changes to host requires local admin password, enforced.Prevent the unassignment of the assigned admin account in host modules, enforced.Whitelist in use to allow connections only from the admin account, enforced.Install all new updates automatically, enforced.On top of that there's a policy attached to the custom host module deployment that specifies the following things for every host: TeamViewer custom host module with account assignment for the admin account (easy access/unattended access) enabled, so the deployment happens with the specific api token.Full TeamViewer client for admin to give remote assistance (random password disabled).TeamViewer account with a complex password and 2FA enabled.Now I decided to come seek professional and objective opinions about the security of the following scenario: I'm a systems specialist in our organization and I've read a lot about TeamViewer security concerns over the last few years.

Teamviewer host only