This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
computing:remote:teamviewer [2013/06/06 11:17] gcooper |
computing:remote:teamviewer [2019/05/22 10:46] (current) jcooper |
||
---|---|---|---|
Line 4: | Line 4: | ||
Home: http:// | Home: http:// | ||
+ | |||
+ | Download: https:// | ||
===== Linux ===== | ===== Linux ===== | ||
Line 46: | Line 48: | ||
Sonora Communications, | Sonora Communications, | ||
</ | </ | ||
+ | |||
+ | ===== Windows UAC issue Quicksupport ===== | ||
+ | |||
+ | https:// | ||
+ | |||
+ | When using QuickSupport connected to a Windows PC without Admin rights any action that brings up UAC will stop control of the remote PC. | ||
+ | |||
+ | The fix is using Admin Windows credentials instead of TeamViewer credentials to login. | ||
+ | |||
+ | How to connect using Windows Authentication: | ||
+ | |||
+ | - Start TeamViewer on your computer. | ||
+ | - Ask your partner to start TeamViewer or TeamViewer QuickSupport on his computer. | ||
+ | - Ask your partner for his TeamViewer ID shown in the TeamViewer application. | ||
+ | - | ||
+ | - Click on Connect to Partner. | ||
+ | - Click on Advanced. The dialogue displays advanced settings. | ||
+ | - In the drop-down field, set the authentication method to Windows. | ||
+ | - Enter your Windows (Admin) login, the domain (if used) and the Windows password. | ||
+ | - Click on Log On. | ||
+ | - The end user will need to click **Yes** on UAC pop up. | ||
+ | - TeamViewer on the **remote PC** will restart. | ||
+ | - Click Connect again and use the **Advanced** option to login with local Admin credentials | ||
+ | |||
+ | Now you will be able to see and control UAC messages. | ||
+ | |||
+ | |||