I’ve read a whole lot of articles about why MS was going to beat VMware and the other way around. I guess the only thing we can do is wait and see what happens. Of all the articles I’ve read there’s one that hit the nail right on the head.
This patch will ensure that Friendster and Obama are added to your dictonary on Vista and 2008 Server. No big deal right? This brings up a few questions for me:
- Why does my server have a GUI?
- Why does this patch require a reboot?
- Who is typing the words Friendster or Obama on their 2008 Server?
At the root of the issue is that I will never deploy Hyper-V for enviroments I admin. I understand patching for core issues and security but this is stupid. If this server was in fact running my virtual server farm I would now be rebooting for Friendster and Obama. Yikes!
Lukas Beeler says
1.)
Terminal Server. But i doubt anyone would use Windows Mail on a Terminal Server. Stil, this is exactly the reason why Microsoft recommends running Hyper-V on Server Core only.
2.)
Windows was designed as desktop system – anything later evolved. This is the backlash from that that we’re still seeing.
3.)
Again, see 1.)
nisahnet says
I’m not an MS fan (nor hater), but KB955020 specifically says “…without Hyper-V” under the applies to. Couple that with Lukas’ note that MS recommends running Hyper-V on Server Core only, and I don’t see why one would feel compelled to patch and reboot a Hyper-V environment based due on the details off this KB.
Now that being said, my concern is the same as yours… How many MS Server Core patches (needing reboots) can we expect? For me, track records with MS points to – too many.
————–
Nisah Cheatham
Duncan Epping says
And how many alike patches can we expect? this is just an example which is disturbing in my opinion. Why would you even have a word processor in the OS, force the customer to use your Office software. Strip the OS!
mlambert says
Anti-msft fud doesn’t solve problems or even make you appear intelligent. Be an equal opportunity technologist and live a happier life.
Lukas Beeler says
nisahnet,
I’ve been using Hyper-V in a (internal) production environment since WS08 was released. So far we had four patchdays, and on one of them a reboot of the Server Core machine was not necessary.
One important thing to notice here is that patches to server core technologies are applied wheter they are in use or not. e.G. if a domain controller component has a security fix, it will also want to install on your Hyper-V host.
You could control this through WSUS, and only allow patches through which really affect the Hyper-V machines, but i doubt this would be much better (and it could cause other issues).