Welcome to MSDN Blogs Sign in | Join | Help

Office SharePoint Server B2TR to RTM

Upgrading from Office SharePoint Server 2007 Beta 2 Technical Refresh to Release Version

Introduction

Follow the instructions in this article carefully when you upgrade from Office SharePoint Server 2007 Beta 2 Technical Refresh to the release version.

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.

In this article:

·         Prepare for upgrade#section1

·         Uninstall Office SharePoint Server 2007 Beta 2 Technical Refresh#section2

·         Install the release version of Office SharePoint Server 2007#section3

·         Uninstall and reinstall Microsoft .NET Framework 3.0#section4

#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_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\WSS\ServerRole 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.

·         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 Premium Features" 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

and then click OK.

2.    In the Registry Editor, navigate to the following subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0\Secure\ConfigDB

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

for the name, and then 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 files\microsoft shared\web server extensions\12\logs"

and then press ENTER.

3.    At the command prompt, type

del psc*.log

and then press ENTER.

 

#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.

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.

5.    Wait until upgrade has been completed successfully on this server computer.

6.    Determine the search topology of the server computer by doing 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. 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

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_MACHINE\SOFTWARE\Microsoft\Office Server\12.0\Search\Applications\{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).

 

See Also

Published Thursday, November 16, 2006 7:51 PM by joelo

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

Thursday, November 16, 2006 4:49 PM by Matthew Roberts

# re: Office SharePoint Server B2TR to RTM

Joel - thanks so much for posting this information - it really helps partners and clients get a jump on our planning.  The link you provided for the registry utility via Help and Support appears to be broken...

Thursday, November 16, 2006 8:45 PM by Microsoft SharePoint Products and Technologies Team Blog

# Announcing the RTW of WSS and Office SharePoint Server 2007 Standard and Enterprise Evaluation!

It is my pleasure to announce the RTW of WSS 3.0 and Office SharePoint Server 2007. Please read the all

Friday, November 17, 2006 12:21 AM by The SharePoint Farmer's Almanac

# Installing MOSS 2007 RTM on a farm running MOSS 2007 Beta2 TR

Tomorrow sometime Microsoft will release Office SharePoint Server 2007 for download at the Microsoft

Saturday, November 18, 2006 12:35 AM by Dan Attis

# SharePoint 2007 - Office SharePoint Server Beta 2 TR to RTM Upgrade Instructions

Looks like MSFT will be dropping this very soon (maybe this weekend). Here is a link to the upgrade...

Tuesday, November 21, 2006 10:40 PM by Bob Fox's Sharepoint Blog

# B2TR to RTM Screenscast

I have created a Screencast to accompany Joel Oleson and Shane Youngs great posts. ...

Thursday, November 23, 2006 4:19 PM by Kumar

# re: Office SharePoint Server B2TR to RTM

Can I uninstall MOSS 2007 B2TR (Enterprise) and clean install MOSS 2007 (Std or Ent)?

Friday, November 24, 2006 12:43 AM by Andrew C

# re: Office SharePoint Server B2TR to RTM

This does not seem to work for a basic, standalone versions using sql express.  It just uninstalls everything and install a fresh copy :-((

Any suggestions?

Sunday, November 26, 2006 12:36 PM by XML is the glue...

# SharePoint 2007 Überblick

Nachdem Anfang des Monats der Office 2007 Golden Code angkündigt wurde, hat sich einiges in der SharePoint/Office

Wednesday, November 29, 2006 10:32 AM by Kumar

# re: Office SharePoint Server B2TR to RTM

I have B2TR installed on the server. I do not have any sites that I needed. Could you please point out any resources to on how I can unstall B2TR and clean install MOSS 2007?

Saturday, December 02, 2006 8:54 PM by bob

# re: Office SharePoint Server B2TR to RTM

In our dev farm environment, it was necessary to stop the WSS Tracing service before uninstalling B2TR.  Failing to do this resulted in the uninstall process hanging about half way through.

Monday, December 04, 2006 2:06 PM by scottdotnot

# re: Office SharePoint Server B2TR to RTM

are these instruction faily the same for wss3.0

Friday, December 08, 2006 4:19 PM by Kevin Cole

# re: Office SharePoint Server B2TR to RTM

I ran into a problem upgrading it During Step 5

...

Actually 2 problems.

1. It kept waiting and waiting and waiting, so I checked the update log and lo and behold it was sleeping eternally 10 seconds at a time.  So I rebooted the machine.

2. It ran into an exception:

- Cannot drop some procedure on a Sharepoint_admin content database....

How I fixed it was, I noticed that the impersonation account had it's own schema for some reason.  This schema was being applied to the stored procedures so it was looking like:

iomer\ipersonateme.proc_FixV2ContentTypeField in the database when I looked at it with enterprise manager.

I droped the procedures manually, and then created new dummy procedures from my account (which created them with the dbo schema)

Then I re-ran the config wizard and it was fixed!

Hooray!, Score one unknown problem solved by Kevin.

Sunday, December 10, 2006 8:23 AM by Matthew McDermott

# re: Office SharePoint Server B2TR to RTM

Joel, Thanks for the details! I posted on what can go wrong. (Totally my fault.)

Wednesday, December 13, 2006 2:08 AM by joelo

# re: Office SharePoint Server B2TR to RTM

These are for MOSS only.  There are separate WSS steps.

Tuesday, December 19, 2006 7:17 PM by Bob Fox's Sharepoint Blog

# Upgrading B2TR to RTM (Multi Server Farm )

A few weeks ago Joel Oleson, Shane Young and I provided some posts that walked you through updating your...

Sunday, December 24, 2006 4:12 AM by Joshua Johnson

# re: Office SharePoint Server B2TR to RTM

I've been having a lot of trouble upgrading...I'm now getting a generic error when installing MOSS 2007 RTM "Microsoft Office SharePoint Server 2007 encountered an error during setup." When looking in the installation log, I can across the follow:

MSI(INFO): 'ExecServiceConfig:  Configuring Service: SPAdmin'

MSI(INFO): 'ExecServiceConfig:  Error 0x80070424: Service "SPAdmin" does not exist on this system.'

It looks like the installation starts rolling back after this.

Any help?

Wednesday, February 14, 2007 1:15 PM by Sean Kelly

# re: Office SharePoint Server B2TR to RTM

I upgraded from B2TR to RTM but now have several problems. For example, when I go to Site Settings, Galleries, WorkFlows I receive the following error message:

Failed to find the XML file at location '12\Template\Features\PremiumRootSite\feature.xml'

I am seeing similar errors on other screens and also in the change log.

Does anyone know how to fix this?  Thanks.

Friday, March 16, 2007 4:19 PM by ...

# re: Office SharePoint Server B2TR to RTM

pagine piuttosto informative, piacevoli =)

Wednesday, July 25, 2007 4:20 PM by Matthew McDermott

# SharePoint B2TR to RTM Upgrade

Leave a Comment

(required) 
required 
(required) 

  
Enter Code Here: Required
 
Page view tracker