How to install the ConsoleAppLauncher

Modified on Thu, 28 Mar 2024 at 12:14 PM

The ConsoleAppLauncher is a new and faster way to execute Home Buttons and Custom Buttons of our five(9)s Console. This is a step by step guide on how to install and use it.


In summary

The RCViewerInstaller and ConsoleAppLauncher are to be deployed on devices that use the five(9)s Console.

Files:
C:\Program Files\LANDesk\ManagementSuite\RCViewer_win_installer.exe (EPM 2021.1 and up)
C:\inetpub\wwwroot\five9sWS\ConsoleAppLauncher\ConsoleAppLauncher.msi
or http://[CoreServerName]/five9sWS/ConsoleAppLauncher/ConsoleAppLauncher.msi

Step by Step Instructions

1. Install a five(9)s Console version of at least 4.7.37.
2. Install Ivanti RCViewer on the Client. The RCViewer_win_installer.exe" is found under:
EPM 2021: C:\Program Files\LANDesk\ManagementSuite\
EPM 2022: C:\Program Files\LANDesk\ManagementSuite\remotecontrol\RCViewer\


(To instead install it silently and for all users you can use the switches: /S /ALLUSERS )


Install for all users.
If possible, keep the default path. Otherwise take a note of the custom path and use it in step 5.
3. Copy the installer "ConsoleAppLauncher.msi" on the Core Server (C:\inetpub\wwwroot\five9sWS\ConsoleAppLauncher) to the Client.
4. On the Client, open the "ConsoleAppLauncher.msi" file and install the tool.
This registers the Custom URL Protocol "five9slaunch://".


A configuration file "ConsoleAppLauncher.json" for custom configurations is created in the install directory.
E.g. C:\Program Files (x86)\five(9)s\five(9)s ConsoleAppLauncher\ConsoleAppLauncher.json


For troubleshooting purposes, a log file is created in the local Application Data directory
%localappdata%\five(9)s ConsoleAppLauncher\ConsoleAppLauncher.log .
5. In case the RCViewer path was customized in step 2., it is necessary to replace the path in the newly created "ConsoleAppLauncher.json". Note that the path separator needs to be "\\".
The setup is now completed successfully.

Now clicking on Home Buttons like Remote Control, and on Custom Buttons of type "Executable" and a location of "Console Device As Logged On User" will use the ConsoleAppLauncher.
Whether it is registered on the client or not will be detected automatically. If we detect it is not installed, the Console will use the original way through Ivanti to execute the Button.
For additional control, there is an Admin setting in Admin -> General Settings -> Custom Buttons -> ConsoleAppLauncher Behavior. With this setting you can control whether to use the Ivanti Agent or the ConsoleAppLauncher.

Advanced information
A url call has the following format:

{protocol name}://{action}/{base64parameter}

• protocol name: "five9slaunch"
• action: e.g. "ping". This is the corresponding executable to start, as configured inside the .json file
• base64parameter: e.g. "Z29vZ2xlLmNvbQ==", for "google.com"

An example call is five9slaunch://ping/Z29vZ2xlLmNvbQ==

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article