

When AnyDesk, and by extension, the AnyDesk Service, is installed on the remote device, it can interact with any software that requires administrative privileges as well as UAC elevation requests.Administrator Privileges and Elevation (UAC)ĪnyDesk for Linux / Raspberry Pi / FreeBSDĪ connection request to a remote client can be sent by entering the AnyDesk-ID or Alias of the remote client in the “Remote Desk” field on the local AnyDesk window.Īlternatively, one can also be sent by clicking the client tiles found in Discovery, Favorites, Recent Sessions, as well as the Address Book.Īfter a request has been made, the user on the local client must enter the unattended access password to connect if it has been set up on the remote device, or the user on the remote client must manually accept the connection request to start the session. Tasks that require elevations can only be confirmed by providing admin credentials. Users can change system settings, but only settings that will not affect other accounts. Users with this type of account can run but not install applications. Users with this type of account can change settings globally, install programs and pass the user account control (UAC) request without credentials.īy default, they have limited control. Administrator accountsīy default, they have complete control. Windows has two account types: Administrator and Standard User. To avoid UAC prompts with credential requests, log in to Windows as an administrator on the remote device. Every UAC action will still require administrator credentials. Administrator Privileges and Elevation (UAC)ĪnyDesk for Linux / Raspberry Pi / FreeBSDĮlevating the AnyDesk session will not change the windows session from standard user to administrator.
