-
-
Migration from Igel OS to eLux 7
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Migration from IGEL OS 11 or Stratodesk NoTouch OS to eLux® 7
Igel2eLux provides you with an easy-to-use tool to migrate your endpoints running IGEL OS 11 or Stratodesk NoTouch OS and run the lean and secure operating system eLux 7.
The migration can be done fully automatically by distributing and running the Igel2eLux tool centrally via the Universal Management Suite (UMS) or Stratodesk NoTouch Center or by accessing the tool from a network location.
When you run igel2elux.sh, a new partition is created on the local hard drive. From this partition, the migration process is started and the eLux 7 operating system defined by the image is installed.
Downloading the software
- Sign in to the myelux.com portal.
- In the Products & Downloads section, select Tools and then Migration tools
- Download the latest igel2elux
.zipfile.
802.1X Network Setup Guide for the migration
Prerequisites
- The device must be booted using UEFI. If the device is not booted via UEFI, a UEFI boot partition may not be available, which is currently unsupported for this migration.
- The zip file containing the migration tool alongside all necessary files should have been provided alongside this guide.
Steps to Configure 802.1X Network Settings
1. Extract the Migration Tool
Unzip the provided migration tool package (i.e. igel2elux-7.2511.0-2.zip) to a known location on your computer.
# unzip igel2elux-7.2511.0-2.zip -d /tmp/8021x_migration
<!--NeedCopy-->
In this example, we will use /tmp/8021x_migration as working directory directory.
2. Add the 802.1X Configuration
Create the following directory structure inside the extracted migration tool folder /tmp/8021x_migration/conf:
.
├── etc
│ └── wpa_supplicant
│ ├── client.key
│ ├── client.pem
│ ├── serverca.key
│ ├── serverca.pem
│ ├── serverca.sig
│ ├── wpa.conf
│ └── wpa.conf.elux
<!--NeedCopy-->
Note: you can create the directory structure shown above by extracting the example archive
8021xconf.xz:# mkdir conf && cd conf && xz -cd ../8021conf.xz | cpio -iv
Place your wpa_supplicant configuration files in the appropriate locations as shown above.
Note: The
wpa.confconfiguration will be used during the migration process, while thewpa.conf.eluxfile will be used after the migration to enable eLux to reach the Scout server.
3. Pack the 802.1X Confuguration
After placing the configuration files in the correct directory structure, create a file 8021conf.xz by running the shell script intrd-xs.sh as follows:
# ./initrd-xz.sh /tmp/8021x_migration/conf 8021conf.xz
<!--NeedCopy-->
This will create the 8021conf.xz file in your current working directory.
4. Include the file 8021conf.xz into the migration tool
Add the generated 8021conf.xz file into the igel2elux.zip file:
# zip igel2elux.zip 8021conf.xz
<!--NeedCopy-->
You can now proceed with the migration process using the modified igel2elux.zip file.
Debugging Tips
When calling the igel2elux script to perform the migration, you can enable the debugging by adding the --debug parameter. In case the migration fails due to 802.1X issues, you will be dropped into a debug shell and check for the log file /tmp/wpasupplicant.log for more details and any other log file under /tmp/*.
igel2elux.sh reference
Usage: igel2elux.sh [--url <URL>] [--proxy <proxy>] [--port <proxyport>] [--archive <URL or local path>] [--noreboot] [--log <logfile>] [–-debug]
| Parameter | Description |
|---|---|
--url <URL> |
Define to the relevant software container and the image definition file (IDF) which specifies the scope of the installation |
--proxy <proxy> |
Defines a proxy server |
--port <port> |
Defines the port of the proxy server |
--log <logfile> |
Defines a storage path for the log file. By default, the log file is saved in the same directory as the win2elux tool. |
| –noreboot` | Does not restart the system after installation of the recovery image and the boot loader. |
--debug | writes debug information in /tmp/`. |
|
--archive |
Path to igel2elux.zip |
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.