-
-
Migration from eLux RP 6 to eLux 7
-
Performing the migration
-
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!
Performing the migration
The migration from eLux® RP 6 to eLux 7 can be carried out easily via a firmware update. Below you will find details on the requirements and the procedure.
Prerequisites
- The migration enablement 1.6.3-1 package or any newer version is available in the UC_RP6_X64 container and is defined in the current eLux RP 6 image.
-
The following migration files are available in the UC_ELUX7 container:
- `migrationfiles-<version>.tar.gz` - `migration-system-<version>.idf` - recovery_systemEFI.rdf
- The eLux 7 target image (.idf) is defined in the UC_ELUX7 container and has the same name as the current eLux RP 6 image (.idf).
- In the device configuration, the container variable
__CONTAINER__
is specified for the firmware path.
Preparing the migration
The migration enablement package for eLux RP 6 required for migration and the migration files for eLux 7 are provided via a separate download link.
Web-based ELIAS 18
- Import the migration enablement package via ELIAS 18 into the eLux RP 6 Container UC_RP6_X64.
- Define the migration enablement package with activated FPM for the One Step Migration to the current eLux RP 6 image (.idf) in the UC_RP6_X64 container.
- Import the archive
migration-package-<version>.zip
into the container UC_ELUX7. -
Define the eLux 7 target image (.idf) in the UC_ELUX7 container.
- The image should have the same name as the current eLux RP 6 image (.idf).
- If a name other than the current eLux RP 6 image (.idf) is to be used for the eLux 7 target image (.idf), an Advanced file entry must be set before the migration:
File Section Key Value /setup/terminal.ini UpdateInfo MigrationIdfUrl <URL>
The URL must not contain the container variable
__CONTAINER__
in the firmware path. Instead, the container name must be specified. *Example:https://MyWebServ.domain.com/elias/container/UC_ELUX7/MyImage.idf
Legacy ELIAS
- Import the migration enablement package via ELIAS into the eLux RP 6 Container UC_RP6_X64.
- Define the migration enablement package with activated FPM for the One Step Migration to the current eLux RP 6 image (.idf) in the UC_RP6_X64 container.
- Unzip the archive migration-package-
<version>.zip
and copy the migration files (migrationfiles-<version>.tar.gz
, migration-system-<version>.idf
, recovery_systemEFI.rdf) into the UC_ELUX7 folder. -
Define the eLux 7 target image (.idf) in the UC_ELUX7 container.
- The image should have the same name as the current eLux RP 6 image (.idf).
-
If a name other than the current eLux RP 6 image (.idf) is to be used for the eLux 7 target image (.idf), an Advanced file entry must be set before the migration:
File Section Key Value /setup/terminal.ini UpdateInfo MigrationIdfUrl <URL>
The URL must not contain the container variable
__CONTAINER__
in the firmware path.Instead, the container name must be specified. *Example:https://MyWebServ.domain.com/eluxng/UC_ELUX7/MyImage.idf
Important:
The migration files must not be changed manually.
The devices must not be switched off during the migration.
Devices should be connected via LAN, WLAN, VPN und IEEE 802.1X during the migration. Using WWAN connections (i.e. LTE) is not supported. During the migration via VPN the VPN-connection needs to be reconnected after each reboot.
Please do not use the firmware settings “Check for new image version on start / on shutdown” during the migration process.
This can lead to an incorrect device configuration (e.g. Citrix StoreFront application definition), which requires a remote factory reset.
Migration process
The migration is triggered by the installation of the migration enablement package with activated One Step Migration FPM on eLux RP 6, if the device fulfils the migration requirements for eLux 7.
The migration requirements to be checked are:
- 8 GB HDD or more
- 4 GB RAM or more
- Boot Mode UEFI
- eLux RP 6 versions: 2302 LTSR, 2209 CR, 2104 LTSR CU3, 2104 LTSR CU4
If the device does not meet the migration requirements, a new check is carried out each time the device is restarted as long as the migration enablement package is installed.
A system message informs the user that the migration is due in a few minutes. During the migration, an eLux 7 base image is installed first and the eLux 7 target image is installed automatically in a further step.
Note:
Once the migration is complete, it is no longer possible to downgrade to an eLux RP 6 version with the old partition layout using a firmware update. Please use PXE recovery or USB stick recovery if a downgrade is required.
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.