TO AC 16:13
Naa, not old skool, that would make me old skool too :-)
In open converstation, yea we used to use netware too, but from what I remember, it wasn't doing anywhere near as many things as we push our modern windows servers to do? Much better for file and print services, lousy terminal server! :-)
IE on servers, I would say that is on there, so you can download patches and updates for 3rd party software. I use it quite a bit on servers, especially if you have some things that detect the OS through the browser. I would say Microsoft did think of that, hence IE ESC. Microsoft don't know what roles you are going to use on a server, no IE on a Terminal server wouldn't be too good. Patching IE, well you can use WSUS or SCCM to manage those updates. Chances are that IE updates will come out the same time as other updates, so we install the lot in mainatance windows.
Can't say I've ever seen video driver issues from Server 2000 until today. (NT4, another story!) But that might be because we use Dell, with the OpenMangle installer, and it puts the right drivers on from the start. Then use Dell Server update utility, so no rogue drivers can go on.
I'm not saying if you cut me I bleed Microsoft, we've had some issues with some not so written sofware, DFS, and SCCM to name a couple. But I personally think that the current enterprise kit is great. We use 16 blades, with Terminal servers serving up to 100 users on each. Attached to iSCSI SANs. They give us hardly any issues these days, they just run like the old days! With remote app, app-v, hyper-v, I think things are getting better and better!
And I think that back to the original point of this article, my above paragraph shows that MS aren't trying to be Apple. Enterprise is thier core.