Post a Comment
We got bit in the arse my this last month. The rollup changed a file that all the patches applied didn't change. The result of that change is that tha MTA's in Exchange 5.5 took a dive. it took 2 weeks of troubleshooting then a call to MS support who said that they had an internal memo that the rollup could cause a problem with Exchange.
My problem is, why is it that all the patches combined don't do this, yet the rollup does. Does the Rollup change more then the patches it's supposed to cover?
Someone should be fired for making this dumb idea of creating a subpar service pack and calling it a "rollup".
Microsoft should have *done right by the customer* and made a real service pack.
Microsoft should have *done right by the customer* and *tested* a real service pack.
Instead we get the roll-it-over of the roll-up.
This behavior and shoddy engineering is not a good sign that Microsoft is changing for the better.
A service pack, or an updaze rollup doesnt mean, that only the hotfixes offered by WU are packed into one executable. WU offers mostly the critical patches, but MS issues dozens of other small fixes. You have to hunt these, if you encounter a problem on your server (if that is not so widespread). Maybe that was the problem of this rollup: it contained a hotfix, that was apllyed earlyer only by a small number of users.



