- This topic has 3 replies, 2 voices, and was last updated 6 years, 7 months ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Ok I been trying to figure out the best possible way to deploy the ThinOs to our users with VERY min user impact. I currently service about roughly 10k Wyse device around the world. Firmware 84. is about 25megs and the RTME package is about 3megs. Total we are looking at about 30meg file.
Last year we were in some cases, 3 full versions behind, so we had to do several upgrades which cased a major user impact. Now that we are just going from 8.3 to 8.4 it wont be as bad, but I still want to minimize the user impact.
We use CCM or WMS, and in here I do not see a easy deployment option for the firmware. So I am looking at a possible solution in deploying with little to impact to users. I really REALLY dont wantt to create a group and move users to it, but that seems the easiest way of doing it. I can not put the file out there and have users upgrade when they turn on b/c that would cause a issue with bandwidth with 10k devices.
I am open to any suggestion yall have.
You can easily use WMS to push the firmware out to the clients.
Just upload the firmware in WMS – Apps&Data. Then alter your ThinOS profile and add the desired firmware.
You could also do that as an exception on per device level, if you like – good for testing.
CG
Yea right now for testing I am doing the Exceptions.
In the App&Data altering the ThinOS profile, I upload the firmware there, but do not see a option on how to deploy it from there other than making available for doing it per group or an exception.
Correct, you can only push it through a profile and not directly from Apps&Data.
CG
Cookie | Duration | Description |
---|---|---|
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |