-
Update
- Binary Update
- Database Updates
-
Finalize update
- products and technologies wizard
-
version database and binaries must not be the same in sp 2010
- gradually updates possible - more uptime
-
Types
- individual updates to resolve specific issues
- cumulative updates
-
Service Packs
- includes updates as well as new functionality
-
naming: MMMM.mmmm.BBBB.rrrr
- Major - Minor - Build - revision
- SP2010: major 14
-
Build to build update
- applying updates
-
Version to version update
- sp 2007 - 2010
-
multiple server farm
- more detailed planning to reduce downtime
- update in stages
- 1. Obtain the update, copy it to each server in the farm.
2. Schedule an outage window during off-peak hours and communicate
3. Update the binaries on each SharePoint server in the farm prior to the advertised outage window. 4. Review the farm’s servers to identify each server’s role(s) so that you can group together servers with the same roles for updating.
5. If the farm has load-balanced WFEs, remove half the cluster’s node and update them, and then reverse the configuration to ensure optimal uptime.
6. Ensure that the binary update’s installer has been run on every server in the farm prior to the outage window.
7. When the outage window begins, update the farm’s content databases using the Upgrade-SPContentDatabase cmdlet.
8. Finalize the upgrade by running the SharePoint Products and Technology Configuration Wizard. 9. Review the upgrade’s log file to verify that the upgrade completed without error.
10. Validate that the farm’s sites are fully functional.
11. Communicate to users that the outage window has ended.
-
Single server farm
- downtime is unavoidable
- test if possible, the only way to roll back is to rebuild farm and restore conten
-
build to build update
- download update
- schedule outage and communicate
- run the update's installer to deploy the binary to the file system
- stop web sites in IIS and update the content databases using Upgrade-SPContentDatabase
- run products and config wizard
- review log
- validate that sites are funcational
- communicate to users