TeamViewer Reviews

My primary use case for TeamViewer is all of my remote support. I use it throughout the organization for remotely supporting my accounting customers. I have a number of clients who use different ERP systems that I support and I use TeamViewer to connect to their computers, resolve issues, do work after hours, and provide remote training, etc. 

I don't use a lot of any of their managed alerts or any of that kind of thing cause I'm on the intersection between IT and finance. But I'm definitely using it quite frequently, and I'm using it to generate billing as well through the TeamViewer logs.

I don't deviate a lot from the very standard usage. It's along the lines of, "Oh, a client is phoning." I answer the phone, connect to them remotely, resolve their issue, document what I did, and on I go. We don't use a lot of the sophisticated features of TeamViewer. We do programming, data repair, development, and troubleshooting, but as far as TeamViewer goes, we don't get fancy with it. We just want to make sure that we serve the client and then get paid for it.

With billing, when I initially started with TeamViewer, there was no automatic prompt for logging the details of the connection. Now, it has streamlined my process because every time I close a connection, there's an automatic window that pops up asking me what I've done. So immediately Joanne, who does the billing, is able to take that information and turn it into an invoice automatically, unless she has a question about it. It ensures that I'm capturing more of my work, so things don't get missed. It does that for me quite well.

That feature is saving me one or two hours on a weekly basis, but it's also ensuring that I'm not missing any connections. If I had two hours of missed connections, I would miss $250, so it's ensuring that I'm billing that $250 a week that might otherwise get missed.

We are in the commercial cinema theater business, like movies. We have things like simulators, advertising in commercial theaters all over the world. They sometimes have technical issues. So, we connect to see what is going on.

We use TeamViewer on computers, like laptops and servers. We also have tablets, but only one or two. Whereas, we have like 1,000 Windows Servers.

The sound and data transfer have improved the way our organization functions. For example, you can leave a TeamViewer application open and hear if a movie is playing with sound.

With an image, you can see immediately what's going on. You can run some tests. Without the solution, you need to do everything by telephone. It's not even thinkable. You would need to have VPNs with a lot of connections and virtual servers. This is so much more complicated. Weekly, we are saving dozens of hours using TeamViewer.

The remote connection process is pretty straightforward. Every new computer has a TeamViewer ID and password. 

The primary use case is getting access to various test machines from one location.

AirTies makes smart WiFi technology which end up in people's homes. I set it up in a house with WiFi devices. We test our Extenders and gateways with a bunch of clients using TeamViewer. I can access the clients to view the data being collected or what's connecting to wired ports. I do this locally, and sometimes, I access the home office in Istanbul.

It is used on a mix of Mac and Windows machines. Even though we have Android and iOS devices to test for WiFi devices, we haven't put TeamViewer on them yet.

We have a lot of IOT devices, but we haven't used TeamViewer that much manage them or get to them. While I'm open to it, I'm not sure of the roadmap for the rest of the QA team.

We can get machines logged off and check statuses of what's going on a lot easier. Otherwise, you need to track things in the office or wait for someone to be online in Istanbul, which is a bit tough because Istanbul is eight hours ahead of us. 

I've had coworkers who have done remote debugging. So, they ask a client to install TeamViewer so they can access their network from our office and help them troubleshoot problems in the field. In these cases, it is more of a support type role offered.

We use TeamViewer's infrastructure. We have TeamViewer host clients running on devices, some wired in offices, some connected to WiFi or even cellular, and we use it to get quick access to the devices for technical support.

The other use case, which is a little bit weird, is that all of our clients are in healthcare so they are very particular about who gets into their network and who has access to their network. What we've found is that when a client has our company's software on one of the servers in their network, sometimes they don't want to give us access to their network to maintain our software. So whenever they have a problem with our software, we open a TeamViewer session from a desktop inside their network to our tech support group, and that person gives us access to the server so that we can maintain our software.

Again, that use case is a technical-support-type application, but it's a little bit different than us managing our own devices in the field. It is a tool that allows us to access our devices on somebody else's network under their supervision, without needing our own unfettered access. It makes it easier for IT security to approve us and it makes it easier for the client to get us in, particularly in circumstances where there's some urgency around that.

The vast majority of our users use TeamViewer on Windows machines. Some are desktops, some are tablets, and the latter range from a Surface Pro to a more substantial, military-ruggedized type of tablet.

The big benefit is that we can do things pretty quickly and easily, remotely. In many cases, we save a service visit to the field, which would otherwise require us to have a very large field service force or we would need to pay for and train somebody else's field service force. Quite literally, without TeamViewer's capabilities, we wouldn't be able to run our business.

We use it for remote access to other machines. That was the main reason why we bought it. It is for our help desk and support guys to access remote users' machines.

Our users have it on their laptops. We can also do a bit of remote support for Apple devices, but it is basically a screen share. You can just see their screen. You can't manipulate anything, but you can see what they are looking at on their screens. Therefore, it's mostly for laptops, desktop machines, and the PC environment.

It is mostly for the regular support, for anybody who is having issues with a machine.

I use the solution quite a bit. I love it.

It provides efficiency, even if it is something as simple as just maintenance, something that is broken, adding something, a walk-through, or doing training. It is a great tool.

The remote connect process is super simple. As long as the user has an Internet connection and can get on the Internet somewhere, whether they are at home (on their WiFi), using portable Internet (Jetpack), or if they stop in a Starbucks to get on the Internet, I can connect to them. That is what is really convenient.

It was worth the investment. You can do file transfers and video calls with it. You can do a lot of copy paste stuff. E.g., if I have a file and want to place it on somebody's machine, I can just copy it off of mine and paste it right on their machine. I don't have to put it in a Dropbox account and have them log into it to pull it off. I can do all that right through TeamViewer. When you are looking at the TeamViewer screen, you think you are working on your own machine.

We use TeamViewer for support, controlling our ~2,500 end-user computers and our ~60 servers.  Our environment is primarily macOS, with about 95% of end-users on Macs, but our servers split between Windows and macOS.  We also have some digital signage devices that run Linux, and we use TeamViewer to control them as well.

We ran TeamViewer concurrently with LogMeIn for about year as we evaluated TeamViewer as a replacement.  TeamViewer's superior remote quality (especially in low-bandwidth situations) and ease of mass deployment, combined with LogMeIn's serious and longstanding bugs led us to recently discontinue LogMeIn in favor of TeamViewer.

Coming from LogMeIn, TeamViewer's remote control quality, Host reliability, file-transfer capabilities and ability to support multiple simultaneous controllers on a Host have been a great improvement.

TeamViewer's simultaneous-controller/tech licensing is better for us than LogMeIn's device-based licensing, because we don't have to worry as much about maintaining devices in the list as a driver of licensing costs.

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.

The use case is mainly PC and laptop support for our internal staff, where TeamViewer is distributed locally through Group Policy.  Occasionally, we will use it to assist clients having trouble with our services, and in those cases, we will send them a customized linked invitation through TeamViewer.

I have used it as a troubleshooting measure with remote people. With a quick glance at TeamViewer, we can say, "Hey, your machine is not reporting as being online or available. Therefore, check your Internet connection. Make sure you are connected to WiFi or Ethernet." Probably nine times out of ten, that's instantly what it is. We can instantly tell if computers are online or offline, then help in the troubleshooting process. We have set it up in such a way that IT will be on the call prior to the connection and that the person on the other end has to accept the connection. We want people to scrutinize and make sure that, "Okay, do I know this person? Why are they connecting?" and, they have to approve it. This is so they can recognize and be familiar with who we are . Also, the background changes to black, so they know when we are on their PC. Furthermore, we utilize two-factor authentication and other features for stricter security on the management side of TeamViewer.