Didn't your IT guys test it out first?
I work for an engineering firm and we test everything out thoroughly before purchasing in bulk.
just an FYI, I read an article that Microsoft plans to phase out Silverlight in the near future, since everyone will be switching to HTML5, including MS.
It's true that the onus is on the buyer to test compatibility with existing systems. I tend to view Silverlight in a similar way as Microsoft marketing the Surface RT to the corporate space
without Outlook. What Microsoft is planning for phasing out Silverlight is less of a priority compared to existing support--academia, government agencies, and large corporations tend to have slow technology adoption cycles, often
painfully slow due to lack of funding and other resources. While Silverlight has a tiny percent of the overall market compared to Flash, I expect most of that percentage is in the academic and government sectors, though I haven't seen numbers.
Does the Silverlight plugin take up a huge amount of space? If it doesn't, and remembering that Flash is a third-party plugin, there isn't a good argument not to support it. (Java, on the other hand, is huge and Microsoft lost a lawsuit years ago and can't include it themselves.) Are there distinct versioning issues where there isn't backwards compatibility? Maybe there are additional issues at stake in including a working Silverlight plugin on Windows RT, but merely "we're phasing it out so you must follow suit" doesn't really cut it from my POV,
especially when marketing to the academic sector with a student discount to boot; the lack of Outlook was widely publicized in the poor marketing to the corporate space, but there is no visible mention of things like Java/Silverlight in IE RT. Also keep in mind that Silverlight 5 has an official Microsoft support lifecycle end of
2021. Yes, organizations do need to move onto other techs, but I feel the lack of Silverlight in the Surface RT products in particular was a poor and poorly marketed decision for the key academic sector.