Unsolved
5 Posts
1
762
October 14th, 2020 10:00
WMS and ThinOS 9 moving in the wrong direction
In an age where the IT industry is moving toward configuration as code with a heavy emphasis on automation, it seems like Dell is taking the opposite approach with the release of ThinOS 9. Where ThinOS 8 was capable of consuming INI format configuration files, the only option for configuring Wyse terminals with ThinOS 9 is to use a clunky web interface with a limited (if any?) API or option to import/export plain text configuration data.
Am I wrong about this? Does this not seem like a strange choice to anyone else?
I sincerely hope that Dell comes to their senses one day and incorporates more DevOps friendly features into WMS.
No Events found!
daviddrum
1 Rookie
•
47 Posts
0
October 16th, 2020 02:00
I agree.
On top of this, my impression is that the whole Wyse division at Dell is mismanaged and there are not enough investments going there.
I mean areas like quality of the buggy ThinOS releases, quality of the documentation, WMS not supporting basic featured after being there for so long now.
Obviously, the decision to go away from developing ThinOS 8 was done years too late.
Now we are stuck with the old 8.x. firmware which does not have basic required features by the business, and the new 9.x which is so buggy I cannot even start rolling it out to test clients.
Wyse is simply losing the business, maybe that's the actual intention?
Mr_MikeB
1 Rookie
•
18 Posts
0
October 20th, 2020 06:00
Some of the OP I agree with, some I don't. Personally I really like the WMS system, especially the public cloud version - the fewer servers I have to manage on-prem the better, plus we can use a common management portal globally. I used WDM to manage our old terminals and whilst I did understand the ini file format, it does also seem a bit 'old hat' compared to WMS. Maybe I just have a simpler set of requirements than others.
I do agree with the earlier comment about ThinOS 9, it really has been a shambles. Buggy, slow, features that were promised taking forever to appear, and so on. Trying to use it with a headset for Teams is an exercise in frustration. I am very glad that most of my company is WFH at the moment, as bluntly it's a .
One of my managers made a comment when we suddenly found out that the Wyse 3040s were not supported for video calls on Teams, that we should look elsewhere at iGels for example. At the time I resisted it, as Wyse have always been good in our environment, but 2-3 months later the 5070s we bought are still not fit for purpose - maybe he had a point after all.