We use gotomeeting. Mind you, that’s because we want to be able to have multiple people present so we can go through items in a meeting sort of way. We want any number of those people to be able to take control of any other computer in the course of diagnosing.
Just to clear up my recommendation of Teamviewer, it’s not necessarily the best, depending on your needs, but it has an easy and reliable start up process in my experience, and the OP doesn’t have to worry about the guy on the other end configuring his machine correctly. Once that link is established, I’d recommend configuring the other machine to support Remote Desktop and other Windows remote access services. That allows the OP unfettered access to the remote system and the ability to configure it for any other kind of tool.
At work I use SecureLink a lot. It’s an excellent tool, allows multiple users to connect to the same machine, and it’s very secure. I think it is expensive though, and the security is so good there are a lot of problems getting through firewalls with it. It’s not for everybody, but if you are looking for incredibly secure remote access, it’s the way to go.
I have no doubt that you and I could make it work with minimal hassle. But it might be too complicated for this particular situation. I just took a quick look, and MEGO set in. That’s not a good sign if I’m not working with a peer.
I think a large percentage of people responding here read the thread title an not the actual OP.
Best remote support software is one thing, best remote software for your case is entirely another.
Aren’t we geeks supposed to RTFOP?
Teamviewer et al look great, but as any remote support tech has seen, even something as simple as allowing an ActiveX script on a page can be a deal breaker. BTW the first time I went to disable teamviewer in my task bar it finally prompted me to log into a VM, nice, but it didn’t show me a thing about the target’s DL path.
If I have a fleet of PC’s I need to be able to access unattended, do file transfers, etc. I’ll likely choose something like TV, but for dealing with the feeble end users that have to be told how many times to click which button, and when to hit enter, I’ve made my choice.
Speak for yourself, I read it just fine. I assure you, my mother is about as feeble an end user as you will find, and she is capable of clicking the TeamViewer shortcut to launch the program and telling me what the password number is. Yes, I had to talk her through the download and installation initially.
I am unable to parse what you are talking about in the above quote because it in no way translates to any behavior I’ve ever encountered while using the program.
The OP was asking for suggestions and experienced opinions, not religion. I think all of the suggestions have been valid.
Ummm… no. Teamviewer is a very good choice for the OP and I have used it for precisely the OP’s purpose. If I wished for a corporate solution, I might use something like VNC.
I just wanted to report a session with my friend. I wasn’t quite ready and done with my tests, but he had a problem that needed to be fixed, so we plunged in.
First, we ran join.me on both machines. I was able to connect to his with his serial number, and that’s as far as we got. I clicked on the mouse icon, “request control”, and nothing happened on his end (so he says). So I could never control his computer, although I could see the screen just fine.
That wasn’t a good sign, but I installed teamviewer on my machine to see what it looked like, then guided him thru installing it on his, exchanged serial numbers and password, and I was able to control his screen.
One oddity was the low number of colors which made images very blotchy. I checked his display settings and they were 1024 x 768, 32 colors, so that wasn’t the reason. I suspect teamviewer reduces the color palette severely to reduce the amount of data that is transferred.
We ran malwarebytes and his machine was reasonably clean (I think MWB brings up a few false positives that are of no consequence).
We were able to straighten out some problems without too much hassle, so I declare this first trial OK. Thanks for everyone’s suggestions and assistance.
A few thoughts, and I’ll admit this was not a typical support session…
One of the reasons teamviewer worked but join.me did not was the similarity between the client and host side screens in teamviewer. join.me uses different colors for each side – not a bad idea, but if I am trying to tell someone which button to click, it doesn’t help if I say orange and he has only greens.
I ran teamviewer and continued with the installation until I got to the point where one of us had to enter a code and password. Since the two sides were identical up to that point, I could tell my client exactly what, why and how to select. Then when we both arrived at the same point, I could ask him to read the codes on the screen. Also, teamviewer’s default text size was much bigger and more readable.
Even then, I had to anticipate the anti-virus trapping which was different on each machine.
This would not be a problem if we were both frequent users of the support interface, but in this case, neither of us were.
I don’t recall if Teamviewer does this, but some remote software automatically turns the background to black on the target machine to cut down on data transmission. Varying resolutions are the annoying part of these packages. Some machines with low res displays are too small to read when viewed on my screen. The communication rate can also vary in a lot of ways. I regularly use GotoMeeting, Teamviewer, SecureLink, WebEx, and even Skype Desktop Share to connect to different sites. It just depends on what the other end can handle. One good feature of SecureLink is that a gateway can be installed on the remote machine allowing unattended access. If I don’t need the party on the other end to show me something, or watch what I’m doing, I find Windows Remote Desktop to work best (on Windows obviously).