They know what you're doing.' The audit trail on that is very good. You need to make sure that you have the user's permission before connecting to their machine just so: A. That's the draw back of any type of unattended access: They can just do that, so I've always put in a policy saying: 'Hey. The mouse is moving on its own.', and we take a look, and sure enough: One of the support agents has taken control. If somebody, every once in a while, and this isn't exclusive to ConnectWise Control, we'll get a call saying: 'Hey. I also like the fact that it does do an audit, so you can see who's connected to the machine.

We don't want this to pop up.' They've got their laptops connected to an interactive display most of the time, so they don't need to see what's going on in the background. Especially in our situation, a lot of times they're teaching a class and it's like: 'Ugh. schedule reboots, and you don't want to become too invasive to what the user's doing. It does come in handy if you just want to do something in the background, e.g. It's similar to a DOS window where you can run different types of commands against it. for old guys like me who prefer that instead of the fancy GUIs. You can also run commands against the machines, e.g. I haven't really played around with it too much, but what they refer to, what ConnectWise calls the unattended access, I would say is easily 80% to 90% of what we've used here and in previous lives, so it's really great. It also has the ability to have online meetings, like a WebEx scenario. We do push out the agents, but if somebody, for whatever reason, like our board of trustees, don't have the agent on their computer, we can create a support session so they can just join via a web browser and we can support them in the same manner. The primary support or the remote access support is really what we use ConnectWise Control for, but that's just the tip of the iceberg.Įven people outside of the organization would benefit from this.

Alternative to teamviewer