Forum Replies Created
-
Posts
-
Hello Jim, until now we have always installed the simple ThinOS image and not the merlin image. What is the difference?
We are using WMS on premise.Hello Chris S, thank you for the information.
What is the best way to migrate registered devices from server WYSE1 to new server WYSE2 and get them registered on that new server?Hello Vinz,
the updates went fine like you described, thanks for that.Still 1 issues though!
* the host name has changed to something like WT2CEA7F3503A0The other issue has been solved by setting the group token in the policies as well
(the device jumped back to the device group where it was a member before the upgrades)
You can do that in ThinOS 9.x – Services – WMS SettingsHello Vinz,
the updates went fine like you described, thanks for that.2 issues though!
* the host name has changed to something like WT2CEA7F3503A0* the device jumped back to the device group where it was a member before the upgrades
Hello Jim, first of all thanks for the info!
Lot of people are several versions behind, because all these former 9.1.x versions simply didn’t work at all…By the way, what would be the most suitable path to upgrade from 8.6.710 to 9.1.5067?
thanks a lot
Is there still no solution to upgrade in a smooth way from 3.3.1 to 3.5 (or even newer 3.5.2 now)?
I still get the wrong Mongo DB version error.I restored my VM with Wyse Version 3.3.1 again.
It’s pretty anoying that the upgrade to v3.5 can’t be done in a “normal” way/procedure.
Anybody any other ideas?
thanks
PeterThe update to v3.5.0.866 went fine, no errors.
But now the webpages are no longer available??
Both don’t work anymore 🙁
https://wyseserver.domainname.be/ccm-web
https://wyseserver.domainname.be/ccm-web/adminOk, you mean “mongod.log”?
Because in that file I can see an entry “db version v4.2.16”Hello, I ran into problems when doing the upgrade like IT D mentions to do.
I can’t find the file “mongod.txt” either??
Please advise.
thanks a lot
Peter@CG,
additional packages are indeed installed in step 3, like for example the Citrix Workspace app ( Citrix_Workspace_App_20.12.0.12_1.pkg-V20.12.0.12.1)regards
Peter@edv-hotline
Yes WMS-service is connected on the devices and full functional.
I checked this by making changes in policies, rebooting the devices, and all changes are properly propagated.I had similar problems with losing the registration/connection at first as well, but have been able to solve as follows:
The trick to get them all working is the following:
1. start from legacy ThinOS v8.6_606
2. Config the firmware legacy policy to upgrade from v8.6 to v9.0_4024 at first
3. Config the firmware version 9 policy to do an upgrade afterwards to v9.1_1131I have setup several devices this way now, and they all seem to work fine.
regards
PeterI think I might have found a temp solution here !
I had one device 3040 working perfect, and a lot of others didn’t even register in WMS.The trick to get them all working is the following:
1. start from legacy ThinOS v8.6_606
2. Config the firmware legacy policy to upgrade from v8.6 to v9.0_4024 at first
3. Config the firmware version 9 policy to do an upgrade afterwards to v9.1_1131I have setup several devices this way now, and they all seem to work fine.
regards
Peter
