Access your Pro+ Content below.
Time to beef up code retention policies on your SharePoint servers
This article is part of the SharePoint Insider issue of May 2010
Today, many medium to large organizations seem to have a team of people whose job it is to review and approve software patches. As a SharePoint administrator, placing the burden of patch management onto another team may initially seem like a great idea. However, doing that can mean losing some control over the SharePoint servers. The big problem when you allow a dedicated team to handle patch management for SharePoint servers is that you have no way of knowing how thoroughly the patches are being tested. The patch management team should test each patch meticulously, but I have seen IT professionals who skip the testing process altogether, assuming that if a patch was released by Microsoft then it must be OK. Microsoft openly admits that patches do not receive the same degree of testing as service packs do. Normally, Microsoft seems to do a decent job of releasing patches that work as advertised, but there have been a couple of buggy patches that have made it out the door. And buggy patches can severely cripple your servers. Why ...
Access this PRO+ Content for Free!
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Features in this issue
Organizations should use code retention policies in their governance plans to correct patch management policies for SharePoint servers.
Isolated from other sites, sandbox solutions offer the ability to deploy solutions within the governance of Web applications.
By email-enabling document libraries in SharePoint, you can share information with co-workers for a set period of time.