LogoLogo
LogoLogo
  • Welcome
    • Navigation
  • RealmJoin Deployment
    • Onboarding
    • Required Permissions
    • Infrastructure Considerations
      • Multi User Devices
    • Migration to RealmJoin vNext
  • User, Group and Device Management
    • Overview
    • User Profile
    • Organization Details
    • User, Group and Device Lists
      • Advanced Search
      • User Details
      • Group Details
      • Device Details
    • User and Group Settings
      • Available RealmJoin Policies
  • App Management
    • Packages
      • Package Store
        • Application Store Details
      • Package Management
      • Package Details
      • Package Assignments
        • Package Migration
      • Package Settings
      • Packaging Requests
        • Organic Packages
    • AVD Templates
  • Automation
    • Connecting Azure Automation
      • Required Permissions
      • Runbook Parameters
    • Runbooks
      • Runbook Customization
      • Runbook Permissions
      • Naming Conventions
      • Runbook Scheduling
      • Runbook Logs
        • Runbook Job Details
      • Runbooks Changelog
    • Requirements
    • Remediation Scripts
  • RealmJoin Agent
    • Features
      • Local Admin Password Solution (LAPS)
        • KeyVault
        • Application Insights
      • Notifications
      • AnyDesk Integration
        • AnyDesk configuration
      • App Deployment using the Agent
        • RealmJoin ESP
    • Deploying the Agent
    • User Interface
  • Logs
    • Connecting Azure Log Analytics Workspace
    • Audit Log
  • RealmJoin Settings
    • Overview
    • General
    • Roles and Permissions
      • Pre-defined Roles
      • Custom Roles
        • Available Permissions
    • Group Namespaces
    • Workplace Cloud Storage
    • Self Service Forms
  • Developer Reference
    • RealmJoin API
      • Authentication
    • Interacting with Runbooks
    • Simulating a Runbook Environment
    • Local Admin Password Management
  • Other
    • FAQ
      • Security
    • Troubleshooting
      • Package Installation Issues
        • Collecting Logfiles
        • Logfiles Structure
        • Analysing chocolatey.log
        • Troubleshooting failed chocolatey packages
        • Troubleshooting failed craft packages
        • Fixes for common issues
        • Intunewin Debugging
      • LAPS Issues
        • LAPS account passwords cannot be retrieved
        • Requested LAPS Accounts are not being created
    • Changelog
  • Legal
    • Licensing
    • Support
  • RealmJoin Website
Powered by GitBook
On this page
  • Deploy AnyDesk clients
  • End-User client
  • Supporter client
  • Group settings for end-user client
  • Back-End Integration

Was this helpful?

Edit on GitHub
  1. RealmJoin Agent
  2. Features
  3. AnyDesk Integration

AnyDesk configuration

Last updated 29 days ago

Was this helpful?

Deploy AnyDesk clients

In short, the following actions are required:

  • host end-user client on a publicly available URL and add to RealmJoin

  • request supporter client as custom RealmJoin package

End-User client

Please host the end-user client on a publicly available URL. You can simply use RealmJoin's Workplace Cloud Storage Solution for this.

A direct (public available) download from my.anydesk.com is not supported as it might be protected by services like Cloudflare.

Download the current end-user client from your my.anydesk.com instance.

Note, that you are responsible for updating the version on a regular basis.

Simply go to , upload your EXE and copy the link:

Supporter client

Once the package is ready assign it to the desired users/supporters. Old AnyDesk versions will be uninstalled automatically.

Note, that you are responsible for updating the custom client and request updated versions of your package on a regular basis.

The RealmJoin package "AnyDesk Custom Client" (also known as "AnyDesk Supporter Client Setup Launcher") is no longer supported (announced in February 2024). Please use the new process stated above and delete the old package.

Group settings for end-user client

Use a JSON policy to configure AnyDesk in the group settings. The following JSON contains all configurations:

Key: Integration.AnyDesk Value:

{
  "Enabled": true,  # activate integration
  "BootstrapperUrl": "https://xxxx/AnyDeskEndUser.exe", # public download URL
  "CustomClientSuffix": "xxxxxxx", # custom client suffix (see my.anydesk.com)
  "TrayMenuTextEnglish": "Start remote session" # optional: change text in tray menu
}

Back-End Integration

To enable the backend integration the following information is required:

  • AnyDesk License ID

  • AnyDesk API Password

  • Custom Client Prefix

Afterwards, please update the AnyDesk configuration in RealmJoin with the new URL as stated in the .

Please download your current supporter client (as MSI) and request it as a new RealmJoin software package via the package request formular under .

Send this information to to have the integration activated.

portal.realmjoin.com
RealmJoin support
article below
https://portal.realmjoin.com/organization/other-files
Overview in the portal