MOSS SP1 Upgrade Process:
As defined and cleansed by http://technet.microsoft.com/en-us/library/cc263467.aspx#section1
Database Maintenance:
1. Run MOSS BPA and resolve any problems defined
2. Stop the www service and disconnect any users
3. Run DBCC CHECKDB on each database and repair any problems.
4. Remove Orphaned Items from databases using stsadm –o databaserepair
5. Defragment and update statistics of each database
6. Make sure that there is adequate hard drive space in your database files volumes, tempdb volumes, and Windows temporary folder on the servers running SQL Server, front-end Web servers, and application servers.
7. After you have backed up all of your databases, use the SQL Server DBCC shrinkfile command to free unused log space, making the logs as empty as possible. Shrinking the Transaction Log
Upgrade Pre-Steps:
1. Load Balance Site Collections and ensure your not exceeding site collections limits per content database and make sure content databases do not exceed 100 GB as recommended.
2. Make sure that you follow the recommendations concerning SQL Server page-fill factor and other storage planning best practices before you begin the upgrade.
3. Backup
a. Use the full backup operation from SharePoint Central Administration or Stsadm to back up search. The backup should include both the SSP and the index file.
b. Brick level backup the configuration and central admin content databases
c. Backup the SSO and every content database
d. Backup any Front End Customizations such as Templates, features, resources, webparts, etc..
4. OPTIONAL - In server farms that have a large number of sites, you will find that installing a software update with the content databases attached is not practical in terms of downtime. You may want to pursue this route for any content db > 20 GB as well. In order to minimize the downtime, we recommend that you perform the additional steps of running the Stsadm preparetomove operation and then detach the content databases. Do not run against the CONFIG database, SSP or ADMINISTRATION CONTENT DATABASE!
a. Run this command for each content database
stsadm -o preparetomove -contentdb <db_name>
If you do not run this operation before you detach the content database, then the membership and profile information in the content database is static and will not be synchronized after upgrade.
b. If you have multiple Web applications you must run.
stsadm -o deletecontentdb -url http://servername -databasename
c. In this operation, -url specifies the Web application from which the content databases will be detached and -databasename specifies the name of content database to be detached.
After you upgrade your server farm, you must attach the content databases back to the server farm. You can only attach one content database to the server farm at a time, because when you attach the databases to the upgraded server farm the content database is upgraded automatically.
5. To deploy the upgrade you must have these memberships
a. Member of the Administrators group on the Web server computer.
b. Member of the Administrators group on the server running SQL Server or be granted the fixed database role db_owner to all SharePoint Products and Technologies databases.
Install Sequence
1. Add the account for the SharePoint Central Administration v3 application pool identity to the Administrators group on each of the local Web servers and application servers and then log on by using that account. These changes are only required for installing the update and then running the SharePoint Products and Technologies Configuration Wizard to complete the upgrade.
2. The following permissions are required to run psconfig
1. Member of the Administrators group on the local computer that runs Office SharePoint Server 2007.
2. In SQL Server, the account must be:
1. Authorized to access all SharePoint Products and Technologies databases.
2. Granted the Database Creators (dbcreator) fixed server role.
3. Granted the Security Administrators (securityadmin) fixed server role.
Install the software update
This section includes all of the procedures required to install a software update successfully in any size server farm. If you are in a large server farm you should read the Large farm optimization section later in this document.
The following procedure provides the steps to:
· Make all software update files available on all servers in your server farm.
· Complete the update from one of the servers hosting the Central Administration site.
· Finish updating the remaining servers in the server farm.
Note
You must perform steps 1 though 8 from the following procedure on every Office SharePoint Server 2007 server in the server farm before you complete the installation on any one Office SharePoint Server 2007 server.
To install a software update
|
1. Disconnect users from the server farm by stopping the World Wide Web Publishing service (w3svc) on all Web servers.
2. Download and install the appropriate Windows SharePoint Services 3.0 software update for all servers in your server farm.
Important
At the end of the Windows SharePoint Services 3.0 software update, do not run the SharePoint Products and Technologies Configuration Wizard.
3. Download and install the appropriate Office SharePoint Server 2007 software update for all servers in your server farm.
4. At the end of the software update installation, the SharePoint Products and Technologies Configuration Wizard starts.
Note
If the wizard does not start automatically, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.
5. On the SharePoint Products and Technologies Configuration Wizard Welcome page, click Next.
6. In the dialog box that notifies you that some services might need to be restarted during configuration, click Yes.
7. On the Completing the SharePoint Products and Technologies Configuration Wizard page, click Next.
8. When the dialog box about installation in a server farm appears, do not click OK. Instead, leave each server with the following dialog box displayed:
You must run Setup to install new binary files for every server in your server farm. If you have multiple servers in your server farm, run Setup and the configuration wizard on the other servers now, and then return to this server and click OK to continue.
9. When the dialog box from the previous step is displayed on all the application servers and Web servers in the server farm, use one Web server that hosts the Central Administration Web site to finalize the installation.
Notes
We recommend that you install the software update on an application server that is hosting the Central Administration Web site, then the other application servers, and finally the front-end Web servers.
If you are hosting your Central Administration Web site on a front-end Web server, then we recommend that you install the software update on the front-end Web server hosting the Central Administration Web site, then the application servers, and finally the remaining front-end Web servers.
10. On the server you selected in the previous step, click OK.
11. On the Configuration Successful page, click Finish.
12. After you have finished updating one Web server that hosts the Central Administration Web site, you should follow the procedures in the "Verify installation" section on this one Web server to ensure that the software update installation was successful.
13. Continue updating the remaining computers in the server farm, one at a time, by clicking OK in the dialog box.
Note
It is important that the SharePoint Products and Technologies Configuration Wizard perform the configuration procedures on only one computer at a time.
14. When the software update installation and configuration is complete on all the Web servers in the server farm, make the Web servers available to users by manually starting the World Wide Web Publishing service on each server on which you manually stopped the service. |
3. OPTIONAL only If you detached content dbs use the following command line to add them back to the farm
stsadm -o addcontentdb -url <http://backupservername:port> -databasename <ContentDBName>
If you detach and reattach a content database, be aware that the next time the content within that content database is crawled a full crawl will occur even if an incremental crawl is requested. Because a full crawl re-crawls all content that the crawler encounters, regardless of whether that content has been previously crawled, full crawls can take significantly more time to complete than incremental crawls. CPU will be maxed!
4. Verify the server install by running the following command against the config database
SELECT * FROM Versions
1. Release 12.0.4518.1016
2. October public update 12.0.0.6036
3. Service Pack 1 12.0.0.6219
4. Post Service Pack 1 rollup 12.0.6300.5000
· OPTIONAL Force an upgrade by running one of the following commands if you encounter problems
1. psconfig –cmd upgrade –inplace b2b –wait –force
2. psconfig -cmd configdb -connect -server <SQLServerName> -database SharePoint_Config_<dbname> -user <domainusername> -password <password> -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd applicationcontent –install
· Next Install Rollups 1 & 2 for both WSS and MOSS and reboot the server
IMPORTANT NOTICE FOR FUTURE INSTALLS:
From this point forward when you add a new server to the farm you should make sure you do the following:
1. Install MOSS with the SP1 Slipstream Version
2. Install The Latest Rollup which are presently WSSv3 Blackout rollup & MOSS Blackout rollup
3. Run PSConfig to attach to the farm.