Control Machine

The “Control Machine” page provides a list of Agents along with the ability to quickly launch Remote Control sessions. The page is specifically designed as an end-user landing page - for an end-user who requires the ability to remote control a specific machine(s).

As an example, if you support end-users who require access to their office workstation(s) when working from home, you can create a VSA account for each end-user and allow access to this new page via User Role Access Rights.

The “Control Machine” page can be restricted with User Role Access Rights. User Roles have been enhanced to allow visibility of the page and visibility of the Actions such as the “Remote Control” and “Native RDP” options.

• The “Remote Control” action will
  • launch a standard VSA Shared Session on a Windows or macOS Agent
  • launch a terminal session on a Linux Agent
• The “Native RDP” action will launch the new “Native RDP” feature (see Remote Control: Native RDP section in these release notes for details)

Note: On the “Control Machine” page, the “Remote Control” and “Native RDP” Actions require the “Live Connect > Desktop Access” User Role to be enabled. To manage User Roles, navigate to the User Roles > Access Rights page.

Filtering Evaluation for the New Control Machine Page

The Control Machine page contains a new VSA filtering capability.

Filters on the same field are evaluated with an implicit OR. Filters between different fields are evaluated with an implicit AND. Take the following example:

The above expression is equivalent to:

Status = Online AND “Machine ID” in (“vsaqaw81-001.testmarry.marryorg”, “ws-jiwank-02.root.kserver”)

Freeform searches are also supported. When using the wildcard search functionality, all page columns will be scanned to refine the search.

In the example above, by adding a freeform search of “w81” the results of the original expression would be filtered to include only results containing the text “w81” in any field.

Multiple search fields are supported. Multiple freeform searches are evaluated with an implicit OR.