TeamViewer Reviews

TeamViewer is useful for accessing data and systems remotely. Using this application, I can access other computers using an ID number that I provide to the users whose laptop I would like to access.

TeamViewer is publicly available and anyone can use it. This is the reason that many organizations do not permit the use of this solution. It is not considered to be secure enough. 

I have been using this solution for six months. 

The initial setup is straightforward. If your network connection is good, this solution provides you with very scalable performance.

Using this solution does not require any license plan. It's just a soft application which we are going to install on our systems.

I would recommend this solution to other users. I would rate it a ten out of ten. 

We're using TeamViewer at the college to be able to remote in. My boss and I are the two main users. We've used it to remote into our desktops so we can monitor the HVAC program at the college, access control, etc. Plus, if we need to grab files, or something, off of our personal computers at work, we can.

My boss and I both have TeamVeamer installed on PCs at the campus. We have the app on our mobile phones. I have it on my personal laptop at home along with my tablet at home.

We remote into PCs at the campus, and one of those PCs is used as a server.

We are using the latest version. We are using TeamViewer 15. I think we started on version 13.

When I'm offsite and there is an HVAC problem, I can remote in and check out what's going on from anywhere. I don't have to be at the college to do it. It saves me driving time and the hassle of having to leave from wherever I'm at. I have actually accessed it while being on vacation and was several hundred miles away from the college.

• It's easy to remote in.
• It is reliable and stable. The program is not constantly interrupting, dropping, or hanging up.
• It has been very easy to use.

Sometimes, the app can be a little cumbersome when accessing certain aspects of the program. I don't know if that's a TeamViewer thing or the application I'm trying to use on the actual PC.

As far as the connection, there has been no issues with the connection. It's just once I'm in the app and using it, I haven't been able to decide if I can do all functions with the app, like I can if I'm sitting actually at the computer. I don't know if that's a TeamViewer thing or a computer issue. I'm still on a Windows 7 based, six-year computer which is due for an upgrade. It's a minor issue, and some of the minor issues I have may go away once my desktop computer at work is upgraded.

Approximately six months.

I am very happy with the solution's stability. 

So far, we have had no issues with security's success because you need to know the passwords and machine IDs in order to get into the system. TeamViewer identifies each device with a unique identifier, then each device has a separate password. Once you have closed TeamViewer, the password will change periodically. It's not a constant password.

Most of the stuff resides between my computer and my boss's computer. My boss is the director of facilities and I'm the maintenance supervisor.

Eventually, when we're done (hopefully not soon after the first of the year), we're going to be able to go to every building on campus and deploy what we need to look at. That way we don't have to worry about whether we have lost a phone signal, the wireless on campus is working right, etc. Eventually, we'll have a machine on campus that we can just go to and access what we need.

We called the support only one time. That was just to make sure we were doing something right, and we were.

On a scale of one to 10, with 10 being the highest, the technical support was easily a 10. This is based on their responsiveness and helpfulness. We were on hold with them for just a couple of minutes, then the technician that we talked to was very helpful. We didn't have to go back and forth, checking on him a bunch. He was able to answer all our questions. He called my boss back the next day to make sure there were not other issues and everything was working.

LogMeIn and ShareConnect were the only two solutions that we have previously used. Then, somebody told us about TeamViewer. We looked at it. We did a trial run with TeamViewer. We liked it, so we started engaging with them about the cost and everything else. 

The initial setup was very straightforward. You go to TeamViewer or the link that they send you. You click on the link to download and install all the information right off the Internet. It's fairly self-explanatory. 

My boss and I set up all four of our devices, the mobile app on both our phones and both our computers, in less than five minutes.

We had a webinar with TeamViewer to go over some basic, simple things. We only needed 15 to 20 minutes. It was pretty much understanding the basics. 

If we had any other questions, we could call in. I haven't personally had any issues where I've had to call support.

Over the past six months, we have probably saved several thousand dollars just in the cost of either my boss or me having to go up there. We can make sure stuff is turned off and on where somebody might have left something on or off, saving on the utility cost for the college.

TeamViewer was willing to give us a one-year package. Whereas, a lot of the other companies that we explored were paid by the month or quarter. It's just easier for our finance people at the college if we can make a one-time yearly payment.

TeamViewer has multiple licensing options. 

The price was cheaper than what we were previously paying. At the time that we went with TeamViewer, we were using ShareConnect. The TeamViewer package was about half the cost and able to have a bigger number of users.

The remote connection process has been one of the easiest of all the different programs that we have used. We have used LogMeIn and ShareConnect. There was another one back in the very early days. This solution has been the easiest process to connect into. Comparatively, TeamViewer is much easier to deploy, easier to use, and adopt than LogMeIn or ShareConnect.

The solution is definitely a 10 (out of a 10). TeamViewer has been one of the easiest, right off the bat products, that we have employed at the college. We have had no issues. It's been one of the easiest solutions to pick up.

TeamViewer allows the capture of the screens of the colleagues on the network.

For example, when the user works with his screen for a process and encounters a problem, he informs us or reaches out on WhatsApp. We get control of his screen and try to understand the problem and then try to solve the problem.

Without going to the actual user or colleague, I can access his screen. This is the value of the solution for me.

It is quite simple to set up.

It is stable. 

Voice communication and screen communication or face-to-face communication could be improved. The screen should be something like Zoom when I want to talk with my counterpart. I want to communicate with my counterpart while also seeing the screen.

I've used the solution for three years. 

The solution is stable. It is reliable. There are no bugs or glitches. It doesn't crash or freeze. The performance is good. 

We have 13 licenses. For the time being, the solution is fine and we do not plan to increase usage.  

I've never used technical support from TeamViewer. 

Sometimes we use AnyDesk. However, it gets disconnected suddenly. TeamViewer is very good. It doesn't happen. 

The solution is easy to set up and quick to deploy. You can have it up and running in one day. 

We have three to five people in the IT department that can handle deployment and maintenance tasks. They are IT technicians.

I don't handle the licensing. I can't speak to the costs. However, my understanding is that it is reasonably priced. 

I'm not sure which version of the solution we're using. 

I'd rate the product nine out of ten. 

I would recommend the solution to others. 

TeamViewer can be used for remote accessing computer systems.

The most valuable feature of TeamViewer is user-friendliness.

I have been using TeamViewer for approximately five years.

We have 200 people in my company, but not all of them are using TeamViewer. We do not have plans to increase usage.

The support could improve their speed.

I rate the support from TeamViewer a three out of ten.

The initial setup of TeamViewer is straightforward. It took us approximately two weeks to deploy.

We have a team of four that does the implementation of TeamViewer in-house.

I would recommend this solution to others. It is a good solution.

I rate TeamViewer a seven out of ten.

Basically, the solution is being used in order for the IT department to assist me in any problem I have with my computer. It’s for them to have remote access.

It doesn't take any effort for me to fix something that I can’t. I can just call IT and they can just connect and take over the control of my computer and fix it for me, and that’s it.

The implementation process is simple.

It's pretty limited on the options they have. I'm pretty sure they can expand the program a bit and have some more options.

If they, for example, access your computer, I’d like them to be able to diagnose and find any other issues on the computer when they are on there for something else.

The connection and reconnection sometimes lag and can cause problems. They need to look into that. If they can work on the pause button to make it easier to start and stop without lagging, it would be ideal.

I’ve been using the solution for approximately two years.

When we actually pause the connection for a little bit, then we have some problems reconnecting or taking control again. The stability is a bit of an issue.

The scalability has been okay. We haven’t seen any issues there.

We have 200 people using the solution right now.

I’ve never dealt with technical support in the past. I can’t speak to how they would be if someone needs help.

The initial setup is very straightforward. It’s not overly complex or difficult.

The solution may be free to use. However, I’m not 100% sure on this.

I am a customer and end-user.

I’m not 100% sure which version of the solution we’re on.

The solution is mostly on-premises. However, we do use it on the cloud as well.

I’d advise users to go for it and try it out. It saves time for IT, allowing them to remote in from wherever they are. They don’t have to come to you. It makes troubleshooting simple.

I would rate the solution an eight out of ten.

I use TeamViewer for technical support remotely. 

The most valuable features of I use TeamViewer are the ease of access and frequent updates.

In a future release of TeamViewer, they should improve password access. Every time one of my clients access the free version of TeamViewer, the password changes and they cannot update the password. Even if the solution is provided for free, it should allow them to update or set the fixed password because it is very difficult to type the complicated password. 

I have been using TeamViewer for approximately three years.

TeamViewer is highly stable.

I have not contacted the support, I have not had any issue needing the support.

Positive

I use VMware Workspace ONE in parallel with TeamViewer.

The implementation of TeamViewer is simple. In terms of the configuration for the server, the IT team does it. I only need to install the client, which is very simple, but I don't know much about the backend configuration.

Usually out client does the configuration of TeamViewer on the backend.

For 100 TeamViewer users, we would need a team of 10 to manage the maintenance.

After trying free version, you can buy proper license. 

I evaluated VMware Workspace ONE before choosing TeamViewer. However, our company uses both for different purposes. We use VMware Workspace ONE for accessing company assets and we use TeamViewer to support some clients in some projects.

I rate TeamViewer a nine out of ten.

We primarily use the solution for remote access. We have been using TeamViewer for gaining access to the other systems.

TeamViewer can be used for gaining access to another system. By having the remote ID of their system we can completely access their system from TeamViewer. Mostly we have been using it for that purpose only.

It is very easy to check other solutions. 

It's very easy to learn how to use it, including the process and everything about it.

The solution is scalable. 

It's a straightforward setup.

The product can sometimes crash. The stability could be better.

Technical support could be improved.

I've been using the solution for a year or two.

The solution is mostly stable, although it sometimes crashes. 

I'd rate the scalability at a seven out of ten. Sometimes I have faced issues with adapting, to gaining a new acquisition. I haven't been using the latest version, so it might be improved. Also, it is now cloud-based. It may have grown in scalability.

We have 20 to 25 users on the solution. 

We've used technical support once or twice. I have faced issues with the TeamViewer application. I have tried contacting the technical support, however, on the first attempt, I didn't get any response so I had to call and call them again. They said that there have been some errors going on with their server and they were affected at that time. They have increased rates. For most users, it means, hopefully, that they have to get more technical support. Their support team might also be increased.

We have some people who are using AnyDesk. Most of the people in our company are using this. It's likely 100 to 150 people. TeamViewer gave us issues, which is why we switched to AnyDesk.

The product is really straightforward and completely easy to implement.

It took roughly two months to set up and deploy.

We have 14 engineers, however, we only need maybe three for deployment and maintenance. 

We were able to handle the initial setup ourselves. 

I am using the free version only. I've never had to buy their license.

I haven't updated it to the latest version.

Without having tried the latest version, I wouldn't recommend their solution completely. However, it is good. If on the current version it is still good to use, then I would recommend it completely to the others. I'd rate the solution eight out of ten.

The primary use case is remote support.

It saves trips to customer sites, which saves time. I am able to get in there remotely and fix things. Before having this tool, it involved having to touch the customer's PC, which required me to either talk to somebody on the phone through doing the process or go out to the customer's locations and install it myself.

I can grant permission to my organization so a person must be signed into TeamViewer if they're a member of my organization in order to be able to access that machine. In the event that a customer needs access, I can go ahead and define a policy either at an individual machine level for an individual user that we create, or we could conversely say somebody in the company needs to access all machines, which is great. We can go ahead and add that user to the access policy for all machines, so it is definitely robust like that.

It works well on a Linux laptop or desktop. Linux support has been huge for me because that is what I use for my computer systems. To be able to have something which works properly on the operating system that I prefer is great. I like to use the remote file transfer on occasion, but the remote desktop access is my number one most used feature.

It has good multi-tenant support. As an IT service provider, it has the configuration options required to make it work well across multiple customers, as it is highly configurable.

Its branding has been valuable for me.

Since TeamViewer version 13 introduced a Native Linux rather than running the Windows version through an emulation layer, that has been great. However, certain features didn't make it into the initial two releases. So far, the Linux version no longer has support for meetings. It wasn't a feature, and very often a group that we put together recently was looking for a way to do online meetings. I thought, "I have a subscription to TeamViewer that includes that." I do, but that function no longer works in Linux version. I am sort of waiting for that to come back. 

Support for mobile devices from Linux has been missing since the Native client was rolled out. This was a nice option, especially when trying to walk somebody who was struggling to understand something on their phone. I don't do a whole lot of support for mobile devices, but if I could just direct them to the Google Play Store to go grab the TeamViewer app, they could give me a number to connect to and I could see the screen with them.

I'm very grateful that there is a Native Linux client. That is a step forward and in the right direction. It shows TeamViewer's commitment to the Linux platform. I am very pleased about it, but there are some things that I used to have when the Linux version was just the Windows version packaged with the necessary emulation layers to make it work. I miss some of those features which used to be there prior to the Native Linux version. Hopefully, they will make it back into the product in the not too distant future.

It would be nice to see some of those other features that we used to have come back, using them on Windows and Mac.

I can no longer connect via web links, which is not the end of the world, but it's a mild annoyance. I used to be able to click something from my browser, then boom, there you go. At the time, it was the old TeamViewer that was based on the Windows software. I had to take some initial steps to configure an environment where those links worked, but once Linux was up, it was no different than on Windows. I could be on the web or in a remote monitoring platform, and if I needed to connect with one of my client devices. I would select from there, and say, "Connect to TeamViewer," and it would jump right in. I can't do that anymore.

The product and platform work well. That is why I have stay with them so long. The stability has typically been good.

Scalability is hard to say, because I am the lowest scaled out degree of utilization. The clients that I use it on are relatively small. I am the only person using the tool at my company, as the founding member.

I am using it fairly extensively. It is on almost every customer computer that I support. Anyone who has a maintenance agreement with me will have a copy of it. At this time, that is under 100 customers.

I have done work for people who have used it in larger environments: Hundreds upon hundreds of teams running it. So, I have seen it perform well in a huge environment. I have seen it perform well in a large, multitenant environment. 

I try to go to the TeamViewer forums before contacting their technical support. My interactions with the technical support has always positive.

The improvements since the Native release of the Linux version have been great. They have been good about addressing the most critical issues first. There was one that left many of us that work on Linux and support Windows machines, particularly in enterprise environments, having to press Control-Alt-Delete to log into a system. When the Linux client first came out, there was no way to send Control-Alt-Delete. How do you miss something that important? They were actually very quick in getting that fixed and rolling out a version that supported that.

They have been doing some support for ARM, which is sort of cool. That is the chip that runs the Raspberry Pi. While I don't know if it is all ARM devices, specifically Raspberry Pi support for Linux is something that you can get from TeamViewer, which is beneficial.

With Raspberry Pi out there with TeamViewer on it, you are not having to kick somebody at the customer site off of their computer in order to get access to a desktop, then fire up a browser to look at somethings locally. Therefore, it is nice to see support for it out there.

I came to be familiar with TeamViewer when I was trying to find a way to access Take Control from Linux. Instead, I found out it could be done with TeamViewer. That is what made me aware of TeamViewer and made me discover firsthand that it was a great solution. 

I didn't replace another service. While I have used other technologies in the past, like VNC, they don't do exactly what TeamViewer does. If you wanted to use VNC remotely, you'd need to get your traffic through the firewall and take care of securing or encrypting that traffic yourself. Thus, it is not really in the same league of software. You have to bring your own security. With TeamViewer, you are encrypted out-of-the-box.

The initial setup was straightforward. I use the corporate plan now and have the installer pushed from my remote monitoring platform, so it's ridiculously simple these days.

Nowadays, the installation happens automatically, so it doesn't take any time at all. Basically, when I put my remote monitoring and management tool on the customer machine, it takes care of pulling it down, setting it up, and joining it to my account all on its own.

You can easily deploy a Raspberry Pi with Linux on it at a customer site with TeamViewer on it. Now, you have a machine at a customer site that you can get on it if you needed to use a web browser to look at things on the network, like a printer scanner, or multi function device interface. If your security policy was so you could only manage the firewall from inside of the LAN, then I tend to have some other methods for keeping the firewall secure. Still, this is something where there is a real value-add to it.

I don't have good numbers due to the small sample size.

The pricing and licensing are sort of high. Having been an early adopter of the subscription model, and primarily because version 11 was the last licensed version that I owned, when I was looking at 12, I was also looking at upgrading to corporate. I called TeamViewer sales and talked with them. At that point, subscription was a relatively new option. It was not even mentioned on the website at that time. However, it was pretty easy for me to look at my historical TeamViewer purchases in my accounting software and see that I was buying a new TeamViewer license every time a new version came out. So, switching to a subscription model wasn't going to be anything different than what I was already doing, so renewing the subscription every year was not any different than buying the upgraded version every year. There was good incentive to move from the middle tier to the corporate tier.

LogMeIn started this rush to higher prices whenever they got bought out and chopping off lower-end tiers. A lot of people in my industry had been using them for a long time. I never cared for their solution. I always thought it felt clunky and didn't think it worked well, but plenty of people did like it. I don't know if it was the pricing that was the primary draw, or what, but there were many people in my industry who were leaving LogMeIn after their 400 percent price hikes.

Take the time to learn what TeamViewer can do. Take advantage of some of the features that it offers. Learn some of the best ways to leverage its capabilities.

I have some Linux test virtual machines that I do connect to using TeamViewer. In the past, I connected to Android devices, but that functionality is currently missing from Linux.

TeamViewer had some negative press a few years back when some people had their accounts breached. TeamViewer was being used by bad actors to commit malicious acts on people's PCs, but that was not TeamViewer's fault. It was bad implementation by users. Despite the fact it wasn't TeamViewer's fault, TeamViewer still went above their obligation and helped make it easier for people to properly secure their accounts. I think they did a great job with that.

Increased TeamViewer usage would be hand-in-hand with increasing our customer base, so I both want and need a bigger customer base. Part of my standard support software stack is TeamViewer, so every new customer PC device which is added to the support contract would be one more deployment of a TeamViewer Host. So, I definitely plan to increase TeamViewer deployment.