August 12, 2013 at 8:33 pm
Comments posted to this topic are about the item Patch Problems
August 13, 2013 at 8:02 am
I'm just hoping that, after last month's .NET updates broke SharePoint, they don't reintroduce the problem this month. It took them three weeks to release a patch for a single OS last time; I hate to think what will happen if they haven't fully fixed it when they push the updated patch through.
August 13, 2013 at 8:26 am
This conundrum has always been one of my favorites. Apply the patches to keep your systems secure but potentially break something, or leave yourself vulnerable while testing patches (or waiting for MS to patch the patch) so nothing breaks.
____________
Just my $0.02 from over here in the cheap seats of the peanut gallery - please adjust for inflation and/or your local currency.
August 13, 2013 at 11:46 am
We had issues because of the 2840628 patch where it denied us adding a column to a table. Fortunately for us this was in a non-production environment. We also saw errors in replication related to this.
Russ
August 20, 2013 at 2:34 am
With MS moving to automated patching that you have no control over (or have i misunderstood the latest info. about MS's upcoming patch policy?), I'm wondering how long it will be before there's a law suit suing MS for the damage their automated patch caused.
August 21, 2013 at 10:04 am
I think that although the quality of software coming from Redmond has dramatically improved over the last few years, there will always be a requirement to enable local manual uninstallation of patches in case of failure. The whole patch lifecycle should be thought of as part of a software development project from the outset before even a single line of code gets written. Rarely is though.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply