-
-
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 to eLux® 7
Igel2eLux provides you with an easy-to-use tool to migrate your IGEL OS 11 endpoints and run the lean and secure operating system eLux 7.
The migration can be done fully automatically by distributing and running the tool centrally via the Universal Management Suite (UMS) or by accessing the tool from a network location.
When you execute 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.
Requirements
- The tool
igel2elux.shneeds to run as root (remotely or in a terminal window)
How to run
- Distribute the tool as a ZIP file on the Igel endpoints or on a network drive
- Extract the package on the endpoint
- Run the tool on the endpoint, using the parameters that suits your requirements
Once executed, Igel2eLux will perform the installation of eLux by using the image location that has been provided. No user interaction is needed.
After successful installation, eLux will boot and the endpoint can be onboarded as usual. If an issue is found, the tool will exit.
Parameters for igel2elux.sh
The syntax for igel2elux.sh:
igel2elux.sh --url <URL> OPTIONAL_PARAMETERS
| Parameter | Info | Description |
|---|---|---|
| –url | Required | Points to the relevant software container and the image definition file (IDF) which specifies the scope of the installation |
| –log | Specifiy a log file for the output of this tool, e.g. migration.log
|
|
| You can also use a network drive for ensuring a persistent log file | ||
By default, the log file igel2elux.log is created in the same directory as the igel2elux tool |
||
| –proxy | Specify a proxy address, e.g. 1.1.1.1
|
|
| –port | Specify a port number for the proxy, e.g. 8090
|
|
| –noreboot | If the parameter is given, the endpoint will not reboot after the installation | |
| If the noreboot option is used, the migration will not start automatically, but on the next boot | ||
| –debug | Verbose installation messages in the console output | |
| Stops in error situations and shows error messages for different cases | ||
| Without the parameter, the device will restart in case of an error without showing an error message |
Examples
Example-1: Migrate the IGEL OS 11 endpoint to the given eLux image and reboot
Syntax:
bash igel2elux.sh --url http://images.citrix.com/elux/myimage.idf
Example-2 Migrate the IGEL OS 11 endpoint to the given eLux image, write a log file, use a proxy and don’t reboot
Syntax:
bash igel2elux.sh --url http://images.citrix.com/elux/myimage.idf --log migration.log --proxy http://proxy.citrix.com --port 8888 --noreboot
Note:
The migration is possible with or without secure boot or a bitlocker
Share
Share
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.