How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
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.
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 use case is mainly PC and laptop support for our internal staff, where TeamViewer is distributed locally through Group Policy. Occasionally, we will use it to assist clients having trouble with our services, and in those cases, we will send them a customized linked invitation through TeamViewer.
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.
It allows us to access some of our remote sites, especially if we're having internal issues such as a VPN tunnel dropped from site-to-site. We can still connect to the local machines at the different offices as long as we still have an internet connection, and we can log in and troubleshoot networking issues remotely. TeamViewer is installed specifically on our desktop machines. We do also use some laptops that are on Windows 10, and there are a couple of Mac OS X machines we've used to remotely connect.
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.
I am using it more for meetings with my colleagues who happen to be at another worksite. I am using the meeting functionality more often now, compared to the remote-control functionality which I used more often previously. I use it on a Windows PC.
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.
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 use it for remote access to other machines. That was the main reason why we bought it. It is for our help desk and support guys to access remote users' machines. Our users have it on their laptops. We can also do a bit of remote support for Apple devices, but it is basically a screen share. You can just see their screen. You can't manipulate anything, but you can see what they are looking at on their screens. Therefore, it's mostly for laptops, desktop machines, and the PC environment. It is mostly for the regular support, for anybody who is having issues with a machine. I use the solution quite a bit. I love it.
We use TeamViewer for support, controlling our ~2,500 end-user computers and our ~60 servers. Our environment is primarily macOS, with about 95% of end-users on Macs, but our servers split between Windows and macOS. We also have some digital signage devices that run Linux, and we use TeamViewer to control them as well. We ran TeamViewer concurrently with LogMeIn for about year as we evaluated TeamViewer as a replacement. TeamViewer's superior remote quality (especially in low-bandwidth situations) and ease of mass deployment, combined with LogMeIn's serious and longstanding bugs led us to recently discontinue LogMeIn in favor of TeamViewer.
I wanted something which I could use to control other computers over the internet, and then I found TeamViewer, and it worked great. I can control any customer's PC right from my computer with ease.
The primary use case is remote support.
Accessing unattended servers, Mac, Linux, Windows, Raspberry.
We use this product primarily for remote technical support and software upgrades. We have quite a number of computers in the field which would be costly to facilitate transportation to a service location.
IT help desk support for nonprofit organization of 200 computers. We purchased the product pre-installed with the TV in unattended access mode. We also use it for ad hoc remote support of individuals, primarily using TeamViewer QS.