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
  • Deployment Workflow
  • Start Remote session using tray Icon (Windows)
  • Trigger Start Remote Session via shortcut

Was this helpful?

Edit on GitHub
  1. RealmJoin Agent
  2. Features

AnyDesk Integration

Last updated 29 days ago

Was this helpful?

AnyDesk provides access to devices, including the ability to elevate rights using the RealmJoin . It can be installed on both Windows and macOS devices.

To establish a connection between two computers, AnyDesk uses ID numbers. Share your ID number with another user (who also needs AnyDesk). The other user will enter your ID number in the AnyDesk menu. Once you accept the connection request, they will have access to your desktop.

The RealmJoin Client for Windows eliminates the need to share ID numbers, as each device in an organization is linked to a unique ID. Administrators can request access to a desktop simply by identifying the device. However, depending on the configuration, the user must still accept the access request.

Deployment Workflow

Please follow . Steps in short:

  1. Order a license from AnyDesk.

  2. Tailor your AnyDesk settings and create custom clients for end-users and supporters by configuring them at my.anydesk.com.

  3. Host the end-user client and configure the AnyDesk group settings in .

  4. Request your custom supporter client as RealmJoin package.

  5. to enable the backend integration.

Start Remote session using tray Icon (Windows)

Once everything has been set up, the tray icon can be used to get support without sharing the ID number or downloading executables by hand. The users are instructed by their support agent to open the tray menu and click Start remote session.

This text can be changed! Create a setting with the key Integration.AnyDesk.Ui.TrayMenuTextEnglish in the backend.

This process downloads the appropriate executable and sends the ID number to the RealmJoin Portal. The support agent can then view the ID under device details and connect to the user's desktop.

Trigger Start Remote Session via shortcut

This process may also be initiated outside of RealmJoin's UI. Simply create a Windows shortcut with the target realmjoin:remotesupport:default. This will trigger RealmJoin and behave as if the user had clicked the menu entry.

LAPS feature
AnyDesk configuration
RealmJoin Portal
Contact RealmJoin support