
Originally Posted by
Hellfury
I use teamviewer, I know there are other options, but it's silly easy.
We went with the QS on clients so they don't need an installation, and it's only running when they want to (I don't want to have remote control software running anywhere it doesn't need to). We just showed it into the \users\default\desktop folder so any user who logs in will get it on their desktop regardless.
Older versions only used 9 digit ID + password (or other setups), the newer versions let's you "hook" the QS to a specific account, so whenever someone needs help, they just start the QS module from their desktop, and I get an e-mail, and their user pops in my TV software, I click their name to connect and they confirm.
I have two issues with teamviewer.
1, Older versions struggled a lot on multiple screens.
2, 50% of the time, when I close teamviewer if I've been working at home, the XIV client stops taking input. No idea why.
the downside to having just the QS on the users computers is that it'll cockblock you if it needs adminaccess, you can just tell the QS to install a full version though and give it your domain admin.
it feels like it is remarkably adept at navigating our messy network configuration with no hassle, so I like it. actually one pet peevee, the default warning mail about a new case only contains the session ID, not the user ID, I need to get off my lazy ass and see if I can change that.
Being able to see what's going on (for most cases) rather than depending on users trying to describe something they don't understand is divine. between teamviewer and netsh winsock reset my job is a lot less complicated than before.