- This topic has 3 replies, 2 voices, and was last updated 3 years, 1 month 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.
Tagged: firmware
Hello,
we are using WMS 3.0 and all our Thin Clients running 8.6 027 RTME 2.5.
I created a new group to apply 8.6 606 and RTME 2.8.
When I move a client to the new group it applies the fw update instantly instead of waiting for the next reboot even so the live upgrade is deactivated in the config. I thought maybe it is meant in reverse but activating it changed nothing.
Anyone encountered this before ?
The 2nd problem is that some clients do not apply the rtme package. I get an error “download not possible or illegal package”. These clients are in the same network . I even tested it on the same ethernet plug and same ip address. Some do some not.
Any ideas welcome
Best regards
As long as the checkbox for “Disable Live Upgrade” is marked, an update should not start directly.
Is this setting also valid in the original group before moving?
RTME is only valid for x86 based clients. Which ones are you trying to use?
CG
Double Checked it is set in old and new group
we are using Model 3040 Thin OS 8.6 connecting to a ctrix environment. we use the rtme inside the shared desktop for skype. it is definitely working as it is showing connection to the local client. You know these two arrows connecting when it works.
After talking to the support we came to the following conclusion:
The live update paramater does not prevent instant usage of the firmware and settings when the client is moved from one group to another incl. a reboot. It does work if you apply the firmware update for an existing group. In that case the firmware is applied after the next reboot.
so kinda solved – I need to change my upgrade steps.
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. |