Best Practices for applying Cumulative Updates by pptfiles


									Best Practices for applying
  Cumulative Updates

    Joe Vasil – Microsoft Premier Field
         Engineer for Sharepoint
                 What’s a CU?
• Cumulative Updates
  o Cumulative updates include all updates that broadly affect support issues
    that have been released since the last service pack
  o Since December 2008, cumulative updates have become truly
    cumulative, and are released on schedule every two months (on even
  o Contains hotfixes privately released during last two months
  o Each Cumulative update supersedes the previous CU
  o Unlike Service Packs, each CU is Uber (all inclusive)– meaning you do not
    need to install a localized CU for each language pack you have installed
  o If Sharepoint core language is English then you only download/install
    English version of CU
                Pre-Deployment Checks

• Checking for and cleaning up Orphans
  o   stsadm –o enumallwebs
  o   Stsadm –o databaserepair
  o   Stsadm –o deletesite
  o   Stsadm –o deleteweb

• Prepare databases
  o Defrag indexes
                       STSADM –o enumallwebs
•    Stsadm –o enumallwebs –databasename <Dbname>

 <Database SiteCount="14" Name="WSS_Content_jsvcontoso" DataSource="wfe1wsql">
  <Site Id="51911d6f-2073-4fe0-8136-0274c25044a7" OwnerLogin="CONTOSO\administrator" InSiteMap="True">
   <Webs Count="4">
    <Web Id="b4b207e4-6b4a-4975-905a-7efb72e76b02" Url="/sites/test1" LanguageId="1033" TemplateName="STS#0" TemplateId="1" />
    <Web Id="e4a5b679-9924-4b3b-ae4b-98f775e75541" Url="/sites/test1/meetingWorkspace" LanguageId="1033" TemplateName="MPS#0"
TemplateId="2" />
    <Web Id="385ed374-c99e-470c-8062-85c0211e35f4" Url="/sites/test1/meetingWorkspace/reoccuring event 1" LanguageId="1033"
TemplateName="MPS#0" TemplateId="2" />
    <Web Id="0b4fbabf-8814-4f8b-b26f-1d651fc5b902" Url="/sites/test1/subweb1" LanguageId="1033" TemplateName="STS#0" TemplateId="1" />
  <Site Id="24b55e95-076e-46f3-b166-178ed5f94e4d" OwnerLogin="CONTOSO\administrator" InSiteMap="False"
   <Webs Count="1">
    <Web Id="02e85ceb-0860-466f-aade-71d0b244d687" Url="/" LanguageId="1033" TemplateName="STS#0" TemplateId="1" />
  <Site Id="ba96fe57-5c59-4d0e-b7cd-38c4588072b1" OwnerLogin="CONTOSO\administrator" InSiteMap="True">
   <Webs Count="3">
    <Web Id="5c87c660-a623-4f4a-8c67-b5a41e9f00f3" Url="/sites/PublishingSite" LanguageId="1033" TemplateName="BLANKINTERNET#0"
TemplateId="53" />
    <Web Id="c91025ec-1958-4446-9eb0-0a8822bb8241" Url="/sites/PublishingSite/PressReleases" LanguageId="1033"
TemplateName="BLANKINTERNET#1" TemplateId="53" />
    <Web Id="002cb918-d7b3-4af2-9d8f-ded8b103bccc" Url="/sites/PublishingSite/Search" LanguageId="1033"
TemplateName="SRCHCENTERLITE#1" TemplateId="90" />
                 STSADM –o deletesite
•   stsadm -o deletesite
  -url <URL name>
  [-deleteadaccounts {True | False}]
For deleting a orphaned site collection:
  -siteid <site ID>
  -databasename <database name>
  -databaseserver <database server name>

stsadm -o deletesite -force -siteid 24b55e95-076e-46f3-b166-178ed5f94e4d
-databaseserver DS1 -databasename DB1
             Stsadm –o deleteweb

stsadm -o deleteweb
  -url <URL name>
For deleting a site within an orphaned site collection
or an orphaned site within a site collection:
  -webid <Web ID>
  -databasename <database name>
  -databaseserver <database server name>
        Stsadm –o databaserepair
stsadm -o databaserepair
  -url <url name>
  -databasename <database name>
              Defragment Databases

• Defragmentation stored procedure
  o To reduce the level of index fragmentation
  o Run SQL Server stored procedure provided be the Microsoft Sharepoint
    Product Group
  o For more information about this procedure, see How to defragment
    Windows SharePoint Services 3.0 databases and SharePoint Server 2007
    databases (
    in the Microsoft Knowledge Base.

  o For information on Sharepoint database maintenance see
            Clean up the environment

• Address large numbers of site collections in a
  content database
   o If 5,000 or more site collections in a database, consider breaking them out
     into multiple databases
   o In Office SharePoint Server 2007 - default warning at 9,000 site collections
     and a hard limit at 15,000 site collections
   o In SharePoint Server 2010 - 2,000 site collections for the warning and 5,000
     site collections for the limit.
             Backup and Backout stratagy
•   As
     o   “Although the configuration database and the Central Administration content database can be backed
         up, restoring backups of the configuration database and the Central Administration content database
         taken from a running farm by using the tools built in to SharePoint Products and Technologies or SQL Server is
         not supported.”
•   Make sure the following steps are performed on each server “before”
    the Prep task of backing up the Sharepoint Dbs is performed

•   Stop the farm by performing the following steps:
     o   On the server that is running the Central Administration Web site, in the Services snap-in, stop the following
            • Microsoft Single Sign-On service
            • Office Document Conversions Launcher service
            • Office Document Conversions Load Balancer service
            • Office SharePoint Server Search service
            • Windows SharePoint Services Administration service
            • Windows SharePoint Services Search service
            • Windows SharePoint Services Timer service
            • Windows SharePoint Services Tracing service
            • Windows SharePoint Services VSS Writer service
     o   On the server that is running the Central Administration Web site, at the command prompt, type iisreset
     o   Repeat steps on each server in the farm.
         Update strategy
• Determine strategy to use to update farm
  o In-place
  o Database attach
  o The update sequence for the farm servers
  o The order of operations
  o The downtime limits and how you plan to reduce
  o A rollback process if there is a major problem
      Downtime reduction
• Downtime reduction
  o  Read-only content databases (SP2010 or MOSS 2007)
    •    Requires Separate Read-only Farm)
  o  Doing parallel upgrades to reduce downtime (SP2010)
      • After binaries Use the Windows PowerShell Upgrade-
        SPContentDatabase cmdlet to upgrade each content database
      • Can run against multiple contentDbs at same time
  o Upgrade ContentDbs in separate/temp farm (MOSS 2007 )

• Deploy software updates for Office SharePoint
  Server 2007

• Install a software update (SharePoint Foundation
Verify update completion and success
• View the upgrade log file (Also use this logfile to troubleshoot
  a failed installation)
   o   %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS
• To check version numbers on certain files and registry keys
   o   examine the version number of specific files in
       %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\ISAPI
   o   Check Microsoft.SharePoint.portal.dll (MOSS) (SP2010 Server)
   o   Check Microsoft.Sharepoint.dll (WSS) SP2010 Foundation)
   o   C:\Program Files\Common Files\Microsoft Shared\Web
   o   C:\Windows\assembly\GAC_MSIL\Microsoft.Office.Server\

   o   Compare to version numbers provided in CU KB Article
• In Registry, verify value is correct in the DisplayVersion key in
  the following locations: (MOSS 2007)
   o   For x86: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
   o   For x64: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\
      SQL Database Schema version
• To verify through direct examination of the SQL
• This SQL Server query can be run on any SharePoint
  Products and Technologies database to track all
  the upgrades run on the database in the GUID
• SELECT * FROM Versions
• The highest value that maps to the preceding GUID
  should equal the current version of the product. For
  August 2010 CU the version should include 6545.
              Resource Center

• Updates Resource Center for SharePoint Products
  and Technologies (MOSS and WSS)

• Update Center for Microsoft Office, Office Servers,
  and Related Products (including Office WebApps)
      October 2010 CU issue
•   Packages Impacted
•   The packages effected are the Server-Packages for SharePoint
    Foundation, SharePoint Server and Project Server 2010(o14). This
    does not impact the Office 2007 version of these products.
•   Here is the rundown of the Office 2010 specific packages
    released with the October CU that are effected
•   MOSS Server Package 2394320 contains SharePoint Foundation ,
    MOSS packages - impacted
•   Project Server Package 2394322 contains SharePoint Foundation,
    MOSS, and Project Server packages – impacted
•   SharePoint Foundation Server Uber Package 2394323 contains
    SharePoint Foundation and MUI's - not affected installed by itself
•   SharePoint Foundation Server 2405789 SPF only not impacted
•   SharePoint Foundation Server 2427410 SPF+WSSMUI not impacted
•   SharePoint Foundation Server 2436034 SPF+WSSMUI not impacted
            Types of “Hotfixes”
Critical on-demand
     o   A critical on-demand (COD) hotfix is available to address critical problems that cannot be
         handled via the cumulative update delivery cycle
     o   COD hotfixes are limited to emergency situations, for example, an issue that blocks normal
         business operations for the customer or an issue for which there is no effective workaround
     o   COD hotfixes are included in the next cumulative update that is released.

Public update/Microsoft update
     o    Based on the criticality of an update, a COD hotfix is made available for public download or a
         Microsoft security update is released as a public update for SharePoint
     o   The US DST Hotfix - KB941422 is an example of a security update that was released as a public

Post-service pack rollup
     o   includes any “SPLock hotfixes,” which are hotfixes that were developed during the SPLock period
     o    SPLock period is a lockdown on service pack development that is meant to help achieve stability
         in the development process.
     o    hotfixes that have been produced before the SPLock period is declared are integrated into the
         next service pack
     o    SPLock hotfixes are never distributed publically and are only made available during Microsoft
         Customer Service and Support engagements
     o   SPLock hotfixes require special handling because if the next service pack is applied without the
         post-service pack rollup, the fix is lost
     o    This could cause data loss, so Microsoft is very careful about releasing these SPLock hotfixes, and
         provides detailed guidance for each customer scenario

To top