JohnVranesevich once bubbled...
I was doing Information Warfare research for the Pentagon at the time (as a civilian contractor). They have standards, and I'm not the one that sets them, haha...
:hiding:
"Standards", yes... It's good to have standards...
In my home office:
FreeBSD ... gateway, mail, news, file server, etc.
Solaris ... software development (on sun hardware)
Windows ... software development, test
Windows ... end user software, web client, etc
I make my living writing software in both the unix and windows worlds. While much of the OS bashing is just a horrible flame war, there are some good points on either side.
Personally I'd like to see both OS's learn from one another (as they've been doing for years now). It's amazing (from a historical perspective) that you can actually hand a *user* a unix cd and expect them to install it without help (vs. early Berkeley releases on a vax). It's also incredible that Windows can be used as a server (for more than just file sharing).
Ten years ago I would have had a hard time believing either of these statements.
Back to the subject at hand -
The concept of centrally managed software is nothing new - in the enterprise market it's seen as a huge boon. If you're a poor IT guy with several hundred PC's to keep up to date it becomes pretty clear. MS is taking the concept a bit further. I haven't experimented with this, but it seems like a simple answer is to ask the user if they'd like to install the update (as many current packages do now).
I take it from the original post that that's not the plan?