- This topic has 16 replies, 6 voices, and was last updated 2 years, 7 months ago by
.
-
Posts
-
We notice, if we dowgrade a device firwmare 9.1 to 8.6 the specific 9.1 device settings still exist. We cannot acces to the 8.6 settings. Like you se above This is wdm url for a device not update to 9.1 https://wmsserver.symta.fr/ccm-web/admin/device/36 https://wmsserver.symta.fr/ccm-web/admin/group/8/device/36?deviceType=6 And this is wdm url for a device downgrade after update to 9.1 https://wmsserver.symta.fr/ccm-web/admin/wms20/configuration/device/64 https://wmsserver.symta.fr/ccm-web/admin/wms20/configuration/deviceException/64?deviceType=6 Thanks for your help.
Hi,
if you “force unregister” the client, delete it from the device page and let it re-register, it should return to normal….
Regards
Volker
No this is the problem, when i delete the device, and re-register it, i can’t access to the 8.6 settings. only the 9.1 settings.
What settings do you mean?
Any 9.x device can only be downgraded via USB Imaging. You cannot downgrade ThinOS 9.x via WMS.CG
Yes, Fisrt i downgraded the 3040 via USB imaging.
After i re-registred it to WMS. I can’t see the 8.6 settings, only show the 9.1 settings.
Regards.
Hi there.
@vdousset Did you ever found a solution for this because we are facing exact the same problem?Please explain a bit further.
Maybe one or two screenshots could be helpful.CG
Sorry that I didn’t react sooner, but I lost a little track of this topic.
The problem is that after I downgraded a device from firmware 9.1.1131 to 8.6.710 (latest merlin image I could find), when you go to the device to and click on “Create/edit exceptions” you get the settings for the 9.1.x policy and not those for the 8.6.x policy.
So you get this:
Instead of this:
Are you sure that the downgraded device has fully checked in to WMS and ThinOS 8.6 is shown as the running OS?
CG
Yes, I’m pretty sure. For your reference, here a screenshot of that specific device in the WMS devices list (but this problem applies to all thin clients that I downgraded):
I hope the screenshot is somewhat readable.
Could you delete the device with “Force” option? Then filter the devices with “Status=Not registered” and delete the device finally.
After that let the device check in again.CG
I confirm that CG’s suggestion works.
I just had the same problem:I downgraded a 3040 client with the USB imaging Tool to version 8.6_013 then to 8.6_807 via the group firmware policy update. No problem at all there.
I then did the same for another 3040 client, but this time the 3040 after initial boot to 8.6_013 was then upgraded to 9.1.3112 !
So I reflashed to version 8.6_013 but did not reboot it to avoid a new unwanted upgraded and I checked the WMS (3.3.1) : the specific parameters for the client were showing the 9.1 options only.
I inferrred that the client had a specific configuration in 8.6 version to upgrade to the latest 9.1 version, so I guess that the unwanted upgrade was caused by this now ‘ghost’ 8.6 configuration.So I followed CG’s advice and force unregistered the client and then delete it.
Upon registration, I got access to the 8.6 specific configuration.
- You must be logged in to reply to this topic.