Hello,
I am the SharePoint Admin in our organization, and we have a separate group of Windows Server admins that are in charge of rolling out windows server updates across our organization's systems; this includes the SharePoint farm servers.
I started to notice particularly beginning this year that every time our windows admins push updates into our SharePoint farms something breaks and we have to spend several hours of extra effort to repair patching related issues. Another thing to note, is that sometimes these windows updates actually "upgrade" the SharePoint's farm version number. This have been an issue for some time now, but I have noticed patching related issues like this to become more aggressive this year.
Last time this happened (a few weeks ago) our windows admins inadvertently pushed updateKB2879953, and for some reason the update installation didn't went through successfully on one of our servers, and as expected the SharePoint Configuration Wizard wouldn't complete successfully. The only solution was to rollback (uninstall) this particular update (KB). Also, update MS14-022 which is cataloged as critical was installed. This one in particular upgraded the SharePoint version number skipping a few CU version numbers which I haven't installed yet. Isn't this a big issue? Once I actually decide to upgrade SharePoint (Apply a CU or SP) wouldn't this installation fail since it will try to install an update with a lower version level number? Even if it doesn't crash and the "missing" update(s) goes through, how am I supposed to keep track on which version has actually been deployed into my servers? I highly rely on the version information that is presented to me at the Central Admin, but it turns out this information can be deceiving.
Is anyone or has anyone been in this situation?
Any advice on how are you handling/deploying Windows server updates in your SharePoint farms would be appreciated.
About our SharePoint farm:
SharePoint Server 2010
version number (used to be): 14.0.7108.5000 / After last patching: 14.0.7123.5000
Our Development environment has 1 WFE, 1 App server, 1 SQL Server
Our Production Environment has 2 WFE (NLB), 1 App server, 1 SQL server
Thanks.
I am the SharePoint Admin in our organization, and we have a separate group of Windows Server admins that are in charge of rolling out windows server updates across our organization's systems; this includes the SharePoint farm servers.
I started to notice particularly beginning this year that every time our windows admins push updates into our SharePoint farms something breaks and we have to spend several hours of extra effort to repair patching related issues. Another thing to note, is that sometimes these windows updates actually "upgrade" the SharePoint's farm version number. This have been an issue for some time now, but I have noticed patching related issues like this to become more aggressive this year.
Last time this happened (a few weeks ago) our windows admins inadvertently pushed updateKB2879953, and for some reason the update installation didn't went through successfully on one of our servers, and as expected the SharePoint Configuration Wizard wouldn't complete successfully. The only solution was to rollback (uninstall) this particular update (KB). Also, update MS14-022 which is cataloged as critical was installed. This one in particular upgraded the SharePoint version number skipping a few CU version numbers which I haven't installed yet. Isn't this a big issue? Once I actually decide to upgrade SharePoint (Apply a CU or SP) wouldn't this installation fail since it will try to install an update with a lower version level number? Even if it doesn't crash and the "missing" update(s) goes through, how am I supposed to keep track on which version has actually been deployed into my servers? I highly rely on the version information that is presented to me at the Central Admin, but it turns out this information can be deceiving.
Is anyone or has anyone been in this situation?
Any advice on how are you handling/deploying Windows server updates in your SharePoint farms would be appreciated.
About our SharePoint farm:
SharePoint Server 2010
version number (used to be): 14.0.7108.5000 / After last patching: 14.0.7123.5000
Our Development environment has 1 WFE, 1 App server, 1 SQL Server
Our Production Environment has 2 WFE (NLB), 1 App server, 1 SQL server
Thanks.









