TeamViewer Reviews

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.

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 biggest advantage of TeamViewer is the way you can send files. For example, if you need to program something or exchange pictures, it's not that easy to to send a document to a secure network, like Boeing or a military company. Sometimes, sites even block all the Internet and you need to do everything by telephone. With TeamViewer, the main advantage is you can send files and documents easily. 

Another thing is you have sound, in the sense, you can hear. For example, we are playing short trailers, and you can hear it on the distant computer. This is useful to see if the sound is working. We will play trailers and see the image, but the customer will sometimes complain, "Hey, everything is good, but I don't have sound." With TeamViewer, I can hear the sound, not from my computer, but from his computer. This is super cool.

The chat function is handy, especially when we are dealing with people who don't have telephones in their projection rooms, or it's super noisy. Then, the chat is very useful.

Another feature that I like very much is the option where you can save the username and password. Once this is done, all you need to do is double click on the computer. It will connect directly. You don't need to type the password every time. This saves time because you cannot remember a dozen of passwords. You need to go somewhere and find them. But with this feature, you put them in once. Then, every time you are connected to particular sites, you just double click. There is almost no need for a repository for those passwords.

You can reboot remote computers with a feature called "Wait for Partner", so you don't need to monitor it. TeamViewer will pop up a little window when the client is back, saying, "Hey, I'm back online." You can work on something else, and if you need to reboot a computer, TeamViewer will notify you that the customer is back online. This is a nice feature.

You are limited with the regular TeamViewer. You have don't have sound. You cannot transfer things. It has been a long time (years) since I used the regular version.

In the beginning, you will need a bit of adaptation to use the solution. This is normal. For example, if you are switching to a car with the wheel on the left to a car with the wheel on the right, you will need a bit of adaptation.

Even now, we have customers who will not allow us to connect to them because of security sensitivity, e.g., military departments for clients. They will send us pictures or we can talk with somebody onsite, then we need to ask them questions. However, this process is long. It's costly also because of the time spent. Instead of spending 30 minutes, we will spend two to three hours for the same thing.

A feature that they could add is chat with sound to talk.

I have been using TeamViewer Business edition for six to seven years. I have been using the regular version for more than 10 years.

The product has been stable for many years; no glitches.

In the beginning, security was an issue because you could be hacked. Anybody could transfer data from your computer. Right now, from what I have seen and heard, they have put a lot of security in TeamViewer. It's very secure right now. Though, it is hard to be sure 100 percent all the time, especially in the movie industry. For anti-piracy and things like that, studios are very tricky and pushy to have tight security. The fact that they accept TeamViewer means they did tests trying to find security breaches, and everything has been good until now. 

There is not much maintenance need on our end as it is a lightweight program. The program upgrades itself.

We have a limited business license. We can have 10 people on it at the same time. We are doing support all over the world. With the version that we have, we are allowed to have 10 people using it at the same time. For example, because we are working with engineering of other groups, if we go over 10 users, the eleventh person who wants to use TeamViewer cannot.

We have about 1,000 clients. Our support team is six or seven guys, plus engineering. Though we are not all connected at the same time. For example, if five of us are support 1,000 clients, then individually, we are supporting 200 clients each.

We are sending out computers every day. So, we will probably double the solution in a couple of years. Right now, it's okay. There are some days when we need to ask somebody, "Close your session because we need another guy from engineering to connect." So, we will probably need more licenses in the future.

We never need tech support. We needed it once three years ago. We sent an email and had an answer almost immediately.

I used other solutions in the past, i.e., LogMeIn. At a certain point, we switched from LogMeIn to TeamViewer because LogMeIn was limited at 500 users.

It was a bit tricky because we had so many computers. We needed to generate IDs, passwords, and administrate passwords. We needed to have a machine to generate these, as this was sort of an additional software. We had thousands of computers, so we needed to have an ID, a password, and administrator password for each of them. So, we needed to have software to manually input this information in TeamViewer every time. Once we did that, it was perfect. 

We aren't launching all the computers at the same time. We are launching them one at a time. Today, we are doing a server. Then, tomorrow, we may put TeamViewer in two or three servers. It's not a single shot. It's gradual. To install TeamViewer takes five minutes on each device, maybe more time.

We contacted TeamViewer directly in Germany. We discussed the price and things like that. With TeamViewer, you go to the Internet. Everybody can do it. I can do it. My son can do it. You download the program. Then, if you switch from a normal to business license, all you need to do is just put your credentials in and the program will upgrade itself. It is very simple. All you need is the Internet.

We have solved a lot using TeamViewer. While I cannot quantify this in money, without TeamViewer, we would need to call everybody and work with 1,000 clients blindly. 

It is worth the money that you pay for it.

We have a corporate license. The maximum amount number of users changes based on the amount you pay. E.g., with our license, there is a maximum amount of users who can use the solution at the same time (10 users). 

The cost is in the thousands of dollars per year.

We have some sites with LogMeIn because it's a matter of politics. Some companies will not allow you to install TeamViewer. They will only allow you to install LogMeIn. Some others will not allow you to install any software like TeamViewer, LogMeIn, or others. Therefore, you need to go buy a remote desktop (RDP).

For sites that do not allow us to install TeamViewer, LogMeIn, or other software, we use Cisco VPN. This requires a lot of software to install. It needs to run a program through it. You need some administrative passwords that need to be typed every time. It's a lot of security. In the beginning, you don't have sound from the other computer, and it's hard to transport files.

While we use LogMeIn and remote desktop, in 99 percent of the cases, we are using TeamViewer. TeamViewer is very easy to deploy when you have a corporate license. It's easy to install. It's upgrading all the time. Everything is perfect, as long as you pay.

Screen resolution is a huge advantage of TeamViewer over LogMeIn. We have clients with multiple screens. For example, if the client has three screens, when you are connected, you will be on one screen and don't know which one. With TeamViewer, you have a selection. You can select moving from screen number one to two or screen two to three. You can also put all the screens into an all in one or see the best fit.

It is easy to use, but LogMeIn is also easy to use.

It is a great, amazing tool. All companies needs to have it. It's secure, fast, and reliable. 

In the beginning, you need to understand the features, e.g., what a button does. Once you get all of that, it's very easy to use. I'm a heavy consumer of TeamViewer, a sort of professional of it, so I know all the features. But, even for somebody seeing it for the first time, it is very easy to use.

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.

Remote desktop control is what we use in TeamViewer for 99.999 percent of what we do. 

We occasionally use the integrated text chat. There are circumstances we've seen where certain applications don't respond because they've got some sort of security built into them so that a remote user isn't able to control them. We can log in with TeamViewer, view the screen, and then leave instructions in the text chat that say, "Okay, please do this. Now, please do this. Now, please do that." We can actually guide the client through what they need to do, even for applications that don't allow a remote-control user to modify them.

The other thing that we're beginning to use more is the feature where, at the end of each session, you can type a quick note as to why you were logging in to that device. We've started putting in notes saying things like, "I went in to update Windows software," or, "I went in to fix a bug," or, "I went in to update our own software." We have not gone to the next step of reporting on, analyzing, reviewing, or using those comments as a way to drive additional follow-up. But it does at least give us the first step so that if somebody says, "Hey, why were you in my machine?" we can produce documentation that says why.

The TeamViewer system has some built-in security. The TeamViewer client connects to the TeamViewer host securely. Only a certain number of authorized users on our side have access to the system. Even within that, an individual endpoint can be assigned to a group, where not everybody has access but, rather, just one or two people who are part of a support team might have access to that particular device. So TeamViewer has given us tools to be able to segregate who has access to different things. That's been pretty helpful in dealing with some of our clients who have more "buttoned-up" security. They're able to say: "These two people have access to the devices." We have designated support people for that client who can go into their device and nobody else can even see that the device exists. That's really helpful.

The remote connection process is totally simple. It's as easy as it comes. We do install the software on field devices, but we also have TeamViewer's widget on our website. So, if you go to the support page on our website, you can click a link and download a white-labeled TeamViewer app that pops up and gives you a service key that you can fill in. That's an interesting tool. It makes it easier for customers who are not one of our owned assets to quickly download and light up a TeamViewer session so that we can help them with software configuration updates. Sometimes it's not even things that are our problem, but they don't know who else to call, so they call us.

I find it pretty easy to use. They redesigned the interface a while ago, and, honestly, when I first looked at it, it seemed sort of clumsy, but, now that I've gotten used to it, it's pretty darn easy. At first, everything was totally different. Doing simple things that I used to do, like connecting to a certain device, went from being obvious to a situation where there were just so many more features available that I had to click through to find the simple thing that I was trying to do.

In addition, and I don't know if it's TeamViewer's problem or not, I do find that sometimes we'll have a device in the field, and I'll click on remote control and it says "Can't authenticate." I'll double click in a different part of the TeamViewer interface and it'll say "Can't authenticate." Then I'll do it a third time and it connects. It's possible that it's just bad luck. It's also very possible that it's some bug within TeamViewer so that with the first click I'm waking up the TeamViewer connection, and with the second click I'm starting the connection but it's taking a long time because it's in a bad cell zone. Then, the third time, it's working because finally the thing is awake and recognized and is passing everything through. It may have nothing to do with TeamViewer, or it may be a TeamViewer issue. I don't know. That's the only thing I've really noticed that is problematic from our perspective. We'll see a device, we'll see it's online and that it should be available, but when we try to connect it doesn't connect. So that's a challenge.

In terms of additional features, the more TeamViewer can work with, and on, different devices, that would be helpful. We're doing some R&D with Cisco for some modems that have an IOx, which is a Unix-based compute area. If we could control that device using TeamViewer, that would be cool because, otherwise, we have to buy a Cisco cloud management software system to monitor those devices; similar to the Cradle Point. I'm not aware of any sort of onboard storage where we could install TeamViewer on a Cradlepoint, but if that is the case, then they should let people know about it because that would be a useful tool.

One of the things that would be a cool feature, and I'm not sure how TeamViewer could make it happen, would be to take an ad hoc TeamViewer session from our support website and, in the course of that, install the TeamViewer host, so that a client device would then become part of our network of machines we can get to relatively easily. That would be a huge time and energy saver. One of the things we find is that there will be a device and the users of that device have to use our software from time to time, but they don't use it often enough to really be good at it. So each time they use it, they go back through the learning-curve process. If we were able to quickly jump on their machine and walk them through what to do and how to do it, that would make it easier for them and easier for us.

We've been using TeamViewer for four or five years. We started out on version 8 and we're up to 15 now.

The stability has been very good with the possible exception, as I mentioned earlier, of that three-clicks-to-connect issue, which seems to come and go. My guess is that it's something related to our devices being on cellular connections in areas with really bad cell service. But I've noticed it typically occurs when there's either a Windows update or a TeamViewer update, so it makes me wonder if maybe Microsoft introduces some sort of incompatibility that screws up TeamViewer and then there's a TeamViewer update that fixes it. We just have to remember to keep TeamViewer up to date on all of our clients in the field.

We only manage 30 devices. I could see, if we had a thousand devices, that the management part might become a little more complicated. Given that you can separate different devices into groups, and you can give different people access to different groups, it might be relatively straightforward. Huge scalability isn't something that we've had to deal with yet.

The monitoring, asset management, and endpoint protection are things we just haven't had the time or the mental energy to test. If they work as advertised, those seem like they'd be great features for simplifying remote management. In terms of expanding use of TeamViewer, those are next on the list. 

We'll be looking at endpoint protection; the patch-management and device health monitoring. Those are things we're very interested in. We want to do them to see how much, if any, additional CPU load and communication load is put on the device. We are a little concerned that we're going to clog up these fairly lightweight devices out in the field with a lot of administrative overhead instead of leaving them to do what they're supposed to do. We would probably do one or two as a test, just to see how it goes, and then start to crank it up. We have about 30 devices in the field that we monitor with TeamViewer; it's not like we've got tens of thousands.

We have used technical support very sparingly, but when we've used it they've been great. They are very responsive, very knowledgeable, and they typically resolve our issue with one or two calls.

We actually initially started using it because we're based on the east coast in Boston and Washington, D.C. and we had a client in Chicago who had our software on a number of devices. He wanted those computers to be someone else's problem, namely our problem. He asked us to have some sort of solution in place so that we could quickly visit the computer, check that everything was working, upload Windows updates, upload software updates for our software — whatever was needed to make sure that they were happy and healthy, including rebooting them from time to time. That's how we started with TeamViewer. Since then, more and more machines have been added to the list; some with this client and some with other clients. We found it so easy with that first client that we wondered why in the world we weren't using it with everybody else.

We find the initial setup of TeamViewer very straightforward, but not everybody finds it as straightforward as we do. It takes minutes. Deploying TeamViewer is incredibly easy.

I don't really have a firm answer for how many end-users can now be supported with one support person, versus how many could be supported in the past. We didn't really have a pre-existing field support organization. But it's very clear that by using TeamViewer and not needing to go do field views visits, that we're a million times more productive. The eight hours of travel that might've been part of a field visit to go help one customer now become eight productive hours that you can be helping other customers or doing other things.

A lot of the TeamViewer stuff is done by people who do technical support for sales or technical support for core development. If they can quickly pop into a user's computer, check something out, fix something for them, and go back to their work, they get a lot more development work done than if they have to get in a car and drive somewhere or get on a plane and fly somewhere to do that same look at the client's setup and what needs to be fixed.

If you take a $100,000-a-year employee and enable him to spend 20 minutes per service call instead of eight hours per service call, that's a pretty darn impressive return.

TeamViewer is a great value. We obviously wish it was less expensive because we want everything to be free all the time. But we do recognize that sometimes you have to pay for things, just like we try to convince our clients that they should pay for our software. 

TeamViewer is $600 or $700 per port per year, which we find that to be just fine. If we paid $100 per port per year we'd be happier, but we're very happy with the quality of the service and the capabilities that gives us. So it's been a great value for us.

I could go look up how many TeamViewer sessions we do per year, how many where we couldn't get the information through some other method, but that's where it becomes complicated to say specifically what the ROI is. 

It's clear that it's a valuable product. 

It's probably not valuable for everyone because there might be people who've got devices or systems where they have to hear it or smell it running to be able to diagnose what's going on. That's not really TeamViewer's strength. Its strength is getting visibility into a remote desktop, at least as far as we know, so that you can diagnose and treat a computer issue.

We've used a LogMeIn and there was something else that we've used, a solution that a partner of ours used which we tried for a while. TeamViewer seems to be a much more complete, stable, and reliable solution.

It's hard to make comparisons because it's been so long since I used LogMeIn. Longer ago than that, I used to use a VNC product that conceptually did the same stuff: gave me remote access to desktops. That was clunky, but it was probably as good as could be expected given the tools at the time. 

As a user who has been given remote support access via LogMeIn, what people have done with LogMeIn's help function seems easier than what we do with TeamViewer. That may be entirely because we're not organized well enough in our TeamViewer implementation to be doing it the right way. I certainly don't want to bash TeamViewer's capabilities, because I think it's more likely that we just don't know all the things we could do.

With LogMeIn Rescue, the technician gives you an ID number. You put the ID number in and they're in your computer. And TeamViewer can probably do the same thing. I just haven't gone through the process of learning how to make that happen. The way we do it via our website is that you click a link, you download something, it pops open, it gives you an ID, the person then tells you the ID, then you're in. It's a couple of extra steps, rather than just being a web browser access.

If somebody asks me what I recommend for remote support, I always recommend TeamViewer. If they say, "I use LogMeIn, and I love it," I wouldn't be surprised. I've been a user of LogMeIn's remote support, and it seems like a pretty effective and easy-to-use tool. I'm sure the market is big enough for more than two players, but we're pretty comfortably ensconced with TeamViewer as our solution.

Do it. It's outstanding. It's very simple. We love it.

TeamViewer has a lot of additional features. They do audio and even video chat through TeamViewer. They do patch management, asset control, and all sorts of other things and we've actually thought about some of those other services, but we haven't taken the plunge yet.

We have not integrated TeamViewer with a single sign-on application. We actually use the TeamViewer host as often as we can on our remote devices. The device in the field is always on and always connected, and the people on our side who need to log in and access those devices will use the standard TeamViewer authentication process, which is pretty thorough. It's a username and password and it has a visual Captcha and then, when you register a device, it also emails and says, "Hey, we saw that you just signed in on this device from this location. Is that you?" They know what they're doing.

The idea of using TeamViewer for 5G deployments and smart poles with IoT devices is potentially interesting because we have a lot of Cradlepoint modems out in the field and Cradlepoint has a cloud management console. If it would be possible for us to use TeamViewer to access and manage those devices, that would be interesting because we pay $80 a year per device for the license in the Cradlepoint console.

In terms of end-users of TeamViewer in our company, we only have three ports and we have five or six usernames. There are three or four guys who do most of the work, remoting into various devices and rooting around to see if they can fix something or if there are things that need to be fixed.

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.

Every now and then I will do remote training with it. Those features are quite good.

Overall, it's pretty simple and pretty straightforward, and that's one of the things that I like about it. It's also fairly light on the client's end because, most of the time, when I'm phoning a client, they're not technically strong at all. They need something that's just absolutely dead-simple to install.

That's one of the reasons why I went with TeamViewer over some of the other technologies I was looking at. Ease of use was the number-one thing. It's an industry leader for ease of use, specifically on the client-side, which is the absolutely critical thing. If I want to connect to somebody, how easily can I — without seeing their computer — walk them through the steps to install it to a point where I can key in the code and help them resolve their situation? People are phoning because they're already panicked about something to do with technology. If I have something else that's technologically challenging that they have to do before I can help them, that exacerbates the situation rather than helping it. TeamViewer is just a dead-solid, easy answer.

TeamViewer also has great support for multi-monitor. I can have a whack of connections open at the same time.

Speed and performance have been addressed. I know there was a security blip a few years ago and they now do the extra authentication, which I appreciate and clients appreciate.

I haven't had the contact TeamViewer in so long. When I originally started with TeamViewer, they didn't prompt the user to log the details of the connection. You'd have to manually go back into the TeamViewer Manager and log your comment, after you had closed it. Then you'd go back into TeamViewer, go to that connection and assign a comment to it, which I would sometimes forget to do, especially if I was jumping from call to call to call. I sent in a feature request asking them to add the prompts and I'm sure other people sent in the same feature request. They did that many years ago.

I have been using TeamViewer since version 5, so it would have been the first month or week that I started my business, which would be seven or eight years ago.

The stability has been very good to excellent. Every now and then you'll get a silent crash and you relaunch the application. But it happens no more than with anything else in the Windows environment.

It has organizational tools and it's nicely scalable. If I grew the business to 30 or 50 people, consultants, it would still be an excellent solution.

The only time I'd need to expand the technology is if I hire. If I hire another person, I likely wouldn't even increase the channel usage right away because it's based on concurrent usage. Joanne is an intermittent user, so we're not looking for anything extra right now.

There is TeamViewer's ITbrain that we could look into more but, again, it's not really something that we do. I stay in my lane with the accounting software. I'm not looking to manage my clients' IT infrastructure or to manage their PCs. If I see something that's out of the ordinary, 90 percent of my clients are going to have an IT person who handles that side of things. I handle anything that has to do with inventory and accounts receivable, and general ledgers, and debits and credits, and accounting software. Anything that touches on those things, then I'm in. But if they're having problems with their computers running slowly, I refer that out.

The few times I've had to use technical support, it's been fine.

Very briefly, in the first three weeks of the business, there was another tool that I used. Then I used TeamViewer and I've never stopped. I can't remember what that other tool was called. It was more of a standalone kind of product. It was cheaper than TeamViewer.

I switched because TeamViewer was robust. I also felt safer. I was going to be installing the program at clients' places and I didn't want to introduce anything that might be difficult. It is easy to use for clients. Although I've got it installed on my network of eight or nine machines, I have connections to hundreds and hundreds of other computers — some 500 other computers at my clients. I wanted to make sure I was installing something that was not taking up too much memory on their machines, that was stable and secure. I didn't want something that was at all suspect. I wanted solid and robust.

The initial setup was quite straightforward. It just needed to be installed on five or six machines inside the domain, and on a couple of machines at home. I then continued to roll it out to clients and through links to it in my email signature. Deploying TeamViewer across the various environments was really straight forward and easy. There was no implementation strategy required. 

The only thing I had to watch for was if my clients were already using TeamViewer or if they had another company that does not have a certain version of TeamViewer. Suppose I have a client which uses an IT company to handle their network infrastructure and computers, and that company has TeamViewer 11 or 12, while I have TeamViewer 14. I have to be careful to make sure that the client is always installing TeamViewer 11 or 12 — whatever version they have. One of the things I find that is really easy about it is that, with TeamViewer 14, I can connect to any older version. But you can't connect to a newer version from an older license. If somebody is using TeamViewer 12 and, for whatever reason, they haven't renewed their license, they can't connect to TeamViewer 14 installations. I have to remember to play nice if somebody has a limitation like that.

But for me, it's just dead-simple. The client installs the most current version and I'm off to the races. That's one of the reasons why I pay them money every year. Deployment takes ten minutes per machine. I call them "gravity installs." Next, next, next, next, next.

And I'm the only one who maintains it.

It's inefficient to travel. Without any remote support solution, if I drive out to a client, do some work, and drive back, I have the prep time and the clean-up time. I have to get gas in the car. There are all those overhead things. I go out, do three hours of billing, and charge for an hour of travel time. But it really takes most of the day. But with some kind of remote support solution, I can be concurrently overlapping my billing. If I've got a busy day on TeamViewer, for example, I can end an eight-hour day with 12 hours of billing, easily. Comparing those cases — no solution versus having a remote support solution — the ROI could be $50,000.

But compared to if I had a different remote solution in place, the efficiencies I've seen in TeamViewer, and the way that it traps things, would be saving me closer to $3,000.

If we're talking about a strict ROI, I would use the $50,000 number because there'd be ROI with that competing product as well. It allows me to be 20 percent more efficient.

Before implementing TeamViewer, I could support one person at a time over the telephone. After implementing TeamViewer, the most I've ever had were about ten connections at once. For practical purposes, it depends on your level of attention. You can be doing as many things as you want concurrently, and multiple billing if it's appropriate. But you're limited by your own attention span. I run with four large monitors on my desktop, so I've got the real estate. I can have little TeamViewer windows all over the place.

Every now and then, I hear people complain, "Oh, it's pretty expensive," because it will cost you $1,500 to $1,600 a year, but when I think of how much work I do through TeamViewer...

I looked at LogMeIn Rescue and PC Anywhere in addition to TeamViewer.

At the time, TeamViewer was a version license, whereas LogMeIn was a subscription. But one of the big things that really drove me to TeamViewer was seeing how much of the resources it was using on a computer. I installed both solutions and looked at them from the point of view of the client. I looked at the resource usage when they were running and the performance. That's what sold me: the interface and the performance.

The biggest lesson that I've learned from using TeamViewer is probably the ROI lesson. I used to work for another company and I ended up buying the client list from them. There was not a lot of remote support happening at the time. In fact, I helped them usher in the remote support era, but they were still very much on a drive-out-to-the-client paradigm. It used to drive the boss crazy when he'd see me sitting in the office a lot. He always thought sitting in the office was a bad thing. Then he looked at the billings and found my billings were way higher than anybody else's. He would ask, "Why are you in the office so much?" The biggest thing is I learned that sometimes there are better paradigms for work. It's more efficient. It's better for the client and it's better for me. If I have a client who has an issue, I could drive out there, answer three questions, drive back, and send them a bill for a minimum one hour on-site and a minimum for travel charges. Or I can remote-in, connect, solve a problem, log off, and they know that they're getting a bill for 15 minutes. It's way better. There are ways to be efficient. Work smarter, not harder.

If you're looking to implement TeamViewer, just point to the website and go download it.

I install it all on-premise. When I'm working with a client, if they don't have TeamViewer installed, I'll just walk them through very quickly installing TeamViewer on their session and then remotely connect to them, attach, and help them with whatever their problem-du-jour is.

My users use it almost exclusively on Windows PCs. I have connected to a Mac probably one or two times in about eight years, and I have connected from my phone to a client twice. Because I'm working on ERP systems that work in the Windows environment, I don't have much cause to jump on to anything other than a Windows PC. The times that I have had to jump onto a Linux machine or a Mac, I found that the interface is consistent and it doesn't present any problems.

We have three people using it in the organization. We're a small company. Their roles are report developer, administration, and tech support. I'm the support team. The company is me, my wife, and my sister. My wife does the administration and the billings. She uses TeamViewer to view the connection logs and see what she should be charging. My sister uses it, as our Crystal Reports developer, to upload reports to the client, making sure that things are configured correctly and adjusting reports. She's remotely attaching with no intervention from the client's side. I do everything in between. I will phone the client, connect, do training remotely, remote support. I'll upload programs or do troubleshooting. I also do a blend of "guided," where the client is on the other end and is watching what I'm doing. I also use it after-hours where the client's not involved. It solves both of those things. We're a small organization, but it definitely serves our needs.

TeamViewer has matured nicely over the seven or eight upgrades. Now, I just expect them to be doing performance and security. It's got the full feature set that I'm looking for. But computers are complicated ecosystems with tons of challenges, so I just expect that they're going to continue paddling beneath the surface. I don't care if I don't see a lot of extra bells and whistles, I just want to know that it's still secure and fast and doing things the right way.

It's feature-rich and easy to use. It's an excellent product. It's a product that is really deeply integrated into our daily workflow.

Realistically, is there anything more that I would want from it? It does what it's supposed to do and it does it reliably. It would be unfair not to give it a ten out of ten.

The most valuable feature of TeamViewer Tensor is the remote access.

The solution could include more AI (Artificial Intelligence).

I have been using TeamViewer Tensor for four to five years.

I rate TeamViewer Tensor a nine out of ten for stability.

TeamViewer Tensor is a highly scalable solution. Most of our clients for TeamViewer Tensor are enterprise businesses.

I rate TeamViewer Tensor ten out of ten for scalability.

I rate TeamViewer Tensor a nine out of ten for the ease of its initial setup.

The solution’s deployment took a few minutes.

I am working with the latest version of TeamViewer Tensor. I would recommend TeamViewer Tensor to other users.

Overall, I rate TeamViewer Tensor a nine out of ten.

The most valuable feature has been the ability to give control to others for support purposes.

This solution could be improved by offering more flexibility in terms of usage.

I have been using this solution for three years. 

This is a stable solution. 

This is a scalable solution.

We have received good support from the customer service team although at times we have waited a long time in the queue. 

Neutral

The initial setup is simple and straightforward.

We use a paid version. The free version has some limitations and you're not able to make voice calls.

Not every solution is 100% and there's always room for improvement. 

I would rate this solution a nine out of ten. 

The technical support team assists with TeamViewer and performs repairs and installations remotely.

I like that it is simple to set up.

It needs to have proper authentication.

I would like to see in-depth integration with Google and Microsoft products, for example. It would be nice to have a cell phone version as well.

I would like to see the addition of mini storage. What I do in one session should be in the records so that I can recall it. It would be nice to see the last 10 sessions. That is, I would like to see a chat board.

I've been using this solution for about six years. I use the desktop version.

TeamViewer is stable.

It is scalable. We have more than 20 users in our company.

The initial setup is simple.

I would rate this solution at nine on a scale from one to ten.

Most of the time, I use TeamViewer. There was some remote work to be done at the time.

We use TeamViewer for remote access. The login uses a key to gain remote control of someone else's desktop.

From my perspective, the most important is the login. That's the most important because you need that key, and everything else.

In my opinion, the user interface is good.

When the application is minimized I often close it in error.

When the application is minimized, I frequently close it by accident, but I'm not sure why; perhaps there is a way to improve the stability of TeamViewer with the minimize or close or not to close it accidentally, and then you must reconnect, and so on.

Unfortunately, I don't know what additional features I would like to see included right now. I only use the main functionality, and it's fine for me the way it is now. I can't think of any new features right now.

I would like to see something like a TeamViewer mobile application for iOS or possibly Android. I think this would be fantastic given how technology is evolving today. It would be beneficial to use it with your smartphone.

I have been working with TeamViewer for a couple of years. I still use it when it is needed.

There are some issues with the stability of TeamViewer.

I would rate the stability a seven out of ten.

TeamViewer is easy to scale. It is a scalable solution.

We have two or three users in my department.

I have not contacted technical support.

I stopped using SmartBear, and TestComplete Mobile a year ago. That was a requirement at the company where I now work. I am currently assigned to another project and don't use TestComplete.

I am familiar with GitLab, but with limited experience. I don't have much experience with GitLab. I last worked with GitLab six months ago.

I am currently using some companies in specific test tools. We are developing some test tools at the company where I work, and this was one of them. In the past, I used Selenium mostly for web applications and some other dedicated desktop test tools, but that was also in the past.

I worked with SeleniumHQ a few years ago. Now I only work with dedicated test tools.

In this company, I only wrote a few JavaScript tests.

I have used a virtual machine in the past, but that is different from TeamViewer. I don't recall using another solution before TeamViewer.

From my perspective, the setup is simple enough. It is not complex.

I used the free version of TeamViewer.

I would recommend this solution to others who are interested in using it.

I would rate TeamViewer an eight out of ten.

We primarily use the solution for remote access.

I used it mostly for Cisco remote support activities.

It’s so great for when you need to provide remote support. It allows us to troubleshoot in real-time.

The configuration and structure are good.

It doesn’t break down easily.

The product installs easily.

It is stable and can scale well.

The dashboards they have are good.

The solution isn’t expensive at all.

I don’t see any areas where improvement is needed. It’s been helpful overall.

I’ve been using the solution for two or three years.

It’s a stable product. It is reliable. There are no bugs or glitches, and it doesn’t crash on me.

I’ve never had any issues with scaling the solution.

About three or four people use the solution in my organization. While we don’t have plans to increase usage, we might down the line.

We’ve never really contacted technical support. I can’t really speak to how helpful they are as I don’t have much experience with them.

The solution offers a very easy initial setup. It’s not complex at all.

The licensing on offer is reasonable.

I would recommend the solution to others. I’ve used it a lot and found it to be helpful.

I’d rate it eight out of ten.

We use TeamViewer to offer remote help to customers and colleagues. 

I have been using this solution for about three years.

The solution is very stable. We've never had a problem with it.

Scaling this solution is very easy. There are currently more than 200 users of this solution at my company. 

The initial setup is straightforward and only took about five to ten minutes. On a scale of one to five, one being the worst and five being the best, I would give the setup process a five. 

I would rate this solution as a ten out of ten.