That's the only thing I've really noticed that is problematic from our perspective. It may have nothing to do with TeamViewer, or it may be a TeamViewer issue.
Then, the third time, it's working because finally the thing is awake and recognized and is passing everything through. 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. 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. 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. At first, everything was totally different. 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. There should be the same way whether you are doing remote support or just calls. There are different methods for doing different things, which makes it a little bit more complicated. It has the clunkiness of having separate modules that aren't totally integrated. We then decided to go with Microsoft Teams. We looked at it, reviewed it, and tested it out a bit. They were working on bringing a bunch of products together to make their suite a little more integrated, but it really wasn't at the point where we wanted it to be in terms of integration.
In my previous company, we were looking at this solution as being a collaborative tool for the enterprise in terms of video conferencing, calling, and scheduling. For transient clients that you don't necessarily support a hundred percent of the time, it would be nice to be able to connect to them and support their issues without having to install something on their machines. Even if you're using SCCM, it is an undertaking. For a whole enterprise, it is just not an easy task to install a client on everything. If you didn't install the client, you were very limited in terms of what you could do. I didn't like the fact that you had to install a client for remote support.
0 kommentar(er)
