MS preps service pack blocker tool for Windows 7, Server 2008 R2
SP1 action coming to a screen near you soon
Microsoft has prepped its Windows Service Pack blocker tool kit to include its upcoming service packs for Windows 7 and Windows Server 2008 R2.
The SP1s for both operating systems hit Release Candidate status late last month, but they’re not expected to reach manufacturers until early next year.
Ahead of that, MS has updated its Windows Service Pack blocker tool kit that will eventually allow sys admins to control how updates are applied in their organisation.
The software giant will initially push both service packs out to its Windows Updates website, before slowly trickling the code via its Automatic Updates portal.
But not every business will immediately want the service packs to do a stealth install on all their computers. Mindful sys admins will want to test the package of updates and bug fixes on a small sample first, which is where the blocker tool comes into play.
The tool itself will be valid for 12 months after the service packs are made available to all-comers.
Beyond that, Microsoft will hit the AU ‘on’ switch for all remaining hold-outs of the respective service packs.
Microsoft is probably close to bringing out the final version of SP1 for Windows 7 and Windows Server 2008 R2, given the arrival of the tool. ®
Steve nuked my Macs
and he didn't give me a choice, just smoothly invited me to go through software download and 'take it......'
I 'suspect' Macs, but now have to support them on a 75:1 ratio to win machines :(
In this week of harmony I have seen my workstations taken to a new level of 'diferentness' and my few, only kept for novelty, servers to 'doomed, and we don't give a f*** how much they cost' !
I am kinda non-plussed........ I hated them when told I had to support them, and now hate the supplier for dumping the poor little, trendy, shiny, use**ss b**stards when they are beyond the Profit, ooooops pale!
when MZ gets his way, this will be automatically be added to my cv when I email it and I will never work with Macs agai........................UGGGGGGGGHHHHHHHHHHHHHH!!!!!!!!
Only a total idiot
Only a total idiot would roll out a major service pack to an enterprise without thorough testing and waiting for the smoke to settle.
Businesses need to be able to block automatic updates, so the tool is very welcome.
and just to throw the cat among the pigeons....
thinking of a fruity flavour of kit.... who do not give you options on an os update... and once you did theres no going back...
The two previous respondents are missing the point.
Let me splain.
In sane places, you download the fixes for the fuxes. You store them in a central place so as not to over-stress your Internet pipe. You then give your TEST servers a little poke, and they partake of the alledgedly fixed software. You very carefully test whether this makes them fall over in interesting ways. If they don't, then you give your PRODUCTION servers the same little poke and hope that you didn't miss anything.
In insane places, every server wants to be connected to the Internet to function at all, and to acertain that you're not a filthy pirate. As an aside, these boxes will then automatically download the MS fixes as soon as they become available, and politely ask you whether you want to reboot or yes. Only NOW, for people who have a screw loose and actually allow this to happen to any server they care about, there is an ADDITIONAL tool that PREVENTS this thing from happening, should you lack the wit to keep it from happening in the first place. Which will be automatically installed at the next automatic update. Are you with me so far? Well, then. When six months have passed, the fixpack blocker will then cease to block the fixes that you shouldn't have let the machines install in the first place, presumably causing them to be installed automatically after all, unless you have had the notion to disable that behaviour in a more permanent way in that time.
And yes, I agree. That is madness.
But then again, I also think that putting a firewall on your machine to block people from haxoring into your system's less secure facilities, should be a practice abandoned in favour of fixing the sodding leaks in the faulty facility in the first place, or not running that facility in the first place.
So yes, while people are crowing that here MS has given us yet another feature to control the deployment of their shit on our servers, I would argue that there should be only one way. One that works properly.
I think it is perfectly acceptable for a grace period to apply before an SP becomes mandatory. Microsoft has a support policy and rolling service pack levels are part of that policy. 1 year should also be enough time to test how a service pack upgrade will affect services.
I don't think this approach is new either