1

How to move SharePoint content from Windows SharePoint Services 3.0 to Microsoft Office

SharePoint Server 2007 and configure it to serve the Team Project Portals for Team Foundation

Server 2008

By Arun Ramalingam, Microsoft Corporation

Posted to http://blogs.msdn.com/dstfs April 10, 2009

This document addresses the scenario where you wish to move the existing SharePoint sites being server from a

Windows SharePoint Services 3.0 instance to a remote Microsoft Office SharePoint Server 2007 server. The steps

include:

1) Installing Microsoft Office SharePoint Server 2007 as a single server with all the services like Search, Shared

Service Providers, Web application service etc… running on this one server. Run the SharePoint products and

technologies wizard to set the Central Administration page.

2) Enabling “Windows SharePoint server search” .

3) Create a new web application to host the TFS Site Collection.

4) Move the Content database: Detach the MOSS Content database (or take it offline) and attach the content

database from the Windows SharePoint Services 3.0 TFS web application.

5) Install the SharePoint extensions on the MOSS 2007 server and configure SharePoint and reports URL.

6) Configure the new SharePoint URL on the Application tier using “Tfsadminutil configureconnections”

Environment used for this walkthrough

TFS Application Tier Name: 2003AT (Win 2003 x86, WSS 3.0, IIS 6.0)

TFS Data Tier name: 2003DT (Win 2003 x86, SQL 2005)

MOSS 2007 Server name: mossserver2007 (Win 2003 x86, MOSS 2007)

Domain name: arunrama.com

2

Step1: Installing MOSS 2007 on the mossserver2007 box and setting up the Central

Admin page.

To complete this process, you must have a server that complies to the Hardware and software requirements as

mentioned in http://technet.microsoft.com/en-us/library/cc262485.aspx

1) Once all the prerequisites are installed start the Microsoft Office SharePoint server 2007 installation

2) Enter the Product Key and click continue

3) Accept the License agreement and click continue

4) On the “Choose the installation you want” screen select “Advanced”

3

5) On the “Server type” screen you are given three options:

1. Complete - Enables all the options for a single server to offer the entire range of MOSS 2007 services and

features. You can scale out this deployment, start and stop services on this server and use a backend SQL

server to host your databases. (Note: we will be selecting this option for our walkthrough)

2. Web Front End - Enables only those options that allows the server to run as a web front end server. This

option is ideal for a MOSS server in a server form and serves as a Web front End. Mostly used to improve

performance.

3. Stand-Alone: Similar to complete, this option enables all of the services and features for the MOSS 2007

farm, but assumes that there is no SQL server, so the MSDE engine is installed locally on this server. You

cannot scale out this server into a larger MOSS 2007 farm.

Select “Complete” and click “Install Now”

6) Wait for the installation to complete

4

7) On the installation completion screen select the check box that says “Run the SharePoint Products and

Technologies Configuration Wizard”

8) The “SharePoint Products and Technologies Configuration Wizard” starts, click Next

5

9) Accept the warning screen

10) On the “Connect to a server farm” page select “No, I want to create a new server farm” and select NEXT

6

11) On the “Specify Configuration Database Settings” page enter these values and click NEXT:

Database Server : the server name that is going to hold the Configuration database: "2003DT"

a) Database Name: enter a name for the database: "MOSS_Config"

b) Username: enter a windows account that will be used to connect to the configuration database,

arunrama\tfsservice

c) Password: enter the password for the account.

12) On the “Configure SharePoint Central Administration Web application” page enter the values and click NEXT

a) For “Specify port number” , you could take the default or check the box and enter a port you wish, 17012

b) For Configure security settings, select “NTLM” (Note: TFS will work only with NTLM)

7

13) Once the configuration completes you see a completion screen. Hit FINISH.

8

Step2: Enabling “Windows SharePoint server search”

1) Launch the Central administration page for the mossserver2007 instance. You can access this directly in a web

browser by navigating to HTTP://<MOSSserver>:<AdminPort>. You should see “Server Farm Configuration Not

Complete". This is because the essential services are not started yet.

2) Browse to “Operations” tab and select “Services on server”

9

3) Click on “Windows SharePoint Services Search” and the “Configure Windows SharePoint Search Service Settings

on server MOSSSERVER2007” windows appear. Enter the values and click Start

a) Service Account: enter a Domain account (not a built-in account) that will run the search service

b) Content Access Account: enter an account to access the contents of the search service.

c) Search Database: Enter the server name and a database name. Select “windows authentication” for

authentication type. This will be "2003DT" in our case.

d) Indexing Schedule: Leave it as default.

Windows SharePoint services search is now enabled.

10

Step 3: Create a new web application to host the TFS Site Collection

In this section we will be creating a new web application (web site) in MOSS 2007 server to host the site

collection for TFS. The Content database from WSS 3.0 will be moved to this Web application.

1) Browse to the Central administration page and select “Application management”. On the Application

management page select “Create or extend web application” and select “Create new web application”.

Enter a name for the site that you wish to host the TFS site collection on. Enter the Port number for the site

to be created on and select “NTLM” for Authentication provider.

2) (Contd…) Select “No” for Allow Anonymous” and "No" for “Use Secure Socket Layer (SSL). Accept defaults

for “Load balanced URL”. Configure “Application Pool” depending on your wish to use the “DefaultAppPool”

or a new application pool. Depending on your selection for Application Pool, you will be prompted to

configure the identity that runs the Application pool.

11

3) (contd..) Select your option for “Reset Internet Information Services”. For “Database name and

authentication” enter the server name (server\instance if SQL data base engine is on a named instance) that

will hold the Content database for this Web application and modify the name of the content database. Set

the “Database authentication” to “Windows Authentication”. Click OK to create the New Web application.

12

4) A new web application is created

5) The new web application goes by the link http://mossserver2007:83 and its content database can be viewed

under Application Management > Content Databases

13

Step 4: Move the Content database

1) Switch back to Application tier (2003AD) and browse to the Central Administration page of WSS 3.0.

Select “Application management” and then select “Content databases”. Once the Manage Content

databases site comes up make sure that you are working with the content database for your TFS portal

site by checking the link shown besides “Web Application”.

2) Click on the database name “WSS_Content” , it brings up the “Manage Content database Settings” page.

You can either remove the content database by selecting “Remove content database” or alternatively

change the Database Status to “Offline”

14

3) On the Moss server (mossserver2007) browse to the Central Administration page, select “content

databases”. Click on the Database name “WSS_Content_Mosstfs” and Either Remove the content

database by selecting “Remove content database” or alternatively change the Database Status to

“Offline”

4) Open command prompt on the Moss server (mossserver2007) and switch to <drive>\program

files\Common files\Microsoft shared\Web server extensions\12\bin and type the command

Stsadm –o addcontentdb –url http://mossserver2007 :83 –databasename wss_Content –databaseserver

2003dt

Values: -url > the url fro the new web application that we had created to host the TFS projects

-Databasename > Name of the old content database that was holding the tfs projects on WSS3.0

-Databaseserver > The SQL instance that will hold the Content database.

15

5) Verify the content database move by accessing the “Content databases” page under “Application

Management” page of Moss server’s central administration page.

6) Reset IIS by running IISRESET.

16

Step5: Install the SharePoint extensions on the MOSS 2007 server and configure

SharePoint and reports URLs

1) On the Moss server (mossserver2007), Run the “Microsoft Visual Studio 2008 Team Foundation Server

SharePoint server extensions” installation wizard from the TFS 2008 installation media.

2) Accept the defaults and complete the installation

17

3) Once you click “Finish” , “Team Foundation Server SharePoint Configuration” wizard pops up. Enter the

values requested.

Values: Windows SharePoint Service site > The URL of the site collection that hosts the TFS projects

portals (http://mossserver2007:83/sites)

Reporting Services reports site > The URL of the reports manager site. Note that the site is

running off the Application tier (http://2003at:80/reports)

Reporting Services administrative site > The URL of the report server site. Note that the site is

running off the Application tier (http://2003at:80/reportserver)

18

Step6: Configure the new SharePoint URL on the Application tier using “Tfsadminutil

configureconnections”

1) On the Application tier (2003at) open a command prompt and switch to <drive>:/Programs files/Microsoft

Visual Studio 2008 Team Foundation Server\Tools and run the “TfsAdminUtil Configureconnections view”.

You should see the current configuration and the SharePoint sites are still pointing to the old WSS 3.0 sites.

2) To modify the SharePoint values use the” TfsAdminUtil Configureconnections” with the switches given

below:

/SharePointUri: http://mossserver2007:83

/SharePointSitesUri:http://mossserver2007:83/Sites

/SharePointAdminUri:http://mossserver2007:17012

3) Once the configuration changes are successful, do a IIS reset

You have now moved your Team Project Portals for Team Foundation Server 2008 from WSS 3.0 to MOSS 2007. As you

are using TFS 2008, you can even go one step further at this point and uninstall WSS 3.0 from your TFS AT if you like - it

is no longer needed there.