Applying Updates in SharePoint 2010 Server Farm Environments

2. Applying Updates in SharePoint 2010 Server Farm Environments Name Title Company

3. Objectives • Understand the new capabilities in the SharePoint patching process • Learn the options an administrator has when patching SharePoint 2010

4. Patching Process VersusUpgrade Process • Installing patches has two distinct parts • Patching • Laying down bits • Stopping services to replace in use files • Deployment • Copying bits to other locations on the server • Upgrade • Moves moving parts up to new version • Services • Databases

5. Upgrade Method – In-Place • Databases to be upgraded are already attached to the farm • Patch is installed via EXE • Patch and upgrade is separated into two steps • Configuration Wizard manages locks to manage multiple instances

6. Upgrade Method – DB Attach • Databases may incur upgrade when mounted/attached • Databases outside of compatibility mode will automatically upgrade • 2007 to 2010+QFE1 • Possibly 2010+QFE1 to 2010+SP1 (target) • Possibly 2010+QFE1 to 2010+QFE4 (non-target) • Databases within compatibility mode require Upgrade-SPContentDatabase or Configuration Wizard • Mount-SPContentDatabase • Maximize upgrade speed by attaching multiple databases at one time

7. Backwards Compatibility • Patches are built to be compatible with databases at previous patch level • This gives some flexibility on whenpatches are installed, and when databases are upgraded • Don’t leave in this state too long, it can cause some inconsistent behavior

8. Allowing Bits Upgrade Separate from Database Upgrade • Patches can be installed on servers minimal downtime • Bits can be installed gradually • Roll a WFE out of rotation • Apply patches • Remove existing unpatched WFEs from rotation • Roll WFE back in rotation • Repeat • Patch application servers • Database upgrades can be done at a convenient time

9. SQL Modification Improvements • Fewer schema alteration actions • Database Upgrade State cached • SQL stored procs are only altered if changes are small • In SharePoint 2007 they are completely rewritten regardless of how much changed

10. Automatic Deployment Mechanism • Supports major update methods • WSUS • Windows Update (no SharePoint updates) • Microsoft Update (only if Single click install) • Updates binaries only, not content • Health monitoring rule alerts Admins

11. Providing Administratorswith Patch Reports • Central Admin allows you to monitor the upgrade status • Upgrade status page • Database schema information page • Can also be monitored in PowerShell with Get-SPContentDatabase or Get-SPDatabase • Validate NeedsUpgrade Property • Use STSADM -o localupgradestatus

12. Farm Servers UI Showing Farm Status (Including Upgrade) • One location to see the patch status forall the members of your farm • Can show entire farm orindividual members • Can tell if a server has a patch that needsto be installed • Also shows status of databases as well as their type

13. Upgrade and Patch Management

14. Manage Patch Status

15. Farm Status UI

16. Patch Status UI

17. Database Upgrade, Upgrade Status, and Patch Installation Status Management Detailed UIs

18. Manage Database Status

19. Database Status UI

20. Configuration Wizard Patch Detection • Can be run on multiple boxes concurrently • Will put a lock on any content it is upgrading • Each instance looks for a lock or the upgrade status

21. Configuration Wizard

22. Patch Health Rules • New feature in SharePoint 2010 • Include several that pertain to patching • Databases require upgrade • Databases are running in compatibility range, upgrade recommended • Product/patch installation or serverupgrade required • Can be used to keep administrators aware of potential problems and address them

23. Patch Health Rules demo

24. Using Windows PowerShell for Patching • Central Administration is not the only option for upgrading databases • Windows PowerShell can be used to determine database patch level • Use Get-SPContentDatabase • Can also be used to upgrade database • Use Upgrade-SPContentDatabase • Add-SPContentDatabase may also upgrade it • Can be used to upgrade databases with multiple SharePoint servers

25. Patch Availability • Cumulative Update (CU) and Critical on Demand (COD) patches will be available • CU will continue to ship on even months • COD will ship on demand • COD patches will continue to contain just the MSPs needed for that specific COD

26. Applying a Patch demo

27. Summary • Understand the new capabilities in the SharePoint patching process • Learn the options an administrator has when patching SharePoint 2010

29. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.