-
Interface of the Scout Console
-
-
-
-
Update to new partition layout (1.77 / 1.84 GB to 2.35 / 2.41 GB)
-
Update to new partition layout (2.35 / 2.41 GB to 3.75 GB)
-
Advanced device configuration and Advanced options
-
-
-
Client remote management by commands
-
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!
Update to new partition layout (2.35 / 2.41 GB to 375 GB)
eLux RP 6 2302 LTSR CU2 contains a modified partition layout that provides more space on the system partition for additional software packages. To upgrade to eLux RP 6 2302 LTSR CU2, please note the following information.
System requirements for the new partition layout
-
Memory size at least 8 GB
-
System partition size 2.35 GB / 2.41 GB
Devices with less than 8 GB memory size can be updated to eLux RP 6 2302 LTSR CU2, but the repartitioning will not be performed.
Downgrade to the previous partition layout
Once the repartitioning is complete, it is no longer possible to downgrade to an eLux version with the previous partition layout via firmware update. Please use PXE recovery or USB stick recovery if a downgrade is required.
Perform the firmware update
The update to eLux RP 6 2302 LTSR CU2 is done exclusively via a specially configured firmware update, which automatically triggers a second update. The image macro _P4 and the service package Custom updater (part of the eLux RP 6 2302 LTSR CU2 release) are used for this purpose.
The process is started by a firmware update to an image that has the image macro __P4_
in its name. This _P4__
image must contain the package [Custom updater] and must not be larger than 2.35 GB / 2.41 GB.
After the installation of the _P4 image on the device a restart is performed and the Custom updater starts the second firmware update automatically.
The second update installs the final image, which must have the same name, but without the image macro _P4 in the name and without the package Custom updater in the image. The size of this final image can be up to 3.75 GB.
Process
a. Currently installed image with system partition 2.35 GB / 2.41 GB Example: MyCurrentImage.idf
b. Firmware update to [eLux RP 6 2302]2 LTSR CU2 image with image macro P4_ in its name and the **Custom updater** package Example: MyNewImage__P4.idf / max. 2.35 GB / 2.41 GB
c. Automatic update to the final eLux RP 6 2302 LTSR CU2 image without image macro and without Custom updater package Example: MyNewImage.idf / max. 3.75 GB
Note:
The image with the image macro _P4__ in the name can be kept in the firmware tab of the device configuration until the update to the next eLux image. eLux RP 6 2302 LTSR CU2 ignores the macro and always checks the update against the final image without image macro.
Installing the update step-by-step
-
Create an IDF for eLux RP 6 2302 LTSR CU2 with the image macro _P4__ in the name containing the package Custom updater. Image size <= 2.35 GB / 2.41 GB. Example: MyNewImage__P4__.idf
-
Via ELIAS perform Save as for this IDF and remove the image macro _P4__ from the name and remove the package Custom updater from the image. Add more packages if needed. Image size <= 3.75 GB. Example: MyNewImage.idf
-
In device configuration > Firmware tab enter the name of the image with the image macro _P4__ in its name. Example: MyNewImage__P4__.idf
-
In Scout Console perform a firmware update via update command or update notification.
Recommendations:
-
Send the update command only to devices with the status “Switched on” (see parameters of the update command) or send a separate command to switch on the units before the update command. Otherwise, the devices could be switched off after the first update.
-
Using Check for new image version on start / on shutdown may result in a failed second update on some devices and is therefore not recommended.
-
Check the results
In Scout Console > Properties after a successful update to the final image UEFI devices should display the following values:
-
Partition info system 3,75 GB setup 256,00 MB update 3,75 GB (up to 20,00 GB) - Image | Image name without image macro
__P4__
in its name Example: MyNewImage.idf
Note:
Due to a missing boot partition, legacy BIOS devices should display the Partition info system 4,00 GB setup 255,00 MB update 3,75 GB (up to 20,00 GB).
Troubleshooting
Error / problem | Reason | Solution |
---|---|---|
Properties in Scout Console | The second automatic update via Custom updater was not carried out | Restart the device |
|
||
|
||
|
||
Properties in Scout Console | A second update was carried out, but not via the Custom updater. | Perform a manual update via Scout Console with a format of the system partition before update. |
|
||
|
||
|
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.