How to automatically upgrade IGELs without bothering your users (Much)


ABSTRACT: Automated Firmware Upgrade Steps for IGEL UD & UDC devices.

Learn more, read the entire thread inside the IGEL Community o Slack

TESTING ASSUMPTIONS: Before each version upgrade, the method below would be tested on a variety of individual machines before performing en masse upgrade attempts.

STEPS:

*

Communication: Send a blanket email to the user community being upgraded notifying them that IGEL system will be sporadically upgraded automatically during badge-out/log-off. If any systems are unsuccessful or non-operational after the upgrade, be sure to instruct them to power off/on the systems before contacting the Service Desk.

*

Configure Upgrade Folders: Assign the Reboot-Post Citrix Session Profile along with the current IGEL Firmware to the respective “Upgrade” folder.

*

Move Devices to Upgrade Folder: Either Cut/Paste or Drag and Drop a subset of IGELs to the “Upgrade” folder. Due to bandwidth issues, limit the number of machines to 20 and don’t upgrade all systems in one area at the same time.

Note: Nothing happens at this point until a user “Badges Out” and disconnects (or logs outs etc.) from their Citrix VDI session.

*

Badge-out Trigger: Using the “Badge-out” event as a trigger ensures the system is not actively in use by Clinicians.

The Reboot-Post Citrix Session Profile also instructs devices to “Auto Update Check on Boot”

*

When a User Badges out, the IGEL system will automatically reboot after the Citrix Session ends. Note: Rebooting before doing an upgrade is an IGEL best-practice which makes it an ideal trigger. Upon reboot the firmware upgrade process begins automatically (see below) but the user is given a chance to cancel out of it.

Note: The upgrade might perform multiple reboots depending on the version or the number of firmware you have assigned.

Subsequent reboots: After the upgrade is complete, all IGEL systems in the “Upgrade” folder will continue to reboot at every badge-out (taking ~35 seconds) until the devices are moved out of the Upgrade folder. Also important to note, subsequent reboots skip the upgrade (the upgrade only runs once).

Move Upgraded Devices Back to Original Folder: Move upgraded IGEL Devices out of the Upgrade folder to the original entity folder (usually one level up).

Choose Next Reboot

ABSTRACT: Automated Firmware Upgrade Steps for IGEL UD & UDC devices.

TESTING ASSUMPTIONS: Before each version upgrade, the method below would be tested on a variety of individual machines before performing en masse upgrade attempts.

STEPS:

*

Communication: Send a blanket email to the user community being upgraded notifying them that IGEL system will be sporadically upgraded automatically during badge-out/log-off. If any systems are unsuccessful or non-operational after the upgrade, be sure to instruct them to power off/on the systems before contacting the Service Desk.

*

Configure Upgrade Folders: Assign the Reboot-Post Citrix Session Profile along with the current IGEL Firmware to the respective “Upgrade” folder.

*

Move Devices to Upgrade Folder: Either Cut/Paste or Drag and Drop a subset of IGELs to the “Upgrade” folder. Due to bandwidth issues, limit the number of machines to 20 and don’t upgrade all systems in one area at the same time.

Note: Nothing happens at this point until a user “Badges Out” and disconnects (or logs outs etc.) from their Citrix VDI session.

*

*

Badge-out Trigger: Using the “Badge-out” event as a trigger ensures the system is not actively in use by Clinicians.

The Reboot-Post Citrix Session Profile also instructs devices to “Auto Update Check on Boot”

*

When a User Badges out, the IGEL system will automatically reboot after the Citrix Session ends. Note: Rebooting before doing an upgrade is an IGEL best-practice which makes it an ideal trigger. Upon reboot the firmware upgrade process begins automatically (see below) but the user is given a chance to cancel out of it.

Note: The upgrade might perform multiple reboots depending on the version or the number of firmware you have assigned.

Subsequent reboots: After the upgrade is complete, all IGEL systems in the “Upgrade” folder will continue to reboot at every badge-out (taking ~35 seconds) until the devices are moved out of the Upgrade folder. Also important to note, subsequent reboots skip the upgrade (the upgrade only runs once).

Move Upgraded Devices Back to Original Folder: Move upgraded IGEL Devices out of the Upgrade folder to the original entity folder (usually one level up).

Choose Next Reboot


This is awesome Thanks @member


Much thanks David! This is handy.


Your welcome….It was time to give back to the internet instead of always being a “taker” 😉

Continue reading and comment on the thread ‘How to automatically upgrade IGELs without bothering your users (Much)’.  Not a member? Join Here!

Learn more, search the IGEL Knowledge Base



Ask a question or comment on the above message 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: