ThinOS 10 2605 released

Below are steps I have seen for successful deployment, and some tips if you are struggling with succeeding. 

Engineering is aware, and if you are still struggling please open a support case. I will continue to edit this to add additional findings as I discover them. Please do not share your SR# in this thread, it will be removed.

**Update There is an identified issue with this update on the Dell Pro Micro thin client. Do not attempt this update on that platform**

1. Please review page 15 of the Release notes
   1. https://dl.dell.com/content/manual43738726-dell-thinos-10-x-2602-and-2605-release-notes.pdf?language=en-us
2. The below worked starting from T10 2602.555 and 765, I have not had time to test older builds yet.
   1. Ensure your WMS has Configui 1.10.847 applied. If you are WMS Cloud this is already done for you.
   2. Use a multi group/step approach
      1. Group 1, Apply Security Add on 
         1. SecurityAddon_2605.10.0009_T10.pkg
      2. Group 2, Apply 2605 firmware update 
         1. In BIOS Common Configuration, set the BIOS policy option Enable UEFI Network Stack to Disabled.
         2. If you have anything other than the factory BIOS PW set on the device you MUST set the current BIOS password in the security section of “BIOS Common Configuration, Dell Supported Device BIOS Settings”

Additional Notes/Gotchas if it is failing:
1. USB Boot must be disabled

2. Secure boot must be enabled

There is no ISO package with this release
3. Non Dell HW is not supported with this release.
4. 5. If a non factory BIOS password is set, then the BIOS Password must be in the policy that delivers the 2605 update. If the BIOS password is in multiple sections of the policy, they must match.
6. Confirm Security patch has been delivered to the device, if it is older than the 2602.765 build

7. There were no BIOS packages posted with this release. I am tracking this down.

8) “set new BIOS Admin Password” must be set to NO.  At this time you cannot change the BIOS password in the same policy.

9) It looks like BIOS versions matter.  Make sure your BIOS is current prior to starting the upgrade.

10) Remove any USB Bootable devices prior to updating

11) Confirmed that P2P shadowing appears to be broken

12) Confirmed that there was an undocumented security change to restrict access to "Central Configuration" in the local UI after successfully registering with WMS.   Engineering is aware and looking into a ConfigUI (WMS) option to re enable it.

If you end up in a boot loop

. Boot Loop Issue – Upgrade Prerequisites
To prevent the boot loop issue, the Security Add-on package must be deployed before the 2605 firmware upgrade. :
If the 2605 firmware package is deployed without first installing the Security Add-on package, the device may enter a boot loop condition.
Question
What troubleshooting steps can the customer perform to recover from the boot loop issue?
Answer
The easiest recovery method is to uncheck or remove the Root Package assignment in WMS and allow the device to revert from the pending package deployment.

Thanks for sharing this information. Unfortunately, the 2605 update is still failing for me even after installing the security add-on package and disabling UEFI network stack. I have opened support ticket <To protect you, your private information was removed from public view. All private data was saved to your private Case. DELL-Admin> as you recommended.

@nleva​ Thank you. Please follow up here with any solution you come to so I can add it to the master thread.

My test device was stuck in a boot loop as well but I didn’t use dedicated groups for this, just device overrides. Having to mess around creating new multiple new groups and move devices around will be annoying. There has to be a better way to handle this upgrade…

Same here, boot loop, the above steps were followed and getting the below messages after failed upgrade.

@harkx​ i had a similar thing, i noticed the device had a device exception for a package so the  SecurityAddon_2605.10.0009_T10.pkg wasnt installing. once i cleared that it installed 2605 fine.

@DELL-Scott H​ Any idea when Team Slimcore will be supported  

@DP2811​ I have yet to see anything from MS that it is available for Linux.  Once it is available, we can leverage it.   If you have any documentation or a contact that says it is please send it along so I can engage engineering. 

@harkx​ Bootloop is always tied to the security package not being installed or failing to be installed prior to 2605 update. 

@k_rind24​ Completely agree and we are providing that feedback.

@DELL-Scott H​ thank you!

Reading through both the 2605 Release Notes and the Administrator Guide, I'm not sure what the supported upgrade path is for ThinOS 9.x clients. All of my OptiPlex All-In-One 7420 clients are currently running ThinOS 2511 (9.6.4029). The guides specifically mention Root_2505.10_0076_signed.pkg, but WMS lists Root_2602.10_0555_signed.pkg-V2602.10.0555 as being available under the ThinOS 9 Config for OS Firmware Updates.

So is 2511 (9.6.4029) --> 2602 (2602_10.0555) --> 2605 (2605_10.2100) a supported upgrade path?

@Tolstoy88155​ 

There was not a T9>T10 2605 file released so I would suggest.

1. T9 2511
2. T10 2602
   1. ThinOS 9.5.3102 or Later to ThinOS 10 2602 Upgrade Package
3. T10 Security Package
   1. SecurityAddon_2605.10.0009_T10.pkg
4. T10 2605

Below are steps I have seen for successful deployment, and some tips if you are struggling with succeeding. 

Engineering is aware, and if you are still struggling please open a support case. I will continue to edit this to add additional findings as I discover them. Please do not share your SR# in this thread, it will be removed.

**Update There is an identified issue with this update on the Dell Pro Micro thin client. Do not attempt this update on that platform**

1. Please review page 15 of the Release notes
   1. https://dl.dell.com/content/manual43738726-dell-thinos-10-x-2602-and-2605-release-notes.pdf?language=en-us
2. The below worked starting from T10 2602.555 and 765, I have not had time to test older builds yet.
   1. Ensure your WMS has Configui 1.10.847 applied. If you are WMS Cloud this is already done for you.
   2. Use a multi group/step approach
      1. Group 1, Apply Security Add on 
         1. SecurityAddon_2605.10.0009_T10.pkg
      2. Group 2, Apply 2605 firmware update 
         1. In BIOS Common Configuration, set the BIOS policy option Enable UEFI Network Stack to Disabled.
         2. If you have anything other than the factory BIOS PW set on the device you MUST set the current BIOS password in the security section of “BIOS Common Configuration, Dell Supported Device BIOS Settings”

Additional Notes/Gotchas if it is failing:
1. USB Boot must be disabled

2. Secure boot must be enabled

There is no ISO package with this release
3. Non Dell HW is not supported with this release.
4. 5. If a non factory BIOS password is set, then the BIOS Password must be in the policy that delivers the 2605 update. If the BIOS password is in multiple sections of the policy, they must match.
6. Confirm Security patch has been delivered to the device, if it is older than the 2602.765 build

7. There were no BIOS packages posted with this release. I am tracking this down.

8) “set new BIOS Admin Password” must be set to NO.  At this time you cannot change the BIOS password in the same policy.

9) It looks like BIOS versions matter.  Make sure your BIOS is current prior to starting the upgrade.

10) Remove any USB Bootable devices prior to updating

11) Confirmed that P2P shadowing appears to be broken

12) Confirmed that there was an undocumented security change to restrict access to "Central Configuration" in the local UI after successfully registering with WMS.   Engineering is aware and looking into a ConfigUI (WMS) option to re enable it.

If you end up in a boot loop

. Boot Loop Issue – Upgrade Prerequisites
To prevent the boot loop issue, the Security Add-on package must be deployed before the 2605 firmware upgrade. :
If the 2605 firmware package is deployed without first installing the Security Add-on package, the device may enter a boot loop condition.
Question
What troubleshooting steps can the customer perform to recover from the boot loop issue?
Answer
The easiest recovery method is to uncheck or remove the Root Package assignment in WMS and allow the device to revert from the pending package deployment.

For those of you still seeing Boot Loops AFTER confirmed Security Add on installation. 

What size does it show in "System Tools>Packages"?