The primary use case is remote support.
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.