How to upgrade IGEL OS devices, how to skip v5 devices and only upgrade v10 devices?


Hi There – Curious on the best strategy for this scenario.

Customer has multiple locations and each location is broken into a directory, under that directory is a mix of UDC v5 devices, and newly purchased IGEL devices running v10. When I need to apply a firmware update that only applies to v10 for that location, if I applied it to the folder directly is the update process smart enough to know the targeted devices in the directory contains v5 and should be skipped?

They are older UDC devices which do not support v10? I see I can create views/jobs and be more targeted but first curious about the directory option. In general what would the recommended path be in a mixed scenario like this?


use firmware-update-profiles and apply them via views/ administrative tasks direct to the thinclients.


UMS will push profiles based on v10 to v5 clients as well, which of course can be an issue.

Maybe it is possible to sort them by folder (one v5 folder and one for v10s)? Or use suggestion from @member .


To avoid accidentally updating one of the UDC2 to UDC3 devices, 1) you can create a view that only contains UDC3 and assign the firmware to the view, likewise with your UDC2/v5 firmwares or 2) Create a profile that has the “enable update to v10” unchecked. I believe that is the default anyway, so all of your UDC2 devices should have that unchecked unless you have it enabled in another profile. No updating UDC2>3 unless you specifically allow it.


I missed in my previous answer that the question was about firmware updates and not profiles… Firmware is easier in that way, just as @member says above.


@member You can’t update UDC2 devices to UDC3 devices that easy. You need to migrate them which requires a specific upgrade license. For detailed information see kb.igel.com/igelos/en/upgrading-udc-devices-from-igel-linux-v5-to-igel-linux-10-2720839.html


@member Yep – very true! I was assuming there also might be conversion licenses uploaded in UMS.


@member the migration process contains a safety hurdle that only occurs on devices with IGEL Linux V5 – you need to activate a checkbox to allow the firmware upgrade to IGEL OS 10. To see this checkbox you have to create a profile based on firmware version 5.11.100. Profiles based on IGEL OS10 doesn’t have this checkbox.


ok im back! So many slack teams forgot about my question being asked until i’m back on-site here today! Great Feedback. So in this case, seems like a view which grabs all the V10 devices that need to be upgrades is the best way to push this out. Haven’t done the buddy updates before will look into that as each of these are remote store locations with limited pipes.

@member you bring an interesting point with Firmware update profiles – What would be the difference using the profile there versus just dropping the firmware on the specific directories that require it? I guess more granular control on the update settings?


the usage of Universal Firmware Updates requires no profiles, and/but overrides any profil-based updates further down in the tree (e.g. if you have to use ftp-buddy-updates for some directory).

Other than that you cant apply Universal Firmware Updates via administrative tasks.

I myself have all my Linux-based Thinclients under one directory. I can make use of the same profiles for all types of firmware (V4, V5, V10) – but not for the firmware-update, so i apply them directly to the thinclients via administrative tasks.


@member Thanks for all the info – You mentioned same profiles for V5/V10, how are you accomplishing that? I took care of the firmware update, but the profile requires a modification to update to the latest linux receiver for Citrix. V5 profiles which are currently applied to all V5/V10 devices (Just noticed this) of course don’t have this option. I have a new profile set with the same settings but configured to be based on newest firmware and with the correct receiver. I tested applying this to the V5 device and everything worked just the receiver version was downgraded to the lowest version supported on the V5 clients.

Is it recommended to just break the V5 and V10 devices down into two seperate directories? would be nice if you could attach some condition to the profile similar to views. This way it doesn’t matter if its applied to the directory instead it will only apply if condition is met such as underlining hardware/OS.


its (putting all Version in one dir) not best practise but works. you have to deal with profiles for updates, for receiver version and enabled features which are different. you either go for common options (in my case I have firmwares for 4,5 and 10 which use the same receiver version) or apply profiles directly to thinclients via administrative tasks.

i still hope – feature request was submitted here – Igel goes the way e.g. MS does with GPO to not only apply settings to directories/OUs but also to other parameters such as FW/OS-versions


Yup makes sense – Seems like the way things are designed now the recommended path would be to split V5/V10 into separate folders as newer LX10 supports later receivers the UDC old devices are stuck on LX5. once all customers clients are replaced and on LX10, can remove those legacy directories. Cool man, thanks for the chat. Will submit feature request.

Continue reading and comment on the thread ‘How to upgrade IGEL OS devices, how to skip v5 devices and only upgrade v10 devices? ‘.  Not a member? Join Here!

Learn more, search the IGEL Knowledge Base



Ask a question or comment on the above messasge thread?

Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.

Submit a question, or Join Today!


Popular Message Threads


Categories & Tags: