Content Comparison

...

The ExcludedTabs section allows you to exclude one or more tabs from the Local UI application, or, hide specific channels within a specified tab. If you wish to exclude all channels within a specific tab, enter the TabName and ensure the ExcludedChannels array is empty ([]). If you wish to exclude only specific channels within a tab, then enter the names of the channels to be excluded within the ExcludedChannels section (“Channel1”, “Channel2”, etc.).

An additional property HelpLink can be added to the file to supply your own URL to be launched when users click the help icon (example: "HelpLink": "https://UrlToYourSupportPage")

Once the UiService.config file has been updated, deploy it to the remote agent by uploading via the Gateway UI. You can then install the Local UI by deploying and running the msi package. Once installed, launch the application and fill in the connection details. If a connection cannot be established, the reason should be displayed as part of the connection output.

Detailed debugging of the Local UI service can be done by inspecting the remote agent log file(s), specifically %programdata%\Connexion.Integrator\logs\Integrator.RemoteAgent.txt. Debugging of the Local UI application can be done by inspecting the %programdata%\Connexion.Integrator\logs\RemoteAgent.LocalUi.txtfile on the Local UI host.

The Local UI will cache credentials when connecting to a remote agent hosted on another machine. It will not cache credentials if connecting to a remote agent hosted on the same machine. This allows multiple different users RDPing into the remote agent host to supply proper credentials.

Audit information generated by the Local UI is stored on the remote agent host under the %programdata%\Connexion.Integrator\audit folder. Currently, no viewer is supplied to view audit information. This information should be pulled from the remote agent and put into long-term storage in a similar fashion to both Connexion and Gateway. One option would be to unwrap the audit information and store it within your enterprise audit store, or, push the files to an S3 bucket. A sample channel demonstrating this is attached.