@DarthKevin wrote: No, it's not related to the outage. It's an ongoing problem for us. It sometimes takes as many 5 tries to get connected with each attempt showing Authentication Cancelled. I'm having the same issue here, only on my affected systems, it never connects. Sometimes, I can restart the TeamViewer service on my own machine and it clears up, but on those remote machines, I don't have that option without user intervention or figuring out a sidedoor method, which sort of defeats the purpose. In desperate times I have to try to find a server or other user desktop to TV into, and then use Microsoft Remote Desktop over to the affected machine and either restart the TV service, or reboot the machine. I'm seeing this happening more and more frequently. Again, the cases I'm experiencing, not related to any service outages. What gives? I love TeamViewer and am a long time user/owner, but these reliability issues are starting to concern me. So far it's mostly user desktops and workstations, but when this starts happening on more mission critical gear... I never had this problem with earlier versions of TV. Just seemed to start with TV12 and 13..
... View more
Long time TeamViewer user/admin/proponent/evangelist here. Just wanted to throw in a +1 for this feature. I was just going through old machine entries wanting to clean up my account and looking for a way to mass wipe. While I can understand the concerns for accidental deletion, I do agree that we need better admin tools and controls. Maybe there could/should also be a way to backup or export our accounts/contents, as well as locking down operations we'd be able to perform under certain accounts. This is one of the things I hate about hosted, material designy stuff - very limited access to configuration compared to local administration utilities. Local admin utilities usually seem to have some kind of export functionality, either csv, xml or some kind of database. Not trying to open another can of worms here, but I'm of the same sentiment as above users - at this level, we're admins, not end users. For now I'll have to have a look at the workarounds. Not ideal, but wha'cha gonna do. Just gotta get the job done. At least the status shows us when the last connection was.
... View more
I am using TeamViewer v12.0.90922
I was doing some testing with the meeting module and trying to create a video call, sending an email invite to myself, and joining from a Galaxy S7. The latest TeamViewer Meeting app for Android available to me is version 10.0.2484 on the Play Store.
When I go to join the meeting from my phone, it tells me Incompatible TeamViewer Versions
Then below that a notification displays briefly saying Your partner is currently hosting a video call. The versions of TeamViewer you are using does not support this feature.
Is Video Calling only for computer to computer, or can it be used with mobile as well?
... View more
Good luck, Jeremy. For as many issues as I've tried to bring to the attention of TV support, I've had zero resolved, and no real meaningful response. I've had some contact from the support reps monitoring the forums with some well meaning feedback, saying that they do take every contribution seriously, but the bottom line is that there has been no action on any of the issues I've reported. Can't speak for anyone else. Some committment one way or another would be nice, so that the very least, I'm not wasting my time trying to better a product that I *used* to absolutely love and and recommend without hesitation. I still use it, but when the time comes to upgrade, I'll be taking a closer look at other options. This pains me, because I'm a long time TV user. I still enjoy the platform for what it offers while I'm able to use it, but this upgrade business is a potential show stopper. Our little sub $3k investment apparently isn't enough to warrant attention, or acknowledgement, for that matter, from the devs.
... View more
I have some older client PCs running on TeamViewer v7. We have a perpetual license for TeamViewer v12. I would like to use the Remote Update feature when I visit some of these older client machines, and I do see that TeamViewer's Remote Update feature offers the options of the newest update for the installed version, or to upgrade the installation to the newest version of TeamViewer available, currently v13. Our license is only good for v12. Unless I'm missing something, with the release of v13, I'm now unable to remotely update the client software from v7 to v12, only v7 or v13, without either some other form of remote access, physically putting hands on the machine, or some complicated user interaction to walk through the process. This would also require divulging passwords to a user in order to access the user options to allow Shutdown of TeamViewer in order to install the newer version. It would be tremendously helpful if, in the Remote Update feature, we could get options to update to the latest version of all major versions. For example, in this case going from v7, calling the Remote Update feature would ideally offer the latest versions of v7, v8, v9, v10, v11, v12, and finally the most current v13. I understand that TeamViewer is moving to a subscription service only at this point, but many of us being IT professionals with perpetual licenses are left behind in this, and without the ability to choose which version to install using Remote Update, we are faced with a rather significally difficult situation where it could be simplified. For internal organizations, I imagine one might use .msi packages to roll out these updates, but some of our clients are not inside our organization. Maybe there's a way to script this to avoid the need for user interaction while executing a version upgrade. I've reviewed trying to apply this by policy, but I'm unable to apply a policy to a v7 client, for example; it's simply not an option offered in the TeamViewer Management Console online; grayed out. I would be interested to know if anyone has any input on that as a potential work around if TeamViewer has a legitimate reason/difficulty for not making all current previous versions available as Remote Update options.
... View more
I'm just reviewing some of the posts in this thread - I understand why it doesn't work, but do agree with Tamir's response here. It would be extremely handy to have cross-version compatibility in the connection of OlderClient > NewerHost direction. Might not be able to support all the new features, understandably, but if it's possible to have the basic remote control, that would resolve much of the frustration in working with a previous version as a client/control app to administer and support computers with newer versions installed. The bulk of my TeamViewer use is for remote control. I've been starting to use the file transfer/box/chat options a bit more, but I can figure ways around this in emergencies. Resolving the version difference issue prior to being able to offer support is a show stopper in cases where a client has installed a newer version. @Tamir wrote: This does not fix my problem. It seems Teamviewer support refers all problems with the upgrade harrassment to this guy's quicksupport solution. I have Teamviewer Host 13 (a native Linux app, or so I'm told) running on Ubuntu 17.10. I am trying to remotely control it using Teamviewer 12 (not a native Linux build but rather a WINE wrap) on another Ubuntu 17.10 and I am getting this message: Pressing "OK" does nothing. I can't understand why Teamviewer 12 cannot connect to Teamviewer Host 13. It would seem obvious that one version difference in levels of technology would be compatible.
... View more
I agree with nearly all of this well thought out post from wmelton, except for the last paragraph with the BBB/Attorney General bit. However, I can certainly understand the frustration that drives such a response. It would be great if TeamViewer would simply listen to some of the biggest backers in its customerbase - the IT people who recommend and purchase the software. We're practically screaming for TeamViewer to acknowledge some serious issues, and respond appropriately with fixes. I've been trying to share some of those concerns here in other threads, but those issues haven't been addressed, either. I'm sorry to say I'm not impressed with this forum as an effective feedback system, one that results in problem resolution. What's the point if we don't get any meaningful response or committment from TeamViewer on the matters we take our time to report for discussion? The alternative is the same as always - no one here wants to do it, but it could result in finding another way, which could mean another product. This isn't just a bunch of people annoyed about nuisance price hikes. We're telling you we can't afford it anymore, whether it be small one-man shops or small businesses. You're being warned that you're going to start losing people, if you haven't already. I get it. It's about money. On on both sides, though - TeamViewer's and its customers'. I can understand how this subscription and price model ensures continued revenue for TeamViewer, and I acknowledge that this is extremely important, but it's killing it for a lot of us. I, like the others frustrated here, have become dependent on TeamViewer. Trusting in it for the long term, I've been deploying it throughout our organization over the years since v7. However, if I'm forced to make a change, I will find another way. I love TeamViewer, and I really don't want to have to do this, for a multitude of reasons. We recommend this software to others, and not just internally. I'm always telling other IT people and business owners about it, singing its praises. It's one of the top four productivity tools I require to do my job efficiently, along with Evernote, Outlook and Gsuite. How can we continue to recommend it when it's not affordable? My bosses will balk at renewal at these fees. At best, I'll lose two seats. I'm always using at least one, sometimes two, if I'm using a desktop and Macbook at the same time. Our users won't be able to host meetings with clients. That means we lose half the main functional benefit to the organization. You have to see how that makes it harder to sell. That's my day job. Then there are consulting jobs in less controlled environments where I'm more greatly affected. Just letting you know. I know TeamViewer's got challenges. So do we, and you're pricing us out of your customerbase. Is there a way increase subscription volume through reduced, fairer cost, and still have the necessary revenue to keep TeamViewer going?
... View more
@NeilInOz51 wrote: I have a software company too, with embedded TeamViewer Remote Support. But if a client decides to download a new TeamViewer (maybe the free one) and has it running (as they do) then our version of Remote Support doesn't work, which makes us look stupid and penny-pinching. Summary: The worst pricing policies of any software company, bar none. I've had this happen before, as well, and agree, it can be a little embarrassing trying to explain the difference between paid/free, why I'm running a previous version, and then the subsequent hassle of working around it, and then requesting that users/clients not upgrade in order to keep unattended access working properly. I just had a discussion with a TeamViewer rep recently regarding pricing frustrations. I was provided with some general info regarding what's going on behind the scenes for TeamViewer to keep things going. There's a lot ot consider. Granted there are some hassles with the way things are currently working with TeamViewer, but it's still my go-to pro tool for Remote Support. I'd be lost without it, but I agree, I wish it were either Cross version friendly, at least for remote control, or More affordable to stay current. I like to get at least 3yrs out of a software before having to upgrade. I don't think that's unreasonable, even with as quickly as things are moving these days. If a new feature comes out during that time that I just have to have, I'll pay to upgrade. With internal TeamViewer use, this is easier to manage, but externally, I've had the same problem as Neil. With the subscription plan, I eat up my TeamViewer software budget in 2yrs instead of 3yrs, not to mention, that cost is for one user only, whereas my perpetual license covered three concurrent users. That's a huge cost spike, and we don't use all the new functionality, but again I do understand TeamViewer's got some serious challenges to meet. I don't know what I'm going to do when the hassles of using a previous version of TeamViewer begin to outweigh its benefits. We can't afford to stay with TeamViewer with current subscription rates.
... View more
Kind of figured this out, but leaving it up here in case anyone else happens across a similar problem. This issue seems to be with some setting in the user profile on the Macbook side. Tests fine with a second MBP, which was running a slightly earlier version of TeamViewer 12. I updated that to confirm, and the second MBP still worked just fine in CTRL+Clicking in remote Windows PCs. I created a second test profile on the primary Macbook. TeamViewer worked properly to CTRL+Click objects in the remote Windows PC, leading me to the issue being something in the user profile. Now to figure out what that is... I've already reviewed the keyboard settings for shortcuts and such, and all seems to match between the two machines, so I'm thinking maybe there's something going on with an application, causing this conflict.
... View more
Hey guys, I'm working with some Windows PCs from my Macbook today, and while working in an Excel document on the remote PC client, I'm noticing that I'm unable to Ctrl-Click to select multiple cells in Excel, for example. It's as if the Control (CTRL) key is being ignored. It simply changes the selection focus to the next cell I click.
I've verified that this works properly from a remote session using the PC version of TeamViewer, so nothing going on on the remote PC side.
I've tried this with two different remote PC clients. Tried various key combinations (Command, Opt, etc.) Checked my keyboard preferences on the Mac side Tried forwarding key combinations.
Ctrl+A works to Select All Shift+Click works to Select a Range Just can't seem to get Ctrl+Click to work to select multiple non-adjacent cells.
Nothing's working so far; Can't seem to figure this one out. I presume this should work correctly, yes? Any ideas?
... View more
My experience with scaling is not what you describe. I've never had TeamViewer scale a smaller remote display upward to fill the screen. I see that that can be done with Best Fit, but I don't care to use this feature at all. I see no point. Maybe if my display was larger, but I'm using 1920x1200. I resize session windows frequently - reducing them only - when I am in and out of multiple sessions. Sometimes I need to execute a task, and then will reduce that window's size, move it off to a corner, and monitor it periodically while I'm working with another session window in the foreground. I routinely move these windows around, resizing them numerous times, as needed. Sometimes I'll get my sessions running and reorganize the windows in a cascaded layout, all windows of about the same size, regardless of scaling effects. This is one other way I work sometimes. I can spend the extra time resizing them to get the black bars out, but I have to start this process all over again if I reboot a remote client, or have to reinitiate the session. Aspect lock makes this a non-issue. I still don't understand why it was removed or what TeamViewer's position is on writing it back in, and supporting it for v12, as it should have been all along. Clearly other customers have voiced desire to have this option returned to the software. I'm having a hard time understanding why this is so difficult to understand. Hopefully the imgur gallery I created and posted above will clarify the problem and shed some light on how this lack of aspect lock in resizing is a hugely inefficient nuisance. Happy to continue helping out in the interest of development, but perhaps a phone session would be best if this is not clear at this point.
... View more
Hey Jeremy, how you describe the difference between Best Fit and Scaled has never been my experience with v12 or previous versions of TeamViewer. I've never had TeamViewer scale up a smaller remote client. It's only ever displayed in actual size, or scaled down. I resize because I frequently work with multiple remote sessions at one time, and resizing upward makes it easier for me to shift focus, while resizing downward again to "put it in the background". Sometimes I just want to monitor a running task out of the corner of my eye, but to have that window sitting on my screen at full size, I can't see what's going on with it if I'm working on something else that's full size in the forefront. So I'll change my session windows to be able to monitor multiple sessions at the same time while working on something in the forefront. This is just one reason for it. The point shouldn't be why do I want to work a certain way. The points here are, why has TeamViewer taken a step backward in eliminating an elementary program operation? and why does no one at TeamViewer seem to be able to understand the issue despite contributions and examples from several customers? And there's no response on whether this is to be addressed. It almost seems like no one ont the support team has used TeamViewer. This is becoming frustrating. I've taken some time to compile some examples to better clarify, along with a brief writeup and posted on imgur. https://imgur.com/a/VxbDY
... View more
I was trying to help a user through configuration of a new Android Galaxy device the other day and asked him to installed the TeamViewer QuickSupport client.
My understanding now is that the generic Quick Support client from the Google Store only allows screen viewing. For remote control, a supported manufacturer-specific version of Quick Support needs to be installed. Quick Support for Samsung, for example.
This is fine. The problem is this apparent requirement that the device be added to a management account in order for remote access to work. In real world terms, this would require me to give a user my TeamViewer account credentials in order to add it to my Management Account. There is no way that's going to happen.
The whole point of Quick Support is for quick support. Even if a user can get me access after creating his/her own TeamViewer account, they're not going to go through the process of creating an account with a secure password and then go through all the rigmarole of having to activate the device on the back end through an authentication email. Remember, this particular case I was working - this user had just received a new device to replace a damaged one and did not have immediate access to any email accounts as was not near a computer or other device to be able to create, activate, and authenticate a request to add a device. This does not make sense.
I vaguely recall earlier versions of Quick Support for Samsung working without having to add it to a management account, however, I may be mistaken here, because it was weeks and weeks ago, and I only tried it briefly.
Quick Support for mobile devices is one of the advertised features for TeamViewer 12 that helped me to convince our owners to spring for upgrading our TeamViewer software. This is another feature that is not working efficiently, and I'm sorry to say, in the field is essentially useless at this point from a practical implementation perspective for sys admins.
The iOS client is just as bad or worse. The screen displays in full resolution, requiring scaling functionality that is not there, so I have to scroll up and down to see the full screen. And then I have to prompt the user to pop a screenshot every time I need to see a screen, which is really annoying when I have to simply go back one screen; it doesn't seem to save previous views? Tedious. If I could reach through the remote session I would throw that device on the ground! At least the Android client shows a nice little realtime display of the device and an Admin could direct a user more efficiently by phone while monitoring the screen. Requesting screenshots is p a i n f u l l y slow.
These both need work to be considered selling points. Especially the iOS version.
Hear us, TeamViewer. We love your product. Let's make it the best it can be.
... View more