Introduction
Follow the instructions in this article carefully when you upgrade from Office SharePoint Server 2007 Beta 2 Technical Refresh to the release version. The instructions are taken from "Joel Oleson’s SharePoint Land" blog (http://blogs.msdn.com/joelo). I have added notes and made slight revisions where applicable.
During upgrade, your farm will be offline for a period of time while the databases are upgraded to the release version of the product. Be sure to notify your customers in advance.
Prepare for upgrade
Perform the procedures in this section on every server computer in your farm.
Delete failed timer jobs
1. Open SharePoint Central Administration.
2. On the top navigation bar, click Operations.
3. In the Global Configuration section, click Timer job definitions.
4. On the Timer Job Definitions page, look for backup and restore or upgrade timer jobs in the list. If any exist, delete them by clicking the timer job and then clicking Delete on the page that appears.
Record current server information
1. Record the name of every server computer that hosts SharePoint 3.0 Central Administration.
2. Record the following information for each server computer:
– Server type: When you install the release version, you will need to specify the same server type that you have currently installed for each server computer in your farm.
Note The server type of a computer is located in the HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions12.0WSSServerRole registry subkey. The values are singleserver for Basic installations, and either WFE (commonly referred to as "Web front end") or Complete (commonly referred to as "application server") for Advanced (farm) installations.
I had problems with this step. I found my server installation to be called "Application", not any of the above. This corresponded to Complete as referenced here.
– Enterprise versus Standard SKU: When you installed Beta 2 Technical Refresh, you entered a PID key that enabled either Standard or Enterprise features of the product. When you install the release version, you must enter a PID key that corresponds to the same Standard/Enterprise choice that you made for Beta 2 Technical Refresh. To find out which license you have installed, open SharePoint Central Administration, click Operations on the top navigation bar, and then click Enable Enterprise Features in the Upgrade and Migration section.
If you installed Beta 2 Technical Refresh with a Standard PID key, you can install the release version with either a Standard or an Enterprise PID key.
If you installed Beta 2 Technical Refresh with an Enterprise PID key, you must install the release version with an Enterprise PID key.
Note In Beta 2, Enterprise features were referred to as "Premium" features; if you see "Enable PremiumFeatures" on the above page, you must first upgrade to Beta 2 Technical Refresh.
– Central Administration application pool account and password: You will need to use the same account and password when you install the release version.
Modify the registry setting for the configuration database connection
1. On the Start menu, click Run. In the Open box, type "regedit" without the quotes and click OK.
2. In the Registry Editor, navigate to the following subkey:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftShared ToolsWeb Server Extensions12.0SecureConfigDB
3. On the File menu, click Export, and in the File name box, type
SharePointRegKeyBackup
This backs up the subkey so you can restore it to your registry later, if necessary.
4. Under the registry subkey, right-click the dsn value, and then click Rename.
5. Type "dsn2" without the quotes for the name and press ENTER to save your changes.
Caution Be sure to check that you have renamed the registry key to dsn2. If you fail to perform this step, upgrade will fail and you will
have to manually upgrade the content databases to a new installation. This step is required for the installation process to detect and
upgrade Beta 2 Technical Refresh to the release version.
6. Close the Registry Editor.
To simplify renaming this registry key, you can download a utility from Microsoft Help and Support (http://go.microsoft.com/fwlink/?LinkID=75313&clcid=0x409).
Delete existing SharePoint Products and Technologies Configuration Wizard logs
1. Open a command window.
2. At the command prompt, type cd "%programfiles%common filesmicrosoft sharedweb server extensions12logs" and then press ENTER.
3. At the command prompt, type "del psc*.log" without the quotes and then press ENTER to execute.
Uninstall Beta 2 Technical Refresh
Perform the procedure in this section on all server computers in your farm. You can perform the steps in parallel across all server computers, or complete the procedure on each computer before moving to the next.
Uninstall Beta 2 Technical Refresh
1. In Control Panel, double-click Add or Remove Programs.
2. Uninstall all Microsoft Office SharePoint Server 2007 Language Packages.
Caution You must uninstall all language packs before you uninstall Office SharePoint Server 2007 Beta 2 Technical Refresh. If you do not uninstall all language packs at this point, you will be unable to install the release version of Office SharePoint Server 2007.
3. A message box appears to remind you to run the SharePoint Products and Technologies Configuration Wizard after uninstalling the language packs. You can ignore this reminder; click OK.
4. Select Microsoft Office SharePoint Server 2007, and then click Remove.
5. In the first message box that asks you to confirm that you want to uninstall, click Yes.
6. In the second message box that asks you to confirm that you want to uninstall, click OK.
7. If you are prompted to restart the computer, do so.
Install the release version of Office SharePoint Server 2007
The procedure in this section must first be performed on a front-end Web server that hosted the Central Administration Web application in your Beta 2 Technical Refresh installation, which you noted under "Record current server information," earlier in this article. After you successfully complete this procedure on that server computer, perform it on all the other server computers in the farm.
Note If upgrade fails on any server computer, do not run this procedure on any other computer in the farm until you have fixed the problem. After you have fixed the problem, run the SharePoint Products and Technologies Configuration Wizard again to resume upgrade.
Install Office SharePoint Server 2007 release version
1. Run Setup for the release version of Office SharePoint Server 2007.
2. Follow the steps to install the product. Be sure to select the same server type previously used for this server, and to enter a PID key corresponding to the same license type (Standard or Enterprise) that you selected when you installed Beta 2 Technical Refresh (you noted this information under "Record current server information," earlier in this article). Cancel the SharePoint Products and Technologies Configuration Wizard when it opens.
3. Install any Office SharePoint Server 2007 Language Packages. At the end of every language pack installation, cancel the SharePoint Products and Technologies Configuration Wizard when it opens.
4. Run the SharePoint Products and Technologies Configuration Wizard. Use the Central Administration account and password that you noted under "Record current server information," earlier in this article.
I found the above to not be true. I found it to work if I did it as my domain account, a local admin on the web server.
A message box appears to remind you that services will be started; click Yes.
A message box appears to remind you to run the wizard on each server in the farm; click OK.
Note Upgrade may only be run on one server computer in the farm at a time.
Ignore the warning displayed in the wizard that reads Failed to start search service SPSearchServinceInstance on this server after completing upgrade. Please start it manually. You will start this service in step 7.
Step 8 of 9 will take a long time to complete.
5. Wait until upgrade has been completed successfully on this server computer.
First Start of Central Admin will take a long time. And Each Site hosted by SharePoint takes a long time to load up the first visit. (may be related to virtual hardware)
6. Determine the search topology of the server computer by doing the following:
Before upgrade my server configuration looked as below.
a. Open SharePoint Central Administration, click Operations on the top navigation bar, and then click Services on Server in the Topology and Services section. On every application server on which the Office SharePoint Server Search service is started, note the following:
· If only the Use this server for indexing search content check box is selected, only the INDEXER role is enabled for the server.
· If only the Use this server for serving search queries check box is selected, only the QUERY role is enabled for the server.
· If both these check boxes are selected, both the INDEXER and QUERY roles are enabled for the server.
7. Open SharePoint Central Administration, click Operations on the top navigation bar, and then click Services on Server in the Topology and Services section. On every application server on which the Office SharePoint Server Search service is started, do the following:
a. On the Start menu, click Run.
b. In the Open box, type
cmd
and then click OK.
c. At the command prompt, type
cd Program FilesCommon FilesMicrosoft Sharedweb server extensions12BIN
d. Then type
stsadm -o osearch -action start
and then press ENTER.
8. On every application server on which the INDEXER role is enabled (regardless of whether the QUERY role is enabled), do the following:
a. On the Start menu, click Run.
b. In the Open box, type
regedit
and then click OK.
c. Find all subkeys in the registry that are of the following form: HKEY_LOCAL_MACHINESOFTWAREMicrosoftOffice Server12.0SearchApplications{Application GUID}. For each subkey that has this form, do the following:
· Set the (Default) key to On.
· Create a new subkey named Gathering Manager.
· Create a DWORD value named UseClustering under that subkey (value 0).
d. On the Start menu, click Run.
e. In the Open box, type
cmd
and then click OK.
f. At the command prompt, type
net stop osearch
and then press ENTER.
g. At the command prompt, type
net start osearch
and then press ENTER.
9. On every Web front-end and application server computer in your farm, do the following:
a. On the Start menu, click Run.
b. In the Open box, type
cmd
and then click OK.
c. At the command prompt, type
IISRESET
and then press ENTER.
10. On every application server that you noted in step 6 as having either the INDEXER role or QUERY role (but not both) enabled, do the following:
a. Open SharePoint Central Administration, click Operations on the top navigation bar, and then click Services on Server in the Topology and Services section.
b. (b)On every application server that has the QUERY role enabled (but not the INDEXER role), and on which the Office SharePoint Server Search Service is started, click Stop. Record all server names on which you perform this step. Wait for the status of each search service to change from Stopping to Stopped.
c. On each application server that has the INDEXER role enabled (but not the QUERY role), and on which the Office SharePoint Server Search Service is started, do the following:
· On the Start menu, click Run.
· In the Open box, type
cmd
and then click OK.
· At the command prompt, type
net stop osearch
and then press ENTER.
· At the command prompt, type
net start osearch
and then press ENTER.
d. Wait for five minutes.
e. Navigate back to the Services on Server page. On all servers that you stopped the search service on in step (b), click Start for the Office SharePoint Server Search service. Be sure to let each server complete initialization before you continue to the next server. (To determine when initialization is complete, look for the following values on the Shared Services Provider Search Settings page: starting -> started, Propagation status: Idle.)
After you have installed Office SharePoint Server 2007 release version, check that the Scopes drop-down list on the home page of each portal site displays all the search scopes you expect. If some scopes (for example, All Sites, People, and custom scopes) are missing, perform the following steps for each portal site.
Display search scopes on portal home pages
1. Browse to the home page.
2. Click Site Actions, point to Site Settings, and then click Modify All Site Settings.
3. In the Site Collection Administration section, click Search Settings.
4. Click Use custom scopes, and enter the path to the Search Center site. You can obtain the Search Center site URL by right-clicking Search in the top navigation bar on the portal home page, and then clicking Copy Shortcut. If the Search Center site has been customized, obtain the custom URL from your administrator.
Uninstall and reinstall Microsoft .NET Framework 3.0
After you have successfully installed the release version and verified that the search service is functional, perform this procedure on every server computer in your farm to install the final release version of .NET Framework 3.0.
Uninstall and reinstall Microsoft .NET Framework 3.0
1. In Control Panel, click Add or Remove Programs, select Microsoft .NET Framework 3.0, and then remove it.
2. Install Microsoft .NET Framework 3.0 (http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en).
After the reinstall of the .NET Framework 3.0 you will need to force the upgrade of all your infopath forms and workflows.
This is accomplished by running
stsadm –o reconvertallformtemplates
I found one final thing to be the case. Any Custom themes or visual style elements that you have configured on your Sharepoint will have to be reconfigured after the upgrade.
