For AI agents: the complete documentation index is available at https://www.jumpserver.com/docs/llms.txt, the full documentation bundle is available at https://www.jumpserver.com/docs/llms-full.txt, and this page is available as Markdown at https://www.jumpserver.com/docs/operations/device-manager.md.
🎉 JumpServer v5.1.1 is available. See what's new →
  • v5

    • Device Manager

    Enterprise Edition

    Device Manager (JDMC) requires JumpServer Enterprise Edition. The entry is available only when the deployment includes JDMC and the license and account permissions allow it.

    Request 14-day free trial

    Device Manager opens JDMC, the host operations console that is deployed alongside JumpServer. It manages the server and containers that run JumpServer — not the assets protected by JumpServer.

    Most of the operational tasks covered in this section are available from Device Manager: backup and restore preparation, upgrade preparation, network and certificate changes, disk expansion, license management, container status and restarts, log inspection, and primary/standby setup. Use Device Manager when the task targets the JumpServer host or its containers.

    Warning

    Device Manager actions affect the whole JumpServer deployment and can interrupt active sessions. Restrict access to authorized administrators, plan a maintenance window, and back up the deployment before changing network, disk, or availability settings.

    Open Device Manager

    From JumpServer, open System Settings > Device Manager. The console opens in a new tab and reuses the current sign-in.

    If you open https://<jumpserver-host>/jdmc/ directly, sign in with the server's root password and accept the user and privacy agreements. Device Manager shares the JumpServer host name and is served under the /jdmc/ path.

    For the entry, sign-in, and field-level details, see Device Manager.

    What you can manage

    Device Manager dashboard

    Dashboard

    The default page summarizes the host:

    • Resource usage cards for the server
    • CPU and memory trend charts
    • Host information, including the operating system and deployment details

    Use it as the first check before maintenance, or after a change, to confirm that the host is healthy.

    System management

    AreaOperational use
    Network configurationManage interfaces, routes and gateways, DNS, and Docker networks
    Domain configurationSet the access domain and view or update the service certificate
    Disk managementExpand a data disk and review mount-point capacity
    License managementCopy the machine code and upload a JDMC license
    Service settingsChange the root password, port exposure policy, SNMP settings, and system time
    Primary/standby managementInspect and configure a two-node high-availability cluster

    Network configuration in JDMC

    Application management

    AreaOperational use
    Data backupBack up configuration files, the database, system logs, and session recordings; configure a remote SFTP target
    Application statusStart, restart, and inspect JumpServer containers, with streaming command output
    Application configurationEdit deployment-level settings that are not exposed in Lina
    Application logsView log files and follow live container logs

    Application status in JDMC

    High availability and maintenance

    New in v5.1.0

    JDMC adds primary and standby management, system upgrade management, and patch package management. Use primary and standby management to inspect and configure a two-node high-availability cluster, and use system upgrade management and patch package management to maintain the deployment without leaving the console.

    For the surrounding procedure, see Upgrade & Maintenance.

    Figure 1: JDMC system upgrade and patch package pages.

    Stronger persistent write protection

    Changed in v5.1.1

    High availability deployments apply stronger persistent write protection for databases and Redis across container restarts, re-creation, and failure recovery. Redeployment completion checks tolerate normal replication lag, and switchover waits and recovery coordination are refined to reduce false failure detection.

    Runtime environment check

    Every page except the dashboard shows a runtime environment result. A passing check reports Runtime environment normal. Open the details to see required and optional dependencies, the detected executable paths, and network checks. If a dependency is missing, Device Manager identifies it and the affected operations may be unavailable until it is installed. Select Re-check after fixing the dependency.

    Common operational scenarios

    ScenarioUse Device Manager to
    Prepare for an upgradeCheck the dashboard, take a backup, review application status and logs
    Change TLS or the access domainUpdate the domain and certificate, then verify the service
    Disk is filling upReview mount-point usage and expand the data disk
    License is expiringCopy the machine code and upload a new license
    Network or DNS changeUpdate interfaces, routes, DNS, or Docker networks during a maintenance window
    Container is unhealthyInspect application status and logs, then restart the affected container
    Build a two-node deploymentConfigure primary/standby management
    Collect evidence after an incidentExport logs and a configuration backup

    One console for most operations

    Most of the operational work described in this section can be completed from Device Manager. The table below maps the surrounding Operations topics to the console areas that support them.

    Operations taskDevice Manager area
    Backup preparationData backup for configuration, database, logs, and recordings
    Configuration changesApplication configuration and Network configuration
    Network and port reviewNetwork configuration and Service settings
    HTTPS and certificate changesDomain configuration
    Disk capacity expansionDisk management
    License renewalLicense management
    Upgrade and maintenance supportDashboard, Data backup, Application status, and Application logs
    Container troubleshootingApplication status, Application logs, and the runtime environment check
    Security hardeningService settings: root password, port policy, SNMP, and system time
    High availabilityPrimary/standby management

    Device Manager complements the procedures in this section rather than replacing them: use it for host and container actions, and follow the linked page for the surrounding process, validation, and rollback steps.

    Operational boundaries

    • Device Manager operates on the host and containers; JumpServer Console operates on organizations, users, assets, accounts, and authorizations.
    • Device Manager is not a replacement for Backup & Restore or Upgrade & Maintenance; use it as the host console that supports those workflows.
    • Some actions require root-level access and a healthy runtime environment. Do not run host-level changes during active maintenance windows without a rollback plan.
    • The Device Manager entry and available menus depend on the deployment and the account's permissions.

    Version history

    VersionChange
    v5.1.1Improved persistent write protection, redeployment checks, and switchover coordination in high-availability deployments.
    v5.1.0Added primary and standby management, system upgrade management, and patch package management.