TeamViewer Reviews

I use TeamViewer for remote desktop support to resolve issues and queries. For example, when I, in Johannesburg, get a ticket from somebody in Cape Town, I will use TeamViewer to connect to their computer remotely.

I think TeamViewer's most valuable feature is that it is user friendly. Creating passwords is easy and so is security.

TeamViewer is a step ahead of solutions like, for example, AnyDesk. With AnyDesk, when you connect, if you didn't configure it to connect with your own password, you actually have to wait for somebody to accept your connection. With TeamViewer, you don't have to do that. As long as you've got your user ID as well as password, then you can just connect any time.

One thing I have noticed is that TeamViewer does not work so well when the machine you are trying to connect to remotely is not running the same version as your machine. It would also be great to be able to share a screen using TeamViewer like you would with Skype for Business.

I started using TeamViewer in 2014, so I have been using it for almost seven years.

TeamViewer is a very good product to use. The cost is not that high and there is a free version you can test out. If you are still new in the business, then you can use the free version indefinitely. If you are happy with it, then obviously you can update.

I would say it is easy to scale. At my company, I am the only one using it at the moment because I deal with the IT stuff. When I was working for an IT company, the whole department used TeamViewer to connect remotely to our client's machines.

I'm currently using TeamViewer on a daily basis but I never had issues with TeamViewer. Since I'm a senior level IT professional, when there is a problem with TeamViewer in my company, my colleagues usually escalate it to me.

Also, we acquired TeamViewer from a third-party, so we do not have direct access to TeamViewer's technical support. 

The initial setup was simple for me because I am used to configuring much more complicated stuff. But, even someone who is not in IT can still use it.

I deployed the solution myself in less than 30 minutes. However, how difficult a deployment is depends on how many PCs it has to be installed on. Obviously if it's 10, then it's going to take longer, but if it's one PC, then it can be done in less than 15 minutes.

It does require some maintenance when it comes to updates and making sure all your machines are running the same version. 

I think the price is reasonable. When a company develops software, they are creating a product. The purpose is to help people and also to make money. With this in mind, TeamViewer has a good price because you can still use it well without running into any issues. 

You can get a trial version but you cannot use it for free forever. If you are using the free version, you will have some limitations.

The advice that I can give to users looking into this product is, do not buy a license at first. Start with a free trial. However, you will need a license to access some advanced features.

• The new two-factor authentication is a very good addition to security.
• ITBrain monitoring, which lets me track hard disk space, processor usage and lots more.
• Adding custom logos is a nice feature too, especially for IT companies that provide services to customers.

We don't use it in my current workplace. However, I proposed it for consideration in the budget, because of the highly centralised way it works.

They really need an AMT client and/or iLO client for business use. Big companies would love it.

I have used it for almost five years (personal use).

I have not encountered any stability issues at all. It’s by far the most stable remote software I’ve tested, except for RDP.

I’ve seen it run and connect to a small 500-1000 end-devices company without a problem. At a higher level, I’m not sure, but it’s promising. I’m sure they have some big names in their portfolio.

I’ve never had the chance to talk to technical support.

It’s the other way around now: We have a different solution and we want to switch to TeamViewer.

All the installers are easy to use and also not too hard to deploy silently.

The licensing is pretty straightforward: number of devices and number of remote administrators.

I also looked at Bomgar, LogMeIn, Radmin and DameWare; also at open-source options like VNC and RDC.

Talk to the sales person and ask all the questions you have. Make sure it is the right solution for you before you strike a deal.

It’s primary function of RDP is the product’s most valuable feature.

It has been a great way of allowing multiple users both registered and unregistered to use RDP, from both system management and use points of view - as well as using it to support remote users.

Clipboard management could be better. As could the drag-and-drop file upload/download function (especially when multiple monitors are involved).

For the clipboard management aspect of improvement it would be nice to have some sort of user isolation in regards to the clipboard. You’re already logged in to an account for TeamViewer, but if multiple people are connected (even if not actively on the same remote machine), the clipboard is shared for everyone. So it’s very possible to copy a block of text and when pasting you end up pasting a completely different block of text. Even a clipboard viewer would be nice – maybe show the last 3 or 4 copies so if someone else did copy as well you could at least see it.

For the drag and drop issue, if dragging from a remote TeamViewer window you have to drag and drop on to the same monitor. And there can’t be any other windows in the background you are moving over; otherwise the transfer won’t work. Often times we have multiple remote machines open on one monitor that often overlap. Having to shuffle screens around on the desktop is tedious just to be able to drag and drop. So we end up using the file transfer window process instead. So it’s a “neat feature” to have drag and drop, but implementation has a few pitfalls.

I have used it for four years.

There have been a few times when TeamViewer has been down globally, so that’s definitely an issue for consideration.

I have not had any scalability issues. It’s worked really well for one-machine access for home use, as well with 30+ servers and multiple open connections.

Technical support is usually prompt and helpful. Following their Twitter feed helps with monitoring for external issues and outages.

I have used several different variations of RDP from pcAnywhere to straight Windows RDP. TeamViewer is very easy to set up, use, and instruct others to get running, which is great for support. Very little if any fiddling with firewall rules is needed, so that’s a real plus.

Initial setup was very straightforward. There are multiple installs depending on what you need (host, client, etc.), and it’s easy to switch from one to another or just disable the features that aren’t needed.

The free version is great to get started with and for a lot of people, it might be all that is needed. If you are going to be using multiple machines with multiple connections, you’ll need to consider the enterprise version.

I did not evaluate any software prior to starting to use TeamViewer. The company was already using it when I was hired. But it’s definitely better than a lot of the other RDP clients out there.

Depending on usage, one thing to watch for is the shared clipboard feature. It is nice to have the ability to share the clipboard between machines. However, it also shares it among all the users connected to the same machines. So, in our case, we’d have 4-8 different users connected randomly to different machines. And the clipboards would sometime transfer from user to another. So something that was copied from one user was pasted into another user’s work (can be both frustrating and comical at times).

It is possible to lose connectivity due to external issues, so that might be something to consider.

As with all RDP clients and the functions that they provide, pay close attention to application security parameters, as well as security on the machines themselves. You are opening a direct line of communication to your machines, so tread carefully.

This is a remote access tool. Usually, we just use it for our support team, to help them support our customers.

The interface is good, and it is easy to use.

The document control is quite good.

It’s easy to implement.

The product is scalable and very stable.

Sometimes it lags. They need to optimize it a bit. AnyDesk, for example, works faster.

We’ve been using the solution for five years.

The solution has worked flawlessly. It’s stable and reliable. There are no bugs or glitches.

It’s a scalable solution. The product is easy to expand.

More of our usage is coming from support, and we are about 18 support engineers we have.

We have not really used technical support. We haven’t come to a point where we have needed to seek help from TeamViewer.

We tried the other remote access tools like AnyDesk. We switched due to a management decision. We looked at enterprise options and user manageability. We wanted to monitor our licenses and also the usage we have. AnyDesk worked fast. However, sometimes the video quality is bad.

The initial setup is very straightforward. The instructions related to the implementation are straightforward.

The installation itself is also fast. It only takes two to three minutes.

We handled it ourselves. We didn’t need any help from anyone outside. We didn’t use integrators or consultants.

I don’t have any visibility in terms of licensing costs.

I’d rate the solution nine out of ten.

We use TeamViewer for remotely managing desktops. If a user is facing difficulties or has some technical problems we can easily connect to their system to troubleshoot the issue for a resolution. There is no need to attend to their location.

I have found the solution to be user-friendly even for beginners. It is not that sophisticated. There are different types of security features available, such as encryption and random machine ID.

There is a paid version of this solution with more features available. However, they should provide more free features to the user, such as factor authentication.

I have been using this solution for approximately one year.

The solution is very stable and there is not a lot of delay in performance during a remote session.

We have approximately 20 people using this solution in my organization.

I have previously used Microsoft Windows built-in remote desktop.

The installation is very easy.

There is a free and paid version of this solution. I am currently using the free version.

I would advise others this is the best solution for administrators or IT personnel. You do not require very much knowledge on how to use it. You will be able to use all the features because it is user-friendly.

I rate TeamViewer a nine out of ten.

I only use TeamViewer for troubleshooting methods when the students or staff members are unable to come to the IT desk.

• The most important aspect of the software is remote access
• Helps alleviate confusion with directions over the phone
• Security: The user can input their credentials, personal information such as usernames, passwords, and secure payment methods without the risk of the IT personnel using it maliciously.

This software is a lifesaver for distant and commuter students who cannot physically be on campus. As a school's main IT support center, we use this software constantly. Many students keep the program on their desktops so it is easy to remotely connect to their devices.

Unfortunately, the software is hit or miss when it comes to iOS devices, especially Macs. It seems that the new updates may have included better iOS supported drivers. However, when we used the software, it only worked a handful of times.

I have used this software from September-May of the 2015-2016 school year at Stevens. We still use the software to remotely connect into domain computers and laptops on our wireless network.

Overall, we did not encounter stability issues. For the most part, TeamViewer is a headache reliever. Even though the connection between the two devices may drop every once and a while, it is primarily successful.

There have been no issues with scalability.

It was very simple to set up on both the IT and the student side. We have a link to the main TeamViewer website in our university portal that gives straightforward instructions on how to install the software properly.

Use this product. It is so easy to use and it makes students and staff happy. Older staff and professors are amazed that I can control their machines remotely, almost like a wizard.

• Unattended Remote Access
• Collaboration with partners with all communication channels available at the same time

There are only two of us in the core of the company and we manage about 500 machines based in the UK, mainland Europe, US, Hong Kong, China and South Africa.

ITBrain should be embedded in the product and not an expensive add-on.

We have possibly been using it since TeamViewer 1.x; most certainly, since version 2.x.

We have only rarely encountered stability issues, and when it does happen, it can often be attributed to the state of the remote machine.

Once again, we have only occasionally encountered scalability issues; not often enough to worry us.

We hardly have to use technical support. When I have in the past, they have been very good: prompt, professional and usually accurate.

We previously used many solutions, such as VNC Viewer, and had so many issues, as the software was never designed to be so dynamic and was resource hungry.

For IT professionals… installation is a doddle!

I think it’s a top product, but due to our company size, we find the pricing heavy… Nevertheless, as long as it remains number one, we have to grumble and get on with it.

Once we tested it and used it ‘in anger’, there was no need to look elsewhere. We started on the free versions that were available at the time. As we became more and more reliant on the product, with increased collaboration, the need to up the level of the product became apparent. Which product version to buy was the only option under consideration.

Test it first and determine whether it’s the right technical product for your company, then evaluate your cost options and if they agree, go for it.

• The ability to connect to and control remote PCs across various NAT and firewall barriers.
• The ability to interact with the computer prior to end-user login.

We have a lot of remote offices, and without the ability to remotely control the computers at these properties, my job would be much more difficult to perform. I'd otherwise have to jump on a plane to address any and every hardware or end-user situation that pops up. Other competing products, such as LogMeIn and VNC Server, don't offer the same mix of functionality and security.

Quick User Switching has a very nasty tendency to render the screen output unstable. If my remote work requires switching logins on the remote computer, TeamViewer's video output will cut out completely and I'd have to instruct the end user over the phone to either restart the computer, or end and then restart the session in order to restore video output. In cases where even this doesn't resolve the issue, I've had to resort to the built-in RDP application in Windows, which, of course, makes it impossible for the end user to interact with the computer for troubleshooting.

I have used this solution for two years.

TeamViewer apparently has compatibility issues with Dell's ImageAssist utility (which we use to author and deploy corporate Windows 10 images). Specifically, the way it interacts with a computer's video drivers isn't exactly supported, so I've had to install it post-imaging. That's likely a problem that Dell has to get straightened out.

I've used several flavors of VNC apps in the past. They were OK, but it took work to make them secure out of the box (insofar as a VNC solution can be secure). I've used LogMeIn before also, but it didn't provide the same level of functionality and versatility as TeamViewer. Plus, it had trouble traversing some firewall solutions.

Initial setup was straightforward. Nothing complicated. Just kept clicking Next, basically.

An in-house team implemented it. My advice would be to research how the program interacts with your imaging solution if you're baking it into your corporate image.

$3000+ for a corporate license was steep, I must say. But if your options are between remote support and hopping on a plane (such being the case in my company and industry), you'll make the money back in saved travel expenses alone.

I'd say consider TeamViewer if your company has several geographically separate branch offices. If you're primarily supporting systems in a single building, I think more cost-effective solutions are available. But of course, go with what works best for your given network setup.