Search

Launchers: IGEL OS 10 Partition Launcher

Introduction

Requirements

Steps

Additional resources

Introduction

Login Enterprise Launcher is a host used as an endpoint to communicate between the Login Enterprise virtual appliance running a Test and the Targets (VMware, Citrix, etc.). This article describes the installation, configuration, and best practices for the Login Enterprise IGEL OS 10 Launcher.

To learn about the Launcher’s role in Login Enterprise, what it does, how it works, and more, see Launchers: Overview and best practices.

Requirements

  • 2 files are required and provided via download
    1. .inf (LoginPI.Launcher.Console)
    2. Tarball (LoginPI.Launcher.Console.tar.bz2)
  • IGEL UMS (Management UI)
    1. These files typically go into the following folder on the UMS server. "C:\Program Files\IGEL\RemoteManager\rmguiserver\webapps\ums_filetransfer\LoginVSI\"
    2. This can be placed on any file share, but you’d have to point it at that file share manually.
  • If you are using IGEL OS 11 and UMS 6, you will need to install an Enterprise Management Pack license.
  • A custom partition is created on the endpoint device. IGEL allows for a custom partition, which makes integration easy.

Steps

  • Boot IGEL endpoint device
  • Scan the network subnet with UMS and pick up the endpoint you wish to configure (VM or Physical)
  • Create a new Profile (you can do this before Steps 1 and 2). 

    (note… look for the blue triangles denoting changes you're making)

New Profile (this is all the stuff that comes with the profile if you import it versus building it yourself)

  • Create a new partition, setting the Size to 100 MB and the Mount Point to /loginpi.
  • Add new partition parameters. Click on the "+" (white plus) icon to create them. This will be written into appsettings.json when the launcher is initialized:
    • serverurl - the URL of the Login Enterprise virtual appliance (e.g., https://loginenterprise.lab.com)
    • secret - see below for instructions on how to get the secret

Frame 606.png

To get the secret, go to Portainer, open the identity server container,

Frame 597.png

open console,

Frame 598.png

  • Type “cd /run/secrets/” and “cat LAUNCHER_SECRET &&echo” copy the secret and paste it into the secret field (below).
  • Or, with Login Enterprise 4.1 and higher, you can find the Launcher secret in the Launcher overview under the download section of the Launcher files.

Frame 605.png

Frame 599.png

  • Setting the proper UMS password to access the share. Note the URL below should be the full path to the .inf file that is on the UMS share (e.g., http://192.168.1.101:9080/ums_filetransfer/LoginVSI/Login.Launcher.Linux.inf)

Frame 600.png

Click Add custom application if the Launcher doesn’t exist. This next step adds the Launcher to the desktop. The Autostart enables the Launcher to automatically run with the endpoint boots up. Add a new Custom Application and fill in the details as follows:

Frame 601.png

Other settings

Making an icon

Frame 602.png

The command above is “xterm -bg "black" -fg "white" -iconic -hold -e /loginpi/start.sh”

Making it work with the desktop integration

Frame 603.png

  • Here’s how you can change the hostname of the endpoint IGEL client (Terminal Name). This step isn't required if name resolution works and can always be tested by running ping from the terminal.

Frame 604.png

  • For the dual-homed PI server, you'll need to set up another NIC.  If you don't have a name resolution for the physical client, you can add host entries to the client config.

Additional resources