A Public Funded "Microsoft Shop?"
An anonymous reader writes "I work at a public hospital in the computer / technical department and (amongst others) was recently outraged by an email that was sent around our department: '(XXXX) District Health Board — Information Services is strategically a Microsoft shop and when talking to staff / customers we are to support this strategy. I no longer want to see comments promoting other Operating Systems.' We have also been told to remove Firefox found on anyone's computer unless they have specific authorisation from management to have it installed under special circumstances. Now, I could somewhat understand this if I was working in a company that sold and promoted the use of Microsoft software for financial gain, but I work in the publicly / government funded health system. Several of the IT big-wigs at the DHB are seemingly blindly pro-Microsoft and seem all too quick to shrug off other, perhaps more efficient alternatives. As a taxpayer, I want nothing more than to see our health systems improve and run more efficiently. I am not foolish enough to say all our problems would be solved overnight by changing away from Microsoft's infrastructure, but I am convinced that if we took less than half the money we spend on licensing Microsoft's software alone and invested that in training users for an open source system, we would be far better off in the long run. I would very much like to hear Slashdot's ideas / opinions on this 'Strategic Direction' and the silencing of our technical opinions."
Precisely what I'm moving towards. We'll probably have Exchange for some time to come, and that means Active Directory and DCs, but our file servers are all Samba running as member servers. Maybe someday Samba 4 will allow me to migrate the DCs away from Server 2003, but it will have to be able to prop up an Exchange 2003 server. The point in my shop is not to get rid of Microsoft because I'm an MS hater (though I sure ain't their biggest fan), it's simple economics. Their licenses are too friggin' expensive. I saved the organization several thousand dollars by going to Linux file server.
The world's burning. Moped Jesus spotted on I50. Details at 11.
There's a reason for professional support services in the Linux sector. That can buy you back-porting, bug fixes, a whole host of other services that allow an organization to standardize on a single linux distribution for years. No sane company using Linux to their benefit is using "the flavor of the month". They weigh their needs, their budget, the pros and cons of each distribution that meets their criteria, pick a version and test rigorously. Then you don't fuck with it or upgrade for a few years.
Linux can only be successful in an organization that is open to change and this is very much culture dependent. Your example of tools that are put together hodge-podge that nobody knows about happens plenty in Windows also. The most egregious example of this is managers who think they can write VB applications in Microsoft Office. They can bastardize code and make something work on their computer, but the code is often so poorly written that it won't work across MS Office versions and crashes on the next upgrade.
Bad practices aren't limited to any one operating system.
You can't legislate goodness. Let each to his own destiny, by will of his freely made choices.