TeamViewer Reviews

We are a digital marketing agency. If we need access to something in the Business Manager or in a Google Ad account, we can guide the client to do it, or we can control the screen from where we are to create something on the Business Manager or to edit something.

We are in Istanbul and Istanbul is a very big city. I save time since I no longer have to go to the client's office and edit items by myself. We can do it remotely via TeamViewer to save time.

The quality of the call and the quality of the sharing have been excellent. 

I love that I can control the other user's computer to find what I need or to assist them.

The deployment is simple. 

It is scalable. 

The performance is good. 

There is nothing that really needs improvement. 

I have noticed that when I access another person's computer, sometimes the tab is visible, and sometimes it is not, which can be difficult. It's a little glitch. 

I've used the solution for five or six years now. It's been a while. 

I have noticed some little glitches. That said, for the most part, it is stable. The performance is good. 

Also, sometimes it won't run smoothly the first time, however, the second time it will. 

The solution can scale well. 

We are a team of 11, however, only four to five of us use the solution. It's used occasionally, not extensively. 

I've never been in touch with technical support. 

We also use Microsoft Teams and Zoom, however, we use these for different purposes. 

We also use AnyDesk. I find TeamViewer easier and more user-friendly. The features are mostly the same on both. 

In general, we mostly work with Zoom, unless we have to control the client's computer. 

The solution is very simple to implement. In ten minutes I can have everything up and running. 

In terms of ease of setup, I would rate it four out of five. 

I handled the initial setup by myself. 

I do not handle the licensing aspect of the solution. My understanding is the pricing is reasonable. Everything is included in the price. There are no add-ons. 

We are customers and end-users.

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

I would recommend the solution to others to use. I'd rate it nine out of ten. 

Public Cloud

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.

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.

TeamViewer shows you what is on the desktop of the target machine.

The two features that I use the most are getting onto a desktop, so I can access it, and File Transfer. Quite often, we need put new firmware out there across the network or I need to get logs from a device. So, I log into different PC and just use File Transfer to move stuff back and forth.

There have been a couple of times with the handy remote access feature, where I have been asked for something at eight o'clock on a Thursday evening and it is on my desk machine, but I am driving back to my office. With TeamViewer, I can just stay at my home machine, connect to my work machine, and get the data needed without having to drive back across town.

It does have screen recording, which is a cool feature that I have only used twice.

It has been pretty easy to use. It probably does more things than I know that it can do, so it's probably even more robust than I think. What I do use it for, it is a piece of cake to use. They changed a couple of menu options between versions 13 and 14.

The remote connection process is reliable, good, and fast. On occasion, when it can't connect to a machine, the error messages aren't always helpful to tell you why you can't connect, as the message doesn't help troubleshoot whether it is too slow, too much interference, etc. I usually have to run to another computer and figure out what is going on, then restart it. The diagnostics could be improved.

I have been using TeamViewer for a year and a half at AirTies at this location. It now is required with the job. I have a bunch of different PCs spread around the house which I need access to., but don't want to chase down. My previous experience before AirTies was hit or miss. I didn't use it too often, only if I needed to set up remote access for something.

It has been really stable. It has only locked up once, and I believe this was because I got confused over a network issue since I was changing networks. It is nice that the product is stable. So if I can't connect, it's probably a computer or network problem, not a software problem.

For everything that I use it, it has been rock solid.

I am the only official tester. So, I maintain all the systems. I don't know how many people are on the QA test teams in Istanbul. It might be around 30 people and need an IT team of about 8. However, I am not sure how much they do get called up to test and maintain TeamViewer. Usually, I'm doing all the IT functions.

It scales pretty well. Every time that we get a new machine, we install TeamViewer on it. However, we only buy a new machine every 14 months or so.

There are no obvious limitation to how many end users that we can support. E.g., our home office has six test locations with an entire development team and QA team where have 50 to 60 people.

Our development, QA, and IT teams have access to TeamViewer. Our development team uses it the most. The IT team, which is about eight people, uses it a little. The QA team use it as needed, but not daily. On and off, 20 people use it, but 60 people have access to it.

I haven't had a chance to use their tech support. I've only searched a couple times on forums.

For our client, we just download, install it, install another one internally, and generate the unique ID. Then, you're good to go. The only thing that we do change is the password. It's a lot easier to type it in than the computer generated one.

The install process takes 5 to ten minutes. This includes time to record the ID for look up later on.

It saves me a lot of trouble. Time-wise, it is probably saving me several hours because I don't have to travel anywhere. I just wait for the time difference. With the time difference, it is really hard to talk to people halfway around the planet sometimes.

It has probably saved us several thousands of dollars because we have quick access anywhere. We don't have to worry about finding people onsite or arranging conference calls. We also save time and money with it because we don't have to send somebody onsite to troubleshoot.

TeamViewer offers a free version to try. Download and give it a shot. See what it's like and if you like it, then buy the license for it.

We tell people not to license TeamViewer internally, but they can download it. The product is not quite organized for distribution.

I've used VNC in the past at another company. I like TeamViewer a bit better, as it has more tools built-in. The File Transfer thing is awesome, and it also runs faster than VNC. VNC is free and easy to set up, but it's not user-friendly nor does it have as many options as TeamViewer. VNC doesn't have the powerful UI that TeamViewer has nor does VNC echo the screen like TeamViewer does.

There is also pcAnywhere, which is more PC-centric (not sure if it will work on a Mac). TeamViewer has a lot less overhead versus pcAnywhere. Also, I know that TeamViewer can anywhere and on a Mac.

Test it out and see if it meets your needs. 

It's awesome. Nothing else compares to it at the same level.

Biggest lesson learnt: There are tools available which don't cost too much and can improve productivity. They can make it so you don't have to travel so much.

We haven't done any 5G stuff yet. All our stuff is done WiFi locally.

We use it for interacting with other employees. They'll have TeamViewer, but they're working from home in another state. We link up our computers and, that way, it's almost like we're sitting next to each other. We can see what the other is doing on his computer.

We do use the technical support mode sometimes, which is the same thing as collaboration. You just log in to somebody's computer and fix that computer remotely.

It's smoother. It's faster. It stays on. It seems to have a really good connection and it's consistent.

Once we got it for the company, the IT manager deployed it and started using it for technical support. He doesn't use it a whole lot, but when he does need it, it really helps him. He can get in there and see what problem another computer is having.

The best feature is the remote access and being able to control another person's computer when you're showing them something, or teaching them how to do something during training, or fixing a problem they're having. Also, if I'm at home or even on the other side of the country like I am right now, I can log in to my computer at work.

On slow internet connections, TeamViewer works much better than other products. It seems to deal with slow internet connections better. If we are in a remote location and we want to access our computers at work, or a server, we can just log in to TeamViewer and it seems to connect.

There's a lot more you can do with it as far as collaboration and team co-operation go. You can get a lot of people on it. We're not utilizing it for that. For example, if the boss wants to hold a meeting, and have everybody join the meeting, he can do so and have different people do presentations. They can do their presentations and interact on one computer. If the boss is showing something and he says, "Well, take over and you show me what you think," that person can take over the cursor and start running it as if he's sitting right there in the meeting. I don't see other products doing that very well. 

With the other products that we're currently using, somebody has to say, "Well, let me share my screen and then they have to start sharing their screen and they have to turn it over to somebody else. Everybody has to load the program and get on the same page on their own computers, rather than just switching the control of the presentation to somebody, wherever that person happens to. With TeamViewer, they can take over the presentation right on the same computer that the presenter was using and give their presentation without having to switch screens. I love that part.

I've been using TeamViewer for a couple of years, but we just got the licenses in June.

The scalability has great potential. We could be using this for a lot more people in our company.

Our company has free products in use, like Microsoft Teams. The problem with Teams is that it's not as clear. It locks up and sometimes just doesn't work as well. But it's free, and everybody's using it, so it's hard to get people to move to something that's not free.

Although TeamViewer is a little more dependable and works much better, the cost is high. I can have a meeting online and have 35 people on it, as long as they have installed TeamViewer or log in to the website. They can all get on and they don't have to pay. But since everybody is using another product, and they've been using it for years, it's hard to scale up and get them convinced to use something different.

I've used the vendor's technical support a few times. They're responsive and they took care of my concerns. They showed me how to do things correctly. They were really good, easy to work with.

The setup is fairly easy. The basic connection is easy. When I started using the different services, I didn't know how to go in and start up a meeting. It seems to have a lot of features that have a little bit of a learning curve. I don't have time to learn all those features, so I just use the basic stuff.

On average, deployment takes 30 minutes.

I deployed it myself, as did my co-worker who is also a developer.

We haven't seen ROI. We're using it strictly for IT and technical, internal use.

I do use it a lot for remote accessing of my computer at work. I don't have to do anything, such as turn my work computer on. It just logs right in and I can start using it. I can also log in to other peoples' computers. All you have to do is hit a button and say, "Yes, allow me in." It makes it so simple to connect. It's worth the money, even though it's a little bit expensive.

It does what I need it to do but I think it's expensive. It wasn't easy for me to get approval from the company to get it. Not a whole lot of people in our company use it, but the five or six of us who do use it get a lot out of it.

It's costing us about $700 a year, per license. For the company it was $2,000, and that was on a deal. I think it would have been $2,200 or $2,300. 

I also got it for a friend who was working remotely. At the end of his year's subscription to TeamViewer, he wasn't using it much anymore. He was using something else. He called them to tell them that he did not want to continue with it for another year, but they said, "No, you didn't give us the 30-day buffer at the end of the year which is required to cancel for the coming year, so there's no way you can cancel now." They wouldn't let him out of the contract. He didn't read the fine print. We then read the fine print it did say that you have to give that number of days' prior notice before you cancel at the end of the year. If you don't give them that prior notice, you're stuck. I didn't like that.

I've looked at other companies that provide the same type of thing and their pricing is about the same.

I tried using WebEx and another product as well. They didn't work as smoothly as TeamViewer. We've tried using Microsoft Teams. Using that, you can take over and control the other person's cursor, but it's really cumbersome. When I use TeamViewer and get it up and going, it's almost like I'm just sitting in front of that computer. Aside from the couple of icons and menus that are off to the side, you can't even tell that you're not using the actual computer.

WebEx is great for doing meetings. TeamViewer may be doing great for doing that but I haven't really used it for that.

TeamViewer is much better for doing remote access than WebEx. For the stuff that I use every day, TeamViewer works better than other products, especially when I want to take over control of another computer. The other products that I've tried are not nearly as good when I do that. TeamViewer is the best.

The biggest thing I've learned from using TeamViewer is that you shouldn't spend a whole lot of time trying to find other products to save a little bit of money, when you already have a product that you know is working great. Don't waste your time. Get the product you know is working well, one you have confidence in and a little bit of experience in. Don't try to cut corners. I spend a lot of time trying to find other products because the company doesn't want to spend a few thousand dollars for just me and one other person, but when the IT person got on, then he was able to get them to use it.

In my opinion, it's the best remote access product on the market. The service is great. The product is great.

On-premises

TeamViewer is used to access computers remotely. I used it to fix computers if customers have technical issues. For example, if software or printers are not working correctly. Additionally, I can give demonstrations to customers on how to operate any application.

The most valuable features of TeamViewer are the ease of connecting to remote computers. I do not need a lot of information about their computers to connect, a nontechnical person can give me the information needed for me to connect. Additionally, the solution does not gather other system information about the host or client's systems as other solutions might, such as AnyDesk.

TeamViewer can improve connectivity. I had some problems connecting to my clients and now I use AnyDesk.

I have been using TeamViewer for more than five years.

TeamViewer is a stable solution.

The scalability of TeamViewer is good. However, I now use AnyDesk because I had a difficult time connecting to my clients.

I am the only one using the solution.

I have not used the support from TeamViewer.

I previously used the Microsoft Windows Remote Desktop application, but it's complicated to use. The setup and configuration of the solution are difficult, you need the client to have some technical knowledge to be able to use it. TeamViewer was better.

The initial setup of TeamViewer is easy, but there are some complicated settings that could be made easier. It is easy to download and I can share the link with a client to download and install it. Once installed, they only need to give me the ID and password to their TeamViewer and then I can connect.

There is no license needed to use TeamViewer.

I would recommend this solution to others.

I rate TeamViewer a nine out of ten.

Public Cloud

We primarily use the solution for remote access for foreign Windows devices.

The real-time access has been excellent. 

It's easy to initially set up.

The product is very stable. Its performance is good. 

It is a scalable product.

The solution can be customized. 

It would be very helpful if they could provide a manual for the installation process and describe more of their features. They don't seem to provide that right now. 

We've been using the solution for less than a year. It's been around eight months. 

The stability of the solution is excellent. There are no bugs or glitches. It doesn't crash or freeze. It has been reliable. Of the few times I've used it, I didn't have any issues. 

The solution is scalable. It supports many devices. 

There might be 120 users of the solution at this point. 

I haven't dealt with support very often. They have a contact page to reach them if you need assistance.

Positive

We use the solution once in a while. It's not something I use on a daily because we have other tools like Zoom or like Google Meet.

We don't really use any other remote access products.

The implementation process is simple. It's not overly complex or difficult. 

It was basically just downloading the solution. It doesn't take very long. 

I don't have any visibility of the cost of the solution. It's not an aspect I deal with directly.

TeamViewer is a good system for organizations in general - depending on their customer needs. Users, however, can customize it to what works best for them.

I'd rate the solution eight out of ten. 

Public Cloud

This solution has been really useful when doing product installations and needing assistance. I am able to give remote access to the person assisting me and they can view my operating system. 

Using this solution is straightforward.

It would be useful if the solution could facilitate more than one remote user accessing my desktop at a time. 

We have been using this solution for 5 years. 

This is a scalable solution. 

The initial setup is very straightforward. It took five to ten minutes. It can be done by yourself and there is no technical support needed.

I would rate this solution a nine out of ten.