/i/2003991636.png?fit=%2C&ssl=1)
ARM is therefore anything but a simple assignment for MS. MS is an Enterprise player that tries to meet their needs / wishes as much as possible, whereby the strength does not lie in Windows or Office itself, but with the integration of everything. That integration is also where they make money, why are you going to a pro version? Domain & GPO. Why are you going to an Enterprise? Analytics, App-V deployment, virtual desktop. Then you either have to put MS servers with CALS in between or you have to step into the cloud story, that cloud story starts for a few euros / month but an MS 365 E5 costs 53.7 euros per month, excluding VAT, per user. Then you have not yet tapped support contracts, file servers or one of the many other applications and / or options within their cloud. The price strategy has always been, getting in is as good as free (they earn nothing at Windows home), getting into the cloud is also as good as free, however the more you purchase the faster the price rises, in a nutshell, that is always has been the way of working in MS.
Sometimes they seem to integrate a little too much and are rightly or wrongly criticized for that, Teams with all its different user cases and third party integrations is an example of this. MS can certainly release a working Windows on ARM in the short term, Windows RT is just proof of that. However, the RT version did not get off the ground, why, the whole integration was missing, no domain join, local but of course no GPO, etc.
Windows RT was a consumer Windows, not Enterprise. That also means that there are no bulky support contracts. That also means that there are no extended support, long term service builds. Something that ordinary Windows does take a piece of, if the large customers who pay millions per year report a problem and it is fixed, then, if applicable, the home user also gets that fix.
But MS makes no money at all from Windows for the consumer, that is in the almost free part of their range. For MS, a consumer Windows like Windows RT is doomed to fail before it is even developed, I don’t even understand why they ever thought that was a good idea unless it was just their expertise.
MS must therefore come out with a Windows ARM that does have full Enterprise integration, and that requires a huge amount of adjustments. If you add that to your SCCM and you push a SCCM client, it doesn’t expect ARM. When you add that to your Intune, you push an Intune client, but it doesn’t expect ARM. My domain controller does not expect Windows clients on ARM, nor do I have GPOs specifically for ARM devices and what happens if my current GPOs are applied? And then I only barely touched basic integration, the tip of the iceberg.
Besides, those fat customers with their thick support contracts & SLAs, you can’t just release an update to add ARM Windows support and say, oops, it’s running unstable. If SCCM messes up with 20,000 clients, then not only that client has a big problem, but MS too. MS has to release updates for almost their entire product range.
So yes, that takes time, much more time than we are used to from manufacturers who are purely on the consumer market and therefore do not have to take all of this into account because everything around is simply not there, or because you can easily get legacy support from consumers. fall.
[Reactie gewijzigd door sprankel op 28 november 2020 17:32]
–
