- 2 files are required and provided via download
- .inf (LoginPI.Launcher.Console)
- Tarball (LoginPI.Launcher.Console.tar.bz2)
- IGEL UMS (Management UI)
- These files typically go into the following folder on the UMS server. "C:\Program Files\IGEL\RemoteManager\rmguiserver\webapps\ums_filetransfer\LoginVSI\"
- This can be placed on any fileshare pretty much, but you’d have to point it at that fileshare manually.
- NOTE: 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.
- 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 we make)
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 sign to create them.hTis 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
NOTE: In order to get the secret you need to go to Portainer, open the identity server container,
- Type “cd /run/secrets/” and “cat LAUNCHER_SECRET &&echo” copy the secret and paste it in the secret field (below)
- OR with 4.1 and higher you can find the launcher secret in the Launcher overview under the download section of the Launcher files.
- 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)
Click on “add custom application” if the launcher doesn’t exist. This next step adds the launcher to the desktop. See Autostart below? This enables the launcher to automatically run with the endpoint boots up. Add a new Custom Application and fill in the details like this
Making an icon
Command above is “xterm -bg "black" -fg "white" -iconic -hold -e /loginpi/start.sh”
Making it work with the desktop integration
- Here’s how I changed 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 terminal.
- For dual homed PI server I had to setup another NIC. I didn’t have name resolution for the physical client so I added hosts entries to the client config