Reproducible steps:
- Go to Asset Dashboard and select asset requiring remote access
- Under Remote Sessions
- Clicking ACA thereby download and install ACA
- Select Desktop or some other remote connection type
- Dialog will appear with Remote Connection Status as Connected; otherwise, review 262511 to troubleshoot further
- Click Start Session button
Full Answer
What are Axeda remote access sessions?
Remote Sessions are connections through the Axeda® Platform to remote deployed assets configured to support Remote Sessions (as part of the related Axeda Gateway or Connector Agent project or in the Agent Embedded agent). As opposed to desktop-sharing access connections, these remote access sessions support "headless" computers (without monitors).
How do I connect to an asset running in Axeda?
Users can connect to assets running ADS using the Axeda Desktop Viewer (ADV) whose version is compatible with that of the Axeda Desktop Server running on the asset. When a remote session is started, the agent sends up the version of the Desktop Server application that is running, in a Desktop Application Version ( Dapv) message.
What are Axeda® connected machine management applications™?
The Axeda® Connected Machine Management Applications™ available for sessions must be defined in the project configuration for the Agent running on the asset. The Remote Application tool uses Application Bridge technology to provide a virtual bridge between your local network and the network behind the asset's firewall.
What is Axeda Desktop Server (ADS)?
The eMessage agents can run an application called Axeda Desktop Server (ADS) to support remote sessions with the asset where the agent is running. Users can connect to assets running ADS using the Axeda Desktop Viewer (ADV) whose version is compatible with that of the Axeda Desktop Server running on the asset.
What is connected access?
The Connected Access application (accessed through the Access tab) is a Web-based technology that enables one or more operators to securely view and operate the same remote desktop, through the Internet.
How to request desktop sharing in Access?
To request a desktop sharing session through the Assets tab, use the Asset dashboard Remote Sessions module to run the configured Desktop remote application configuration. If the session is allowed, you connect the Access Viewer computer to the session. If the Access Remote application is configured with a password, you will need to type that password to connect to the session. Additional requirements for this type of desktop sharing are as follows: the Access Remote computer must be configured to accept direct LAN connections; the Agent running on the asset must be configured with support for Remote Application sessions to its desktop; you must have privileges to the asset and the Assets tab.
What is access viewer?
You use Access Viewer or Desktop Viewer to connect to the remote desktop. If the server application is configured with a password, you will need to type that password to connect to the desktop. When the desktop sharing is through the Connected Access application or the Connected Service application, the Axeda® Platform enables and coordinates ...
How to share a session ID?
For desktop sharing through the Access application, you use the Request Session ID link to generate a shared session ID. Then, you connect the client computer to that session ID, and the operator at the server computer connects it to the same session ID. If the server application is configured with a password, you will need to type that password to connect to the session.
Can you share a desktop with Axeda Gateway?
When you define the project for an Axeda Gateway or Connector Agent, you select the Desktop type of remote session for communication through an Application Bridge. This type of desktop sharing does not require an operator at the server computer to permit the session. If the server computer is configured with Axeda® Policy Server support, then the ability to start a remote session on the asset is subject to the security defined for the Axeda® Policy Server.
Does IDM support remote desktop?
For other options, refer to Ways to Transfer Files to and from Assets. The IDM Agents do not support the Access Viewer and Access Remote Server for remote desktop connections. Similarly, the Connected Access application does not support remote session capabilities of the IDM Agents.
What is remote session in Axeda?
Remote Sessions are connections through the Axeda® Platform to remote deployed assets configured to support Remote Sessions (as part of the related Axeda Gateway or Connector Agent project or in the Agent Embedded agent). As opposed to desktop-sharing access connections, these remote access sessions support "headless" computers (without monitors). There are four types of remote sessions: Remote Terminal, Remote Application, Remote Browser, and Remote Desktop. The Remote Application, Remote Browser, and Remote Desktop types of sessions use the Application Bridge. For all three types, if a port is remapped because it is unavailable for a session, the Available Ports field in the Application Bridge Applet window displays the remapping. For example, if port 5920 is remapped to port 10000, the Available Ports field displays 5920 [10000], where the square brackets indicate the remapping.
What is remote terminal session?
o Remote Terminal sessions are connections from the local computer to a specific "interface" exposed by the asset. These connections are based on the standard protocols (Telnet and SSH). All communications to and from the asset are shown in a Terminal Emulation applet window. You type standard Telnet commands for the asset, and the applet window shows responses echoed back from the asset.
What is exclusive session?
non-exclusive sessions - you can connect to sessions in an exclusive manner, such that no one else can join, or in a non-exclusive manner, such that any other users with Remote Terminal privileges to that asset may join the session. If there are multiple users in a Remote Terminal session, you (the session initiator) have control of the session and all other users have view-only privileges. You can "pass" control to another user, at which point you have view-only privileges until you take control again. Users can request control. These control options are available in the Telnet applet window.