Remote Control for Network Devices

The VSA has been updated to support initiating remote control operations using HTTP, HTTPS and SSH or protocols over custom TCP ports for all Assets within the VSA, which includes both Agents and Network Devices that have been promoted to Assets.

Once a device has been discovered through Network Discovery and subsequently promoted to an Asset, or if a device has had an Agent deployed to it, it will be displayed on the Remote Control -> Operations -> Control Machine page.

From here, each Asset can be enabled with new remote control services by clicking the "Actions" button and selecting the "Remote Services" submenu. Remote services like HTTP, HTTPS and SSH can now be enabled, along with a feature to support adding custom protocols using our new port tunnelling technology.

For Assets that do not have Agents present, the VSA will leverage an existing Agent on it's Local Area Network as a proxy for the remote connection. This proxy agent will be selected automatically, or you can designate a manual proxy by selecting an agent on the same network as the target asset by changing the proxy setting from "Automatic Proxy" to "Manual Proxy" on the Actions -> Remote Services screen.

Once you have enabled an Asset with a given remote service, you can initiate remote control to that service via the Assets "Action" menu and select the remote service, or you can access the enabled remote service through Quickview. You can also use the Live Connect Application itself by selecting "Assets" and clicking the Remote Services button.

Upon launching remote control to a given service for an Asset, the VSA will run the installed desktop Live Connect application on your machine. If you select HTTP or HTTPS, your default local desktop browser will be launched, connecting you to the intended web page of the target asset. If you selected SSH, an SSH session will be opened up within Live Connect. If you selected a custom tunnel, a tab will launch within Live Connect that displays a local TCP port you can connect to on your administrative machine that will be tunnelled to the target endpoint -- you can use this to launch any kind of client-side application you want which will be connected to the target port on your intended asset.

Have more questions?

Contact us

Was this article helpful?
3 out of 3 found this helpful

Provide feedback for the Documentation team!

Browse this section