Team Foundation Server

How to make TFS with a User domain over a 1-way external trust with Selective Authentication

I had been working on making TFS work with users from an external forest over a 1-way outgoing trust configured with Selective Authentication & wanted to share the same across.

Goal:

Provide access to users from a UserDomain to a TFS Server in the TFSDomain & perform day-to-day tasks including Team Project Creation.

Detailed Scenario:

Domain1 (aka “TFSDomain”)

Domain Functional Level: Windows Server 2003 [Required for Selective Authentication]

Forest Functional Level: Windows Server 2003 [Required for Selective Authentication]

TFS Single Server (Windows Server 2008 + SQL 2008 + TFS 2008 SP1) as member server of the TFSDomain

Domain2 (aka ”UserDomain”)

Domain Functional Level: Windows Server 2003 [Required for Selective Authentication]

Forest Functional Level: Windows Server 2003 [Required for Selective Authentication]

TFSDomain has a one-way external outgoing trust with a User Domain. The authentication type for the trust is “Selective Authentication”(Instructions for configuring Selective Authentication are available here). Selective authentication gives us the capability to allow specific users\groups from the UserDomain to logon/access/authenticate with specific servers/machines in the TFSDomain.

To enable this setup, following implementations needS to be in place:

1. All users in UserDomain who need to access TFS will need to be granted the “Allow to Authenticate” right on the computer account of the TFS Server in the TFS Domain. You can do this by requesting your domain admin to perform the steps mentioned in http://technet.microsoft.com/en-us/library/cc738653(WS.10).aspx.

2. TFS Service account must be a user account from the user domain. Follow instructions in  http://msdn.microsoft.com/en-us/library/bb552178.aspx  for updating/changing the service account.
***The service account will need to come from the user domain for GSS sync to work because of the 1-way trust in place***

3. Optional: If you want users form TFS domain to access the TFS server as well, you would need to grant the “Allow to Authenticate” right to the TFS Service account(a user account form the user domain) to the computer account for the domain controller of the TFS domain as well.

A high level diagram of how this implementation would look like:

 

Reporting Services installation/configuration does not set the NTAuthenticationProviders

I wanted to bring forward an issue(probably not the correct word) with RS 2005.

 

We typically do the following types of TFS installations, dual server & single server.

 

A typical dual server environment has the following setup: [All SQL Server versions are 2005 only]

Machine A(called as DT) will have SQL Engine & Analysis Services.

Machine B(called App Tier) will have RS, SharePoint & TFS.

 

A single server setup will have SQL, RS, SSAS, SharePoint & TFS running on the same box.

 

The point here is that TFS + RS + SharePoint will be on the same box as part of a typical TFS deployments & SQL & SSAS can be on same or diff box.

 

During TFS installations, RS is installed on the TFS box beforehand(as a pre-req) & SharePoint is installed(typically) as part of TFS installation. SharePoint extends the default web site & sets the “NtAutheticationProviders” to NTLM. After a successful installation of TFS the users create Team Projects. For each team project new reports are uploaded to the report server & a new site collection is created in SharePoint. Clients(machines which have Visual Studio Team Explorer installed) are able to browse reports & SharePoint project portals along with TFS components with no issues. The users can also browse reports directly in IE on their machines as well.

 

Now the real thing, with TFS 2008 we support multi-tiered deployments for TFS. One such deployment could involve machines as follows:

#1 Machine A hosts SQL & Analysis Services

#2 Machine B hosts an existing(not installed and configured during TFS installation) SharePoint farm.

#3 Machine C hosts Reports & TFS.

 

In this kind of a setup when we install TFS on machine# 3, SharePoint is not installed on TFS box(Machine #3). RS 2005 is installed on machine# 3 as pre-req before installing TFS but it is not configured. When a TFS admin will install TFS on machine #3, TFS installation will configure RS as part of its installation & will create Reports & ReportServer virtual directories under the default web site. Also TFS installation will set the NTAuthenticationProviders for the TFS web site explicitly to NTLM. It does not however configure/set the NtAuthenticationProviders to NTLM for the default web site, which is hosting the reports virtual directories.

 

As a result the NtAuthenticationProviders for the default web site will default to “Negotiate, NTLM”, which is the default for IIS for any web site for which the NtAuthenticationProviders is not set explicitly.

 

So the behavior that we get because of this is, on machine# 3, the TFS Application Tier box, Reports work in Team Explorer, IE, etc. However when you try to browse reports from a client box, through IE or VS, you will get a prompt for user credentials three times & then reports will not show up (it fails giving 401.1 error if you browsed reports in IE). Your Event Viewer->System Logs will show a Kerberos related error on the client box.

 

To resolve this issue either setup Reports to work with Kerberos Authentication. To do this follow this link http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/df979570-81f6-4586-83c6-676bb005b13e.mspx?mfr=true mentioned in http://msdn.microsoft.com/en-us/library/bb283249(SQL.90).aspx.

 

Or if you want NTLM as the preferred authentication provider, then use the following command on the AT box(kb215383):

1.  Click Start , click Run , type cmd , and then press ENTER. 

2.  Locate the directory that contains the Adsutil.vbs file. By default, this directory is C:\Inetpub\Adminscripts. 

3.  Use the following command to enable the Negotiate process:

cscript adsutil.vbs set w3svc/WebSite/root/NTAuthenticationProviders "NTLM"

     In this command, WebSite is a placeholder for the Web site ID number. The Web site ID number of the default Web site is typically 1.

Unable to upgrade from TFS 2005 to TFS 2008 when TFS 2005 is working with a SQL 2008 instance.

Configuration: Unable to upgrade from  TFS 2005 to TFS 2008 when TFS 2005 is working with a SQL 2008 instance.

The scenario is like this:

TFS 2005 was initially installed with a SQL Server 2005 default instance as the data store.

Post installation of TFS 2005 the customer upgrades SQL Server 2005 default instance to SQL Server 2008 default instance.

This causes TFS 2005 servicing to fail.

This also impacts TFS 2005 to TFS 2008 upgrades

 

Why is this unsupported:  SQL Server 2008 is not a supported for DT configuration for TFS 2005.

 

Symptoms you might see: 

Servicing for TFS 2005 fails.

TFS 2005 to TFS 2008 upgrade fails.

 

Remediation Options:

Upgrade TFS 2005 to TFS 2008 using a TFS 2008 + SP1 slipstreamed setup. Instructions to create a slipstreamed setup for TFS 2008 are available in TFS 2008 SP1 install guide: http://www.microsoft.com/downloads/details.aspx?FamilyID=FF12844F-398C-4FE9-8B0D-9E84181D9923&displaylang=en

 

For customer who want to rollback to SQL 2005 to remain in a serviceable TFS 2005 state:

The biggest challenge is SQL 2005 does not recognize the database backups taken from a SQL Server 2008 instance. In simple words we cannot restore a SQL Server 2008 database to a SQL Server 2005 instance. If the customer has recently upgraded their SQL from 2005 to 2008 & if they had taken database backups before a SQL 2005 to 2008 upgrade & they are willing to rollback to a previous database state, they can revert to SQL 2005 configuration as a data store. They can follow the instructions in the restoration based move also called hardware based move to do this task. (http://msdn.microsoft.com/en-us/library/ms404869(VS.80).aspx).

I would advice upgrade TFS 2005 to TFS 2008 instead of rolling back SQL 2008 to SQL 2005.

 

Posted by Lakhminder | 0 Comments

Filed under: TFS, Team Foundation Server, SQL Server, SQL 2008, TFS 2005, Upgrade, Servicing

Unable to service TFS 2008/2005 instance running on a Domain Controller

Configuration: Unable to service TFS 2008/2005 instance running on a Domain Controller

The scenario is like this:

Customer installs TFS 2005/TFS 2008 on a Window Server 2003/2008 member server or standalone server.

Customer make the member server a domain controller.

This does not impact the TFS functionality unless the customer wants to do servicing of TFS 2005/2008 or tries to upgrade TFS 2005 to TFS 2008.

 

Symptoms a customer might see:

The servicing of TFS 2005/2008 or upgrade of TFS 2005 to TFS 2008 will fail with TfsGssInit.exe errors.

 

Remediation Options:

Bring up a new Server 2003/Server 2008 member server box & install TFS 2005/2008 on it.

Follow instructions in the h/w based move article to move the TFS instance to the new box.

(http://msdn.microsoft.com/en-us/library/ms404869(VS.80).aspx)

(http://msdn.microsoft.com/en-us/library/ms404869.aspx )

Uninstall TFS 2005/TFS 2008 from the Domain Controller. (Instructions available in install guide)

 

 

TFS 2008: How to move RS 2005 to a new server

1.       Follow KB 842425 to move RS DB to a new instance.

2.       Ensure that you have a login for the TFS Reports account, in case your RS databases are now going to hosted on a different SQL instance. The login for the RS database should have RSExecRole in Report Server databases (which it should retain when you restore the RS databases.)

3.       Create new data connections for TfsReportsDS & TfsOlapReportsDS if required. (Refer to here http://social.msdn.microsoft.com/Forums/en-US/tfsreporting/thread/fc53be12-2ebd-41c8-a66a-ccd4437033fd)

4.       Run TfsAdminUtil ConfigureConnections command to update setting /ReportsUri and /ReportServerUri.  Consider http://support.microsoft.com/kb/959126 while doing it.

5.       Run the TFSWSSConfig.exe on the SharePoint instance to update the reports redirector.

6.      On the AT, edit the MSIProperty.ini file & change the RS machine name for the VSTF_RS_SERVER property. You just need to give new machine\server name for RS & do not give the instance name. Optionally update the VSTF_RS_REPORTS_URI, & VSTF_RS_REPORTSERVER_URI properties.

TFS WSS x64 Installation issue

While installing the latest 64 bit wss tfs extensions you would recieve the following error.

No templates for Windows SharePoint Services Extensions were uploaded to the server that is running Windows SharePoint Services. You will not be able to create projects in Team Foundation Server. For more information, see the Microsoft Windows Installer (MSI) log file. By default, this log file is located in Drive:\Documents and Settings\UserName>\Local Settings\temp.

Could not upload the template that Team Foundation Server requires for Windows SharePoint Services Extensions. Stsadm.exe returned the following error: -1.

To resolve what you are getting, you would need to do this:

1. Download the WssExt64Bit.msi file from http://www.microsoft.com/Downloads/details.aspx?FamilyID=fbd14eea-781f-45a1-8c46-9f6ba2f68bf0&displaylang=en

2. Do Windows Installer Admin install for the wssext64Bin.msi file as:
a. Open an elevated command prompt window
b. Run: msiexec /a <<Path to wssext64bin.msi>> TARGETDIR=c:\WSSExt64
c. This would start the admin installation for wssext64.msi & the binaries would be copied to c:\WSSExt64 folder. If you open this folder you would see that admin install has laid down a folder structure under the wssext64 folder. This folder structure represents the actual folders which would have files added to them if the installation would have been done normally.
The folder structure created would be:

3. While still in the elevated command prompt, change to the folder C:\WSSExt64\Tools & run the command:
TFSConfigwss.exe uploadtemplates

4. While still in the elevated command prompt, type TfsConfigwss.exe & hit enter. Provide the Site Collections uri, Report Manger & Report Server uri in the following dialog:

5. Do an IISReset on the MOSS/SharePoint x64 machine. Close the elevated command prompt.

6. Copy the tfsredirect.aspx file from C:\WSSExt64\Common Files (64-bit) Folder\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS to C:\Program Files\Common Folder\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS folder.

Do the above steps on all MOSS/Sharepoint x64 instances if applicable.

Migrating SharePoint to a new box

Team Foundation Server 2008 a.k.a. Orcas (& TFS 2005 as well) provides you the capability to leverage a remote SharePoint deployment to host the team project portals. I will talk about here on the steps to migrate SharePoint from one box to another from a TFS point of view.

So think about a scenario where you have an existing SharePoint deployment on the Application Tier or another box which is integrated with TFS & you want to move this SharePoint instance to a new box & you want TFS to talk to this new instance for SharePoint things. To do so follow these steps:

Step 1. Identify the current SharePoint instance which is working with TFS.

To do this open a command prompt window & change to the Tools folder in your TFS installation directory & run the following command:

TfsAdminUtil.exe ConfigureConnections /View

A sample output would be:

In the output notice the value for SharePointAdminUri. This is the central admin site’s url for the source SharePoint instance with which TFS is configured to work with presently. Note the value for the SharePointUri. This is the web application that is presently hosting your team portals.

Note the values for ReportsUri & ReportServerUri. These would be required during step #5.

Open a new IExplore window & browse the source central admin site as http://<machinename>:<port number>

Where machine name & port number are the one’s reported in the output of the command for the SharePointAdminUri.

So with the central admin site open, we need to go to the Application Management tab. In the Application Management tab, under SharePoint Web Application Management select Web application list to open the Web Application List page. Click the web application which is listed as the value of SharePointUri in the output of the TFSAdminUtil ConfigureConnections /View command. The objective here is that we want to know the name of the content database for the web application that is hosting the TFS team portals & the database server that is hosting it.

With the correct web application selected, click Application Management-> SharePoint Web Application Management->Content Databases to open the content databases web page. Click the content database which is shown in the list to open the Manage Content Database Settings web page.

On the Manage Content Database Settings web page, note the name of the Database Server & the name of the content database.

At this point we have identified the following:

a. The Source SharePoint Central Admin Site Url & the Web Application url hosting the team portals for TFS.

b. The name of the content database that contains the project portals.

c. The SQL Server instance hosting the content database.

Step 2. Take a backup of the content database from the SQL Server instance which we figured out in Step# 1. Please refer to http://msdn.microsoft.com/en-us/library/ms253070.aspx for procedures to take a backup.

Once you have taken a backup of the correct content database you should restore the content database to the SQL Server instance that will host the SharePoint databases for the target SharePoint instance.

If the target SharePoint instance will be using the same SQL Server instance as that of the source SharePoint instance, you should restore the database on the SQL Server instance with a different name.

General instructions for SQL Database backup & recovery process are available at http://msdn.microsoft.com/en-us/library/ms177429.aspx.

Note: If you are using/decide to use a different SQL Server instance for the target SharePoint instance (other than the SQL instance which is hosting your TFS databases & source SharePoint databases), the TFS Service account should have a login created for it in the SQL Server instance & should be granted the DbCreator & SecurityAdmin Fixed Server Roles in the SQL instance. A more appropriate statement is, ensure that the account which will be the identity account for the application pool of the web application that will be hosting the team project portals has a login in SQL & has the DbCreator & SecurityAdmin Fixed Server Roles granted to the login.

At this point we have restored the content database to a SQL Server instance & we will consume this database as the content database of the web application for TFS on the target SharePoint instance.

For simplicity sake I call the restored database as “WSS_Content”

Step 3. It’s time to move over to the target SharePoint instance. On the target SharePoint Instance the first thing that we need to do is to create a new web application. Typically I expect the default web site on the target box to be in an un-extended state & we want to extend the default web site with SharePoint.

You always have the option of extending any un-extended & available physical site in IIS on the target box with SharePoint or create a new web application from within the Central Administration site itself, & use this web application for hosting the TFS Project portals.

To extend the Default Web Site with SharePoint, launch the central administration site on the target SharePoint instance and:

1. Click Application Management tab in WSS 3.0 Central Administration site.

2. In Application Management tab, under SharePoint Web Application Management, click Create or extend Web application.

3. In the Create or Extend Web application page, click Create a new Web application.

4. In Create New Web Application page, select Use an existing IIS web site & select Default Web Site in the drop down list. In Application Pool settings, ensure that Create a new application pool option is selected & give TFSWSS30 as the name of the new application pool. Ensure that Configurable option is selected & give the Domain\TFSService account as the service account for the application pool. Ensure that Restart IIS automatically is selected. In the Database Server give the SQL Server instance name for TFS 2008. Give WSS_Content_Temp as the Database Name. Click OK to create the new web application with the default web site extended in WSS 3.0.

Step 4: Attach the content database restored in Step #2 to the new web application

Open a command prompt window & change to the folder %Program Files%\Common Files\Microsoft Shared\web server extensions\12\BIN. Delete the temporary content database using the command:

stsadm –o deletecontentdb –url http://<AppTierName> –databasename WSS_Content_Temp

To attach the WSS_Content database to the default web site run the following command:
stsadm –o addcontentdb –url http://<AppTierName> –databasename WSS_Content

Note: The content database was restored with the name WSS_Content in Step #2. Use should use the name which you had given for the content database during the restore process in Step #2.

Step 5: Install TFS 2008 Extensions for WSS

Install TFS 2008 extensions for SharePoint 3.0 from <TFS Installation Location>\wssext folder by running the setup.exe. At the end of installation, after you have clicked Finish, you would be prompted with the dialog box for the WSS 3.0 web part configuration.
Provide the http://TargetSharePointMachineName/sites as the WSS site

Provide the uri which we noted for ReportsUri in step#1 for the reports site. eg: http://lucky-bpa/Reports_TFS2k8

Provide the uri which we noted for ReportServerUri before ReportService.asmx in step#1 for the report server uri . For Eg: http://lucky-bpa/ReportServer_TFS2k8

Click Apply.

Click Exit.

Step 6: Update TFS to use the new target SharePoint Instance

To do this open a command prompt window & change to the Tools folder in your TFS installation directory & run the following command:

TfsAdminUtil.exe ConfigureConnections /SharePointUri:http://<targetSharepointmachinename>:80 /SharepointSitesUri:http://<targetSharepointmachinename>:80/Sites /SharePointAdminSiteUri:http://<targetSharepointmachinename>:17012/_vti_adm/admin.asmx /SharePointUNC:\\<targetSharepointmachinename>\Sites

Note: Substitute the port number values in the above command with the port numbers that are applicable on the target SharePoint Instance.

TFS 2008 & How to Uninstall & Reinstall WSS 3.0

How to uninstall & reinstall Windows SharePoint Services 3.0 with Team Foundation Server 2008

This post is specific to:

1. Team Foundation Server 2008

2. Local installation of Windows SharePoint Services 3.0 (with SP1).

The overall steps required to perform the stated task are:

1. Take a full back up of the content data base.

2. Remove SharePoint from the content site which is normally the default web site.

3. Uninstall Windows SharePoint Services 3.0 from the machine.

4. Drop the WSS_AdminContent & WSS_Config databases.

5. Install Windows SharePoint Services 3.0 on the machines

6. Run the SharePoint Point Products & Technologies Wizard

7. Create a new Web Application to host the Project portals

8. Attach the content database to the new web application

9. Install TFS 2008 Extensions for WSS

Take a back of the content database

Please refer to http://msdn.microsoft.com/en-us/library/ms253070(VS.80).aspx for procedures to back up databases.

To know the name of the content database to backup:

1. Launch SharePoint Central Administration site from Start->Administrative Tools-> SharePoint 3.0 Central Administration.

2. Click on the Application Management tab.

3. Under SharePoint Web Application Management, click Content Databases.

4. In the Manage Content Databases page, note the name of the database. This is the database which you need to take a backup of.

Remove SharePoint from the Default Web Site/Content Site

1. Launch Start->Administrative Tools-> SharePoint 3.0 Central Administration.

2. Click on the Application Management tab.

3. Under SharePoint Web Application Management, click Remove SharePoint from IIS Web site.

4. In the Remove SharePoint From IIS Web Site page, ensure that
a. Web Application is set to http://machinename
b. Select IIS Web site and zone to remove is set to Default Web Site(default)
c. Delete IIS Web sites is set to No.

5. Click Ok to remove SharePoint from the default web site.

6. On the Application Management tab, under SharePoint Web Application Management, click Delete Web application.

7. On the Delete Web Application page, ensure that
a. Web Application is set to http://machinename
b. Delete content databases is set to No.
c. Delete IIS Web sites is set to No.

8. Click Ok.

Close the Central Administration Site.

Uninstall Windows SharePoint Services 3.0 from the machine

To uninstall WSS 3.0:

1. Go to Start->Control Panel->Add/Remove Programs.

2. Select Microsoft Windows SharePoint Services 3.0 & click Remove.

3. You should be prompted with a dialog box stating “Are you sure you want to remove Microsoft Windows SharePoint Services 3.0 from your machine?”. Click Yes.

4. You should be prompted with another Warning dialog box stating “Before uninstalling this product, note the following:

4.- Removing this product might result in partial loss of functionality for sites that depend on features installed by this product.

4.- If you installed this product over an existing SharePoint Products and Technologies installation or choose to cancel the uninstall after this dialog box, you must run the SharePoint Products and Technologies Configuration Wizard to reconfigure the server farm after Setup has exited.

4.Do you want to uninstall now?”.
Click Ok to start the un-installation for WSS 3.0.

5. Once the un-installation is complete, click Close on the confirmation dialog box.

6. Click Yes to reboot the box.

Drop the WSS_AdminContent & WSS_Config databases

1. Launch SQL Server Management Studio from Start->All Programs-> Microsoft SQL Server 2005-> SQL Server Management Studio.

2. Connect to the appropriate Database Engine instance.

3. Expand Databases.

4. Right click on WSS_AdminContent & select Delete.

5. In the Delete Objects dialog box, check “Close existing connections” & click Ok to drop the WSS_AdminContent database.

6. Right click on WSS_Config & select Delete.

7. In the Delete Objects dialog box, check “Close existing connections” & click Ok to drop the WSS_Config database.

Install Windows SharePoint Services 3.0 on the machines

1. Run SharePoint.exe.

2. Accept the terms of Agreement & click Continue.

3. Click Advanced in the Choose the installation you want dialog.

4. Select Web Front End as the Server Type, confirm the installation location & click Install Now.

5. Once the installation is complete, make sure the check box for Run the SharePoint Products & Technologies Configuration Wizard now is selected & click Close.

Run the SharePoint Point Products & Technologies Wizard

Complete the SharePoint Products & Technologies Wizard to set up the WSS 3.0 central admin site & WSS 3.0 services on the box.

1. Click Next on the Welcome page.

2. Click Yes to allow the Wizard to Restart IIS & WSS services.

3. In the Connect to a server farm dialog, select No, I want to create a new server farm & click Next.

4. In the Specify Configuration Database Settings dialog box, give the SQL Instance name for your TFS, WSS_Config as the database name & the Domain\TFSService account name & password & click Next.

5. In the Configure SharePoint Central Administration Web Application dialog, check Specify port number & provide 17012 as the port number for WSS Central Administration site. Make sure that authentication provider is set to NTLM(which is the default selection) & click Next.

6. In the Completing the SharePoint Products and Technologies Configuration Wizard dialog, confirm the settings & click Next.

7. Once the wizard has successfully completed, click Finish. This would open up the WSS 3.0 Central Administration site.

Create a new Web Application to host the Project portals

Create a Web Application & extend the Default Web Site with WSS 3.0.

1. Click Application Management tab in WSS 3.0 Central Administration site.

2. In Application Management tab, under SharePoint Web Application Management, click Create or extend Web application.

3. In the Create or Extend Web application page, click Create a new Web application.

4. In Create New Web Application page, select Use an existing IIS web site & select Default Web Site in the drop down list. In Application Pool settings, ensure that Create a new application pool option is selected & give TFSWSS30 as the name of the new application pool. Ensure that Configurable option is selected & give the Domain\TFSService account as the service account for the application pool. Ensure that Restart IIS automatically is selected. In the Database Server give the SQL Server instance name for TFS 2008. Give WSS_Content_Temp as the Database Name. Click OK to create the new web application with the default web site extened in WSS 3.0.

Attach the content database to the new web application

Delete the temporary content database using the command:

stsadm –o deletecontentdb –url http://<AppTierName> –databasename WSS_Content_Temp

To attach the WSS_Content database to the default web site, open a command prompt window & change to the folder %Program Files%\Common Files\Microsoft Shared\web server extensions\12\BIN. Run the following command:
stsadm –o addcontentdb –url http://<AppTierName> –databasename WSS_Content

Install TFS 2008 Extensions for WSS

Install TFS 2008 extensions for WSS 3.0 from <TFS Installation Location>\wssext folder by running the setup.exe. At the end of installation, after you have clicked Finish, you would be prompted with the dialog box for the WSS 3.0 web part configuration. Provide the http://ATName/sites as the WSS site, http://ATName/Reports as the reports site & http://ATName/ReportServer for the reporting services administrative site & click Apply. Click Exit.

Connect to Team Foundation Server using Team Explorer & verify connectivity.

TFS 2008 & Scripting the WSS 3.0 Configuration

For any body who wants to script the Products & Technologies Wizard & the extending of default web site in IIS with WSS 3.0 the below script would be the answer.

Thanks Siva for the being the inspiration behind this. :)

Copy the below script in a text file & save it with a .bat extension. Run the .bat in a command prompt window to complete the operation. The PCW log would be created at the path c:\PCWPrimary.txt.

 ====================================================================

@echo off

Rem Set ServerName to the SQL Server Instance
Set ServerName=SQLBOXNAME

Rem Do not Change this
Set ConfigDBName=WSS_Config

Rem Set SetupAccount to the TFS Setup Account
Set SetupAccount=Domain\TFSSetup

Rem Set Serviceaccount to the TFS Service Account
Set ServiceAccount=Domain\TFSService

Rem Set ServicePassword to the password of the TFSService Account
Set ServicePassword=P@ssw0rd

Rem Do not change this
Set AdminDBName=WSS_AdminContent

Rem Set WSSDIRPATH to the bin folder in the install location of WSS 3.0
Set WSSDIRPATH="C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN"

Rem Set WSS Admin's email
Set AdminEmail=user@domain.com

Rem Do not Change this
Set ContentDBName=WSS_Content

 

@echo on

@Echo  ---- Dumping the PCW log at c:\PCWPrimary.txt ----

@echo off

Pause

CLS

cd %WSSDIRPATH%

Cls

@echo on

Rem Run Psconfig to create config & admincontent dbs & to provision the Central Admin Site

psconfig -cmd configdb -create -server %ServerName% -database %ConfigDBName% -user %ServiceAccount% -password %ServicePassword% -admincontentdatabase %AdminDBName% -cmd helpcollections -installall -cmd secureresources -cmd installfeatures -cmd adminvs -provision -port 17012 -windowsauthprovider onlyusentlm -cmd applicationcontent -install > "c:\PCWPrimary.txt"

 

Rem Extend the default web site

STSADM.EXE -o extendvs -url http://%ServerName%:80 -ownerlogin %SetupAccount% -owneremail %AdminEmail% -exclusivelyusentlm -databaseserver  %ServerName% -databasename %ContentDBName% -donotcreatesite -description "Default Web Site"

IISReset

Rem Create the root site collection

stsadm -o createsite -url http://%ServerName% -ownerlogin %SetupAccount% -owneremail %AdminEmail% -sitetemplate STS

@echo All Operations completed succesfully..

@echo Please check C:\PCWPrimary.txt for details..

 

================================================================================

Team Foundation Server 2005 & Windows Sharepoint Service 3.0: How to failover to a Mirrored Data-Tier Server

NOTE- PLEASE GO THROUGH THE COMPLETE ARTICLE FIRST before you start working on it

 

This post discusses the steps required to be performed when you failover to a mirrored data-tier server.

 

This post is specific to TFS 2005 that has been configured to work with Windows Sharepoint Services 3.0

 

Please use the following instructions to configure TFS 2005 with WSS 3.0:

http://msdn.microsoft.com/en-us/vsts2008/bb676233.aspx

 

 

How to: Fail Over to a Mirrored Data-Tier Server:

 

Stop the Report Server

 

-          To stop the Report Server, click Server Status, and then click Stop.

To stop and configure the Web Sites

1.     On the Team Foundation application-tier server, click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

2.     Expand the computer node, expand the Web Sites node, select the Default Web Site, and then click Stop.

3.     On the Team Foundation application-tier server, click Start, click Administrative Tools, and then click Windows SharePoint Central Administration.

4.     Click Application Management, click Content databases, click the name of the content database, select Remove content database, and then click OK.

To stop the remaining services used by Team Foundation Server

1.     On the Team Foundation application-tier server, click Start, click Administrative Tools, and then click Services.

2.     In Services Manager, locate the following services, right-click the service, and then click Stop:

• SharePoint Timer Service
• TfsServerScheduler Service

Note

To open Services Manager, click Start, click Administrative Tools, and then click Services.

 

3.     On the Team Foundation application-tier server, click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

4.     Expand the Application Pools node, locate and right-click the application pools, and then click Stop for the following application pools:

• ReportServer
• TFS AppPool

Add Service Accounts to the Mirroring Team Foundation Data-Tier Server

After stopping the services, you must add the Team Foundation service account and the SQL Server Reporting Services service account to the mirroring Team Foundation data-tier server.

To add the service accounts to the mirroring Team Foundation data-tier server

1.    On the mirroring Team Foundation data-tier server, click Start, click All Programs, click Microsoft SQL Server, and then click SQL Server Management Studio.

2.    Select Database Engine for the Server type. Select the appropriate Server name and Authentication scheme for the server. Provide a valid User name and Password if it is required by your SQL Server, and then click Connect.

3.    In SQL Server Management Studio, click File, click New, and then click Query with Current Connection.

A new query window opens.

4.    In the new query, type the following, where domain is the name of the domain to which your service accounts belong, TFSService is the name of the Team Foundation service account, and TFSReports is the name of the SQL Server Reporting Services service account:

CREATE LOGIN [ domain / TFSService ] FROM WINDOWS;

CREATE LOGIN [ domain / TFSReports ] FROM WINDOWS;

GO

5.    On the SQL Server Management Studio toolbar, click Execute. Verify that the command executed correctly, and then close SQL Server Management Studio.

Note

If either the TFSService service account, the TFSReports service account, or both service accounts already exist on the mirroring Team Foundation data-tier server, you will see an error that indicates that these accounts already exist. You can safely ignore this error message and continue with the next procedure.

Manually Swap the Roles of the Principal and Mirroring Databases

After you have added the TFSService and TFSReports service accounts to the mirroring Team Foundation data-tier server, you can manually fail over the Team Foundation databases so that the principal Team Foundation data-tier server becomes the mirroring server, and the mirroring Team Foundation data-tier server becomes the principal Team Foundation data-tier server. For more information about manually failing over databases in SQL Server Management Studio, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=76086).

To open SQL Server Management Studio on the principal Team Foundation data-tier server

1.     On the principal Team Foundation data-tier server, click Start, click All Programs, click Microsoft SQL Server, and then click SQL Server Management Studio.

2.     Select Database Engine for the Server type. Select the appropriate Server name and Authentication scheme for the server. Provide a valid User name and Password if it is required by your SQL Server, and then click Connect.

3.     Expand the Databases node to show the list of databases that make up the Team Foundation data tier.

Complete the "To fail over each database" procedure for the following databases:

• ReportServer
• ReportServerTempDB
• WSS_Config
• WSS_Content
• WSS_AdminContent
• TfsBuild
• TfsIntegration
• TfsVersionControl
• TfsWarehouse
• TfsWorkItemTracking
• TfsWorkItemTrackingAttachments
• TfsActivityLogging

To fail over each database

1.     Right-click the database that you want to fail over, and then click Properties.

2.     On the Database Properties page, in Select a page, click Mirroring.

3.     Click Failover.

Note

If the Failover button is not active, you have not configured the database for mirroring. For more information, see How to: Configure SQL Server Mirroring for the Team Foundation Data-Tier Server.

Map the Team Foundation Application-Tier Server to the New Principal Team Foundation Data-Tier Server

After you have failed over all the Team Foundation databases, the mirroring Team Foundation data-tier server becomes the principal Team Foundation data-tier server for the deployment. To complete the fail-over, you must redirect the Team Foundation application-tier server to that server.

Build the Data Warehouse

After swapping the databases and mapping app tier to new principal data tier, you must build the data warehouse.

To build the data warehouse

1.     Start TFS Application Pool if stopped.

2.     On the Team Foundation application-tier server, click Start, click All Programs, click Accessories, and then click Command Prompt - The Command Prompt window opens.

3.     Open the Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools folder using the command line. For example:

cd C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools

4.     Open a Command Prompt window and build the data warehouse by typing the following command, where newDataTierServerName is the name of the mirrored Team Foundation data-tier server that you have failed over to, TFSReportServiceAccount is the name of the reporting services service account, and TFSServiceAccount is the name of the Team Foundation Server service account:

setupwarehouse -o -s newDataTierServerName -d TfsWarehouse -c warehouseschema.xml -ra TFSReportAccount -a TFSServiceAccount –v –mturl http://tfsappserver:8080

5.     On the Team Foundation data-tier server, click Start, click All Programs, click Microsoft SQL Server, and then click SQL Server Management Studio.

6.     Select Analysis Server for the Server type. Select the appropriate Server name and Authentication scheme for the server. Provide a valid User name and Password if it is required by your SQL Server, and then click Connect.

7.     Expand the Databases node to see the list of databases that make up the Team Foundation Server data tier.

8.     Right-click the TFSWarehouse and then click Process.

9.     In the Process Database dialog box, click OK to process the warehouse.

10.  Configure Reporting Service Configuration

a.     Click Connect

b.    Go to Database Setup, give the new Server name (the mirrored server) & click Connect & OK.  You will see one error/warning at the last in the result list

c.     Restore the Encryption Key from backup

d.    Go to Database Setup, give the new Server name (the mirrored server) & click Connect & OK to make sure every result is green.

e.     Check Event Viewer ->Application Logs to verify that RS initialized without errors.

11.  On the Team Foundation application-tier server, open Internet Explorer and in the address bar, type http://applicationTierServerName/reports.

12.  On the SQL Server Reporting Services home page, click TfsOlapReportDS.

a.     Verify that the correct connection information appears in Connection String.

The string should include the name of the mirrored Team Foundation data-tier server that you have failed over to, and the initial catalog should be TfsWarehouse.

Data source= newDataTierServerName ;initial catalog=TfsWarehouse

b.    Select Credential stored securely in the report server.

c.     Enter the domain, account name, and password for the Reporting Services service account specified for Reporting Services.

d.    Select Use as windows credentials when connecting to the data source.

13.  On the SQL Server Reporting Services home page, click TfsReportDS.

a.     Make sure Connection String contains the mirrored Team Foundation data-tier server that you have failed over to.

Data source= newDataTierServerName ;initial catalog=TfsWarehouse

b.    Select Credential stored securely in the report server.

c.     Enter domain, account name, and password for the TFSREPORTS service.

d.    Select Use as windows credentials when connecting to the data source.

To redirect the Team Foundation application-tier server and restart services

1.     On the Team Foundation application-tier server, click Start, click All Programs, click Accessories, and then click Command Prompt.

The Command Prompt window opens.

2.     Open the Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools folder using the command line. For example:

cd C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools

3.     Run the TFSAdminUtil tool with the RenameDT option to connect to the Team Foundation data-tier server that is now acting as the principal server (the server that was the mirroring server). For example:

TFSAdminUtil RenameDT MirrorDataTierServer

In this example, MirrorDataTierServer represkents the name of the Team Foundation data-tier server to which you want to connect.

If failed, then manually replace MirrorDataTierserver with OldDataTierServer in “C:\Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services\web.config” file.

Also, manually change the value to new principal DB name in database table in TfsIntegration DB

4.     Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

5.     In the Explorer pane, right-click the name of the application-tier server, click All Tasks, and then click Restart IIS.

6.     In Stop/Start/Reset, verify that you are restarting services on the correct server, and then click OK. Wait for the services to stop and restart, and then close IIS Manager.

SharePoint Configuration

1.     On the Team Foundation application-tier server, click Start, click Programs, click Administrative Tools, and then click SharePoint Central Administration.

2.     Select Set configuration database server, type the name of the mirrored Team Foundation data-tier server that you have failed over to in the Database server field, select the Connect to existing configuration database, and then click OK.

3.     Select Set default content database server, type the name of the mirrored Team       Foundation data-tier server that you have failed over to, and then click OK.

4.     On the Team Foundation application-tier server, click Start, click Administrative Tools,         click Services, select SharePoint Timer Service, and then click Start.

5.     Open the command line interface and run following command.

·         C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN>stsadm.exe -o renameserver -oldservername XXXX -newservername XXXX

 

6.     Restart IIS by running “iisreset” at the command line interface

7.     You would have to add the WSS_Content DB as the content database of the defualt web site.

a.     Click Start, click Administrative Tools, and then click SharePoint Central Administration.

b.    On the Central Administration page, click Application Management.

c.     On the Application Management tab, click Content databases.

d.    On the Manage Content Databases page, click Add a content database.

e.     On the Add Content Database page, in Database Information, click Specify database server settings and in Database name, type WSS_Content.

f.     In Database Capacity Settings, in Number of sites before a warning event is generated, type 9000, and in Maximum number of sites that can be created in this database, type 15000, then click OK.

8.     Open Internet Explorer and type the server name as the address to verify that the SharePoint portal site appears.  Ex) http://tfsappserver/sites/ProjectName

9.     Start TFS Application Pool in IIS

10.  Go to  ClientService Web service as follows.

http:// applicationTierServerName :8080/WorkItemTracking/v1.0/ClientService.asmx

11.  Select the StampWorkitemCache Web method and then click Invoke.

12.  Clear TF Client Cache before open TF Client

Delete all directories in “C:\Documents and Settings\tcs_tfssetup\Local Settings\Application Data\Microsoft\Team Foundation\2.0”

 

 

 

TFS 2005: How to fail over to a Mirrored Data-Tier Server with Windows Sharepoint Service 2.0

 

 

I have reveiwed the TFS 2005 failover document, with TFS 2005 working with WSS 2.0, & have made the required corrections. The scenario is documented at:

http://msdn2.microsoft.com/en-us/library/aa980627(VS.80).aspx.

 

Please ensure that you follow the instructions in sequence suggested here.

 

====================================================================================================

 

If you have configured SQL Server mirroring for the Team Foundation databases, you can manually swap the roles of the principal and mirrored Team Foundation data-tier servers in case the principal Team Foundation data-tier server must be taken off-line. This can help minimize disruption of your Team Foundation Server deployment. For more information about Team Foundation Server and SQL Server Mirroring, see Mirroring the Team Foundation Data-Tier Server.

Note

The following procedures are for use if the principal data-tier server is available. If the principal data-tier server is unavailable, follow the procedures in How to: Fail Over to a Mirrored Data-Tier Server if the Principal Data-Tier Server is Unavailable.

Required Permissions

To perform these procedures, you must be a member of the Administrators group and a member of the SQL Server Administrator group on the principal and mirroring Team Foundation data-tier servers. For more information, see Team Foundation Server Permissions.

Prepare and Stop the Team Foundation Application-Tier Services

Before you fail over the Team Foundation data-tier server, you must stop the services from using the principal Team Foundation data-tier server and prepare the Team Foundation application-tier server to use the mirroring Team Foundation data-tier server.

To re-configure and stop the Report Server

1.    On the Team Foundation application-tier server, open the Reporting Services Configuration tool and connect to the Report Server instance.

To open the Reporting Services Configuration tool, click Start, click All Programs, click Microsoft SQL Server 2005, click Configuration Tools, and then click Reporting Services Configuration.

2.    In the Explorer pane, click Database Setup, type the new database server name in Server Name, and then click New.

3.    In the SQL Server Connection dialog box, type ReportServer in Database Name, click OK, and then click Apply.

Note

If the Team Foundation data-tier server is offline, applying the connection might take several minutes.

4.    In the Explorer pane, click Windows Service Identity.

5.    On the Windows Service Identity page, in the Built-in Service Account drop-down box, Network Service should be selected, but Apply is unavailable. To grant the Team Foundation application-tier server log on permissions to the SQL Server on the Team Foundation data-tier, in the Built-in Service drop-down box, select Local Service. Do not click Apply, but instead return to the Built-in Service drop-down box and re-select Network Service. When Network Service is selected and Apply is available, click Apply.

Steps 1-5 will cause the following error, Only Step 6 should be done:

“The database ReportServer exists on the SQL server. You must choose a different database or install Reporting Services into existing databases.”

 

6.    To stop the Report Server, click Server Status, and then click Stop.

To stop and configure the Web Sites

1.    On the Team Foundation application-tier server, click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

2.    Expand the computer node, expand the Web Sites node, select the Default Web Site, and then click Stop.

3.    On the Team Foundation application-tier server, click Start, click Administrative Tools, and then click Windows SharePoint Central Administration.

4.    Click Configure virtual server settings, click Default Web Site, click Manage content databases, click the name of the content database, select Remove content database, and then click OK.

5.    On the SharePoint Central Administration page, click Configure virtual server settings, click Default Web Site, click Remove Windows SharePoint Services from virtual server, click Remove without deleting content databases, and then click OK.

To stop the remaining services used by Team Foundation Server

1.    On the Team Foundation application-tier server, click Start, click Administrative Tools, and then click Services.

2.    In Services Manager, locate the following services, right-click the service, and then click Stop:

·         SharePoint Timer Service

·         TfsServerScheduler Service

Note

To open Services Manager, click Start, click Administrative Tools, and then click Services.

3.    On the Team Foundation application-tier server, click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

4.    Expand the Application Pools node, locate and right-click the application pools, and then click Stop for the following application pools:

·         ReportServer

·         TFS AppPool

Add Service Accounts to the Mirroring Team Foundation Data-Tier Server

After stopping the services, you must add the Team Foundation service account and the SQL Server Reporting Services service account to the mirroring Team Foundation data-tier server.

To add the service accounts to the mirroring Team Foundation data-tier server

1.    On the mirroring Team Foundation data-tier server, click Start, click All Programs, click Microsoft SQL Server, and then click SQL Server Management Studio.

2.    Select Database Engine for the Server type. Select the appropriate Server name and Authentication scheme for the server. Provide a valid User name and Password if it is required by your SQL Server, and then click Connect.

3.    In SQL Server Management Studio, click File, click New, and then click Query with Current Connection.

A new query window opens.

4.    In the new query, type the following, where domain is the name of the domain to which your service accounts belong, TFSService is the name of the Team Foundation service account, and TFSReports is the name of the SQL Server Reporting Services service account:

CREATE LOGIN [ domain / TFSService ] FROM WINDOWS;

CREATE LOGIN [ domain / TFSReports ] FROM WINDOWS;

GO

5.    On the SQL Server Management Studio toolbar, click Execute. Verify that the command executed correctly, and then close SQL Server Management Studio.

Note

If either the TFSService service account, the TFSReports service account, or both service accounts already exist on the mirroring Team Foundation data-tier server, you will see an error that indicates that these accounts already exist. You can safely ignore this error message and continue with the next procedure.

Manually Swap the Roles of the Principal and Mirroring Databases

After you have added the TFSService and TFSReports service accounts to the mirroring Team Foundation data-tier server, you can manually fail over the Team Foundation databases so that the principal Team Foundation data-tier server becomes the mirroring server, and the mirroring Team Foundation data-tier server becomes the principal Team Foundation data-tier server. For more information about manually failing over databases in SQL Server Management Studio, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=76086).

To open SQL Server Management Studio on the principal Team Foundation data-tier server

1.    On the principal Team Foundation data-tier server, click Start, click All Programs, click Microsoft SQL Server, and then click SQL Server Management Studio.

2.    Select Database Engine for the Server type. Select the appropriate Server name and Authentication scheme for the server. Provide a valid User name and Password if it is required by your SQL Server, and then click Connect.

3.    Expand the Databases node to show the list of databases that make up the Team Foundation data tier.

Complete the "To fail over each database" procedure for the following databases:

·      ReportServer

·      ReportServerTempDB

·      STS_Config_TFS

·      STS_Content_TFS

·      TfsBuild

·      TfsIntegration

·      TfsVersionControl

·      TfsWarehouse

·      TfsWorkItemTracking

·      TfsWorkItemTrackingAttachments

·      TfsActivityLogging

To fail over each database

1.    Right-click the database that you want to fail over, and then click Properties.

2.    On the Database Properties page, in Select a page, click Mirroring.

3.    Click Failover.

Note

If the Failover button is not active, you have not configured the database for mirroring. For more information, see How to: Configure SQL Server Mirroring for the Team Foundation Data-Tier Server.

Build the Data Warehouse(These steps have to be done after - Map the Team Foundation Application-Tier Server to the New Principal Team Foundation Data-Tier Server)

After swapping the databases, you must build the data warehouse.

To build the data warehouse

1.    On the Team Foundation application-tier server, click Start, click All Programs, click Accessories, and then click Command Prompt.

The Command Prompt window opens.

2.    Open the Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools folder using the command line. For example:

cd C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools

3.    Open a Command Prompt window and build the data warehouse by typing the following command, where newDataTierServerName is the name of the mirrored Team Foundation data-tier server that you have failed over to, TFSReportServiceAccount is the name of the reporting services service account, and TFSServiceAccount is the name of the Team Foundation Server service account:

setupwarehouse -o -s newDataTierServerName -d TfsWarehouse -c warehouseschema.xml -ra TFSReportAccount -a TFSServiceAccount -v

4.    On the Team Foundation data-tier server, click Start, click All Programs, click Microsoft SQL Server, and then click SQL Server Management Studio.

5.    Select Analysis Server for the Server type. Select the appropriate Server name and Authentication scheme for the server. Provide a valid User name and Password if it is required by your SQL Server, and then click Connect.

6.    Expand the Databases node to see the list of databases that make up the Team Foundation Server data tier.

7.    Right-click the TFSWarehouse and then click Process.

8.  In the Process Database dialog box, click OK to process the warehouse.

 

These steps have the potential of failing as TFSApp pool is stopped. So setupwarehouse will fail saying mturl parameter is required. A standard fix to that is to start the TFSApp pool, but this wont work at this stage because the AT is bound to the original principal server & we have not used the TFSAdminutil RenameDT yet… So the web.config is having an incorrect data source at this stage..

This statement should be used after the Map the Team Foundation Application-Tier Server to the New Principal Team Foundation Data-Tier Server step.

 

 

Map the Team Foundation Application-Tier Server to the New Principal Team Foundation Data-Tier Server

After you have failed over all the Team Foundation databases, the mirroring Team Foundation data-tier server becomes the principal Team Foundation data-tier server for the deployment. To complete the fail-over, you must redirect the Team Foundation application-tier server to that server.

To redirect the Team Foundation application-tier server and restart services

1.    On the Team Foundation application-tier server, click Start, click All Programs, click Accessories, and then click Command Prompt.

The Command Prompt window opens.

2.    Open the Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools folder using the command line. For example:

cd C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools

3.    Run the TFSAdminUtil tool with the RenameDT option to connect to the Team Foundation data-tier server that is now acting as the principal server (the server that was the mirroring server). For example:

TFSAdminUtil RenameDT MirrorDataTierServer

In this example, MirrorDataTierServer represkents the name of the Team Foundation data-tier server to which you want to connect.

4.    Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

5.    In the Explorer pane, right-click the name of the application-tier server, click All Tasks, and then click Restart IIS.

6.    In Stop/Start/Reset, verify that you are restarting services on the correct server, and then click OK. Wait for the services to stop and restart, and then close IIS Manager.

This is the time when” To build the data warehouse” will work & should be done. If the mturl missing error comes then one can start the TFSApp pool.

Also one would have to reprocess the TFSWarehouse DB in SSAS. Other wise reports will end up with error “The Team system cube either does not exist or has not been processed”. To process the ware house cube on the Mirrorred server..

a)   In the Object Explorer pane, click Connect, and select Analysis Services.

b)   On the Connect to Server dialog box, make sure that the server name and authentication values are correct, and then click Connect.

c)   In the Object Explorer pane, expand Databases, right-click TFSWarehouse, and then click Process.

d)   In Process Database - TFSWarehouse, click OK.

AT this time the Report Server app pool needs to be started & the default web site should be started(I feel the default web site should not have been stopped at all…). The reason I say this is we can’t browse

http://applTierName/Reports when the default web site is stopped & ReportServer application pool is stopped. An attempt to open Report Manager will give “Page Not Found”…

Starting just the ReportServer app pool wont also help..

Staring Just the Default Web Site wont also help…

 

Start both the ReportServer app pool & the Default Web Site..

Note that it this stage the Report Server Instance(in RSConfig) is already stopped… Therefore you will get the following error while browsing the Reports Manager site(http://AppTierName/Reports):

“The report server is not responding. Verify that the report server is running & can be accessed from this computer.”

 

 

Therefore use the RSConfig tool to:

a.    Start the RSServer instance

b.    Restore the encryption key backp

c.    Go to Database Setup, give the new Server name(the mirrored server) & click Connect & OK.

d.    Click Apply & Ok.

e.    Check Event Viewer ->Application Logs to verify that RS initialized without errors.

Proceed with the below steps..

 

7.    On the Team Foundation application-tier server, open Internet Explorer and in the address bar, type http://applicationTierServerName/reports.

8.    On the SQL Server Reporting Services home page, click TfsOlapReportDS.

a.     Verify that the correct connection information appears in Connection String.

The string should include the name of the mirrored Team Foundation data-tier server that you have failed over to, and the initial catalog should be TfsWarehouse.

Data source= newDataTierServerName ;initial catalog=TfsWarehouse

b.     Select Credential stored securely in the report server.

c.     Enter the domain, account name, and password for the Reporting Services service account specified for Reporting Services.

d.     Select Use as windows credentials when connecting to the data source.

9.    On the SQL Server Reporting Services home page, click TfsReportDS.

a.     Make sure Connection String contains the mirrored Team Foundation data-tier server that you have failed over to.

Data source= newDataTierServerName ;initial catalog=TfsWarehouse

b.     Select Credential stored securely in the report server.

c.     Enter domain, account name, and password for the TFSREPORTS service.

10.  Select Use as windows credentials when connecting to the data source.

11.  On the Team Foundation application-tier server, click Start, click Programs, click Administrative Tools, and then click SharePoint Central Administration.

12.  Select Set configuration database server, type the name of the mirrored Team Foundation data-tier server that you have failed over to in the Database server field, select the Connect to existing configuration database, and then click OK.

13.  Select Set default content database server, type the name of the mirrored Team Foundation data-tier server that you have failed over to, and then click OK.

14.  In SharePoint Central Administration, select Extend or upgrade virtual server, click Default Web Site, click Extend and map to another virtual server.

15.  Select Default Web Site in the Server Mapping list, select the Use an existing application pool option, and then click OK.

You would have to add the STS_Content_TFS DB as the content database of the defualt web site.

a)  Click Start, click Administrative Tools, and then click SharePoint Central Administration.

b)  On the Central Administration page, click Configure virtual server settings.

c)   On the Virtual Server List page, click Default Web Site.

d)  On the Virtual Server Settings page, click Manage content databases.

e)  On the Manage Content Databases page, click Add a content database.

f)    On the Add Content Database page, in Database Information, click Specify database server settings and in Database name, type STS_Content_TFS.

g)  In Database Capacity Settings, in Number of sites before a warning event is generated, type 9000, and in Maximum number of sites that can be created in this database, type 15000, then click OK.

16.  On the Team Foundation application-tier server, click Start, click Administrative Tools, click Services, select SharePoint Timer Service, and then click Start.

17.  Open Internet Explorer and type the server name as the address to verify that the SharePoint portal site appears.

18.  On the Team Foundation application-tier server, open Internet Information Services (IIS) Manager. To open Internet Information Services (IIS) Manager, click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

19.  Expand the Application Pools node, locate and right-click the application pools, and then click Start for the following application pools:

·         ReportServer

·         TFS AppPool

20. Open the Reporting Services Configuration tool, click Server Status, and then click Start.

21.  On the Team Foundation application-tier server, open Internet Explorer.

22.  In the address bar, type the following address to connect to the ClientService Web service.

http:// applicationTierServerName :8080/WorkItemTracking/v1.0/ClientService.asmx

23.  Select the StampWorkitemCache Web method and then click Invoke.

 

TFS 2005: How to do data tier only move

How to: Move Your Data Tier to another computer

Note: To complete these procedures successfully the old TFS AT & new TFS DT should have TFS 2005 SP1 applied to them.  This instruction set assumes that TFS 2005 is working with version 2.0 of WSS (Windows SharePoint Service).

 

Required Permissions

To complete these procedures, you must be a member of the Administrators group on the old and new Data Tier and a member of the Team Foundation Administrators group.

Prepare For a Data Tier Move

Before you can move your Data Tier Server, you must back up the Team Foundation Server databases.

For more information about how to back up Team Foundation Server, see How to: Back Up a Team Foundation Server.

Add the service accounts to the new Team Foundation data-tier server

1.    On the new Team Foundation data-tier server, click Start, click All Programs, click Microsoft SQL Server, and then click SQL Server Management Studio.

2.    Select Database Engine for the Server type. Select the appropriate Server name and Authentication scheme for the server. Provide a valid User name and Password if it is required by your SQL Server, and then click Connect.

3.    In SQL Server Management Studio, click File, click New, and then click Query with Current Connection.

A new query window opens.

4.    In the new query, type the following, where domain is the name of the domain to which your service accounts belong, TFSService is the name of the Team Foundation service account, and TFSReports is the name of the SQL Server Reporting Services service account:

CREATE LOGIN [ domain / TFSService ] FROM WINDOWS;

CREATE LOGIN [ domain / TFSReports ] FROM WINDOWS;

GO

5.    On the SQL Server Management Studio toolbar, click Execute. Verify that the command executed correctly, and then close SQL Server Management Studio.

6.    Grant the dbcreator & securityadmin fixed server roles to the TFSService Account.

7.    In Team Foundation Data Tier machine, launch SQL Server Management Studio, click File, click New, and then click Query with Current Connection.  A new query window opens.

8.     In the new query, type the following,

use master

exec sp_addsrvrolemember N'Domain\TFSServiceAccount', 'dbcreator'

exec sp_addsrvrolemember 'Domain\TFSServiceAccount', 'securityadmin'
GO

9.    On the SQL Server Management Studio toolbar, click Execute. Verify that the command executed correctly, and then close SQL Server Management Studio.

 

Install Team Foundation Server on the New Hardware

After backing up your Team Foundation Server data, you must install Team Foundation Server Data Tier on the computer to which you want to move the Data Tier to. Apply kb919156 hotfix (http://www.microsoft.com/downloads/details.aspx?FamilyID=c18c756e-8f80-4987-b3bf-600068a9e3c4&displaylang=en) & TFS 2005 Service Pack1 (http://www.microsoft.com/downloads/details.aspx?FamilyId=A9AB638C-04D2-4AEE-8AE8-9F00DD454AB8&displaylang=en).

 

Prepare the Team Foundation Server Application Tier for the Data Tier move

1.    Click Start, click Administrative Tools, click Services, select the TFSServerScheduler service, and then click Stop if the service is not already stopped.

2.    Select the SharePoint Timer Service, and then click Stop.

3.    Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

4.    In the Explorer pane, expand the Application Pools node, right-click TFS App Pool, and then click Stop.

5.    In the Explorer pane, under the Application Pools node, right-click Report Server, and then click Stop.

6.    Click Start, click Programs, click Microsoft SQL Server 2005, click Configuration Tools, and then click Reporting Services Configuration.

7.    In Report Server Installation Instance Selection, make sure that the computer name is the name of the Team Foundation application-tier server and that the instance name is MSSQLSERVER, and then click Connect.

8.    In the Explorer pane, click Server Status.

9.    In the Report Server Status pane, in Instance Properties, click Stop.

 

Restore Team Foundation Server databases from the backups taken from the old box

You can restore the Team Foundation Server data using the restore tools provided with SQL Server 2005.

To open the Restore Database dialog box

1.    On the new Team Foundation data-tier server, click Start, click All Programs, click Microsoft SQL Server, and then click SQL Server Management Studio.

Note

For more information about how to restore databases, see Implementing Restore Scenarios for SQL Server Databases.

2.    Select Database Engine for the Server type.

3.    Select the appropriate Server name and Authentication scheme for the server, provide a valid User name and Password if it is required by your SQL Server, and then click Connect.

4.    Expand the Databases node to show the list of databases that make up the Team Foundation Server data tier.

 

Complete the "To restore each database" procedure for each of the following databases:

·         ReportServer

·         ReportServerTempDB

·         STS_Config_TFS

·         STS_Content_TFS

·         TfsBuild

·         TfsIntegration

·         TfsVersionControl

·         TfsWarehouse

·         TfsWorkItemTracking

·         TfsWorkItemTrackingAttachments

·         TfsActivityLogging

 

To restore each database

1.    Right-click the database you want to restore, point to Tasks, point to Restore, and then click Database.

2.    In the Restore Database dialog box, select From Device in the Source for restore area, and then click the ellipsis button (…).

3.    In the Specify Backup dialog box, fill out the information to specify the location of the backup file, and then click OK.

The first backup you apply must be a full backup, followed by the transaction log backups, in the order they were created.

4.    In the Select the backup sets to restore area, select the backup sets to restore.

5.    From the left navigation pane, select Options, and then select the Overwrite the existing database box.

6.    Verify that the paths specified in the Restore the database files as area match your current database paths.

This is important if you are restoring the database to a different drive.

7.    Select the appropriate state from the Recovery state area.

8.    Perform one of the following steps:

If you are not applying additional transaction logs, select Leave the database ready to use.

- or -

If you are applying additional transaction logs, select Leave the database non-operational.

9.    Click OK to dismiss the Restore Database dialog box and restore the database.

10.  If you are applying additional transaction logs, follow this procedure for each log backup in the order they were created starting from the one made after the full backup.

For more information, see Applying Transaction Log Backups.

 

Rename the Team Foundation Data-Tier Server

After restoring the Team Foundation Server databases you can use the TfsAdminUtil command-line tool to rename the data tier.

On TFS Application Tier, from the Command Prompt window, change directories to drive:\%ProgramFiles%\Microsoft Visual Studio 2005 Team Foundation Server\Tools and type the following command:

TfsAdminUtil RenameDT newTeamFoundationDataTierServerName

 

Configure Reporting Services on the Application Tier

1.     Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

2.     In the Explorer pane, under the Application Pools node, right-click Report Server, and then click Start.

3.     Click Start, click Programs, click Microsoft SQL Server 2005, click Configuration Tools, and then click Reporting Services Configuration.

4.     In Report Server Installation Instance Selection, give the computer name is the name of the Team Foundation application-tier server and ensure that the instance name is MSSQLSERVER, and then click Connect.

5.     In the Explorer pane, click Server Status.

6.     In the Report Server Status pane, in Instance Properties, click Start.

7.     In the Explorer pane, click Database Setup.

8.     In the Database Connection pane, make sure that the name of the Team Foundation data-tier server is the new Data Tier Server Name, and then click Connect.

9.     On the SQL Server Connection Dialog dialog box, click OK.

10.  In the Database Connection pane, click Apply.

11.  On the SQL Server Connection Dialog dialog box, click OK.

12.  In the Explorer pane, click Windows Service Identity. On the Windows Service Identity page, in the Built-in Service Account box, Network Service should be selected, but Apply is unavailable. To grant the Team Foundation application-tier server log on permissions to the SQL Server on the Team Foundation data-tier, in the Built-in Service box, select Local Service. Do not click Apply, but instead return to the Built-in Service box and re-select Network Service. When Network Service is selected and Apply is available, click Apply. In the SQL Server Connection Dialog dialog box, and then click OK.

1.    On the Team Foundation application-tier server, open Internet Explorer and in the address bar, type http://applicationTierServerName/reports.

2.    On the SQL Server Reporting Services home page, click TfsOlapReportDS.

a.     Verify that the correct connection information appears in Connection String.

The string should include the name of the new Team Foundation data-tier server, and the initial catalog should be TfsWarehouse.

Data source= newDataTierServerName ;initial catalog=TfsWarehouse

b.    Select Credential stored securely in the report server.

c.     Enter the domain, account name, and password for the Reporting Services service.

d.    Select Use as windows credentials when connecting to the data source.

3.    On the SQL Server Reporting Services home page, click TfsReportDS.

a.     Make sure Connection String contains the new Team Foundation data-tier server.

Data source= newDataTierServerName; Initial Catalog=TfsWarehouse

b.    Select Credential stored securely in the report server.

c.     Enter domain, account name, and password for the TFSREPORTS service.

d.    Select Use as windows credentials when connecting to the data source.

 

Build the Data Warehouse

To build the data warehouse

1.    On the Team Foundation application-tier server, click Start, click All Programs, click Accessories, and then click Command Prompt.

The Command Prompt window opens.

2.    Open the Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools folder using the command line. For example:

cd C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools                

3.    Open a Command Prompt window and build the data warehouse by typing the following command, where newDataTierServerName is the name of the new Team Foundation data-tier server, TFSReportServiceAccount is the name of the reporting services service account, and TFSServiceAccount is the name of the Team Foundation Server service account:

setupwarehouse -o -s newDataTierServerName -d TfsWarehouse -c warehouseschema.xml -ra TFSReportAccount -a TFSServiceAccount -v

Note: In case you receive an error while executing the above command that –mturl parameter is required, start the TFSApp application pool in IIS & run the above command as:
setupwarehouse -o -s newDataTierServerName -d TfsWarehouse -c warehouseschema.xml -ra TFSReportAccount -a TFSServiceAccount –mturl http://application-tiername:8080

4.    On the Team Foundation data-tier server, click Start, click All Programs, click Microsoft SQL Server, and then click SQL Server Management Studio.

5.    Select Analysis Server for the Server type. Select the appropriate Server name and Authentication scheme for the server. Provide a valid User name and Password if it is required by your SQL Server, and then click Connect.

6.    Expand the Databases node to see the list of databases that make up the Team Foundation Server data tier.

7.    Right-click the TFSWarehouse and then click Process.

8.    In the Process Database dialog box, click OK to process the warehouse.

 

 

Configure Windows SharePoint Services 2.0 on the Application Tier

1. On the Team Foundation application-tier server, click Start, click Programs, click Administrative Tools, and then click SharePoint Central Administration.

2.    Select Set configuration database server, type the name of the new Team Foundation data-tier server in the Database server field, select the Connect to existing configuration database, and then click OK.

3.    Select Set default content database server, type the name of the new Team Foundation data-tier server and then click OK.

4.     On the Central Administration page, click Configure virtual server settings.

5.     On the Virtual Server List page, click Default Web Site.

6.     On the Virtual Server Settings page, click Manage content databases.

7.     On the Manage Content Databases page, click STS_Content_TFS.

8.     On the Manage Content Database Settings page, select Remove content database, and then click OK.

9.     On the Manage Content Databases page, click Add a content database.

10.  On the Add Content Database page, in Database Information, click Specify database server settings and in Database name, type STS_Content_TFS.

11.  In Database Capacity Settings, in Number of sites before a warning event is generated, type 9000, and in Maximum number of sites that can be created in this database, type 15000, then click OK.

12.  (Optional) If you backed up any Windows SharePoint Services custom site definitions, custom site templates, or custom Web parts and you want to keep your customizations, restore these components now.

For more information, see the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=63543).

13.  Click Start, click Administrative Tools, click Services, select the SharePoint Timer Service, then click Start.

 

Start the Team Foundation Services & Verify operation

1.     On the Team Foundation application-tier server, click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

2.     In the Explorer pane, expand the Application Pools node, right-click TFS App Pool, and then click Start.

3.     On the Team Foundation application-tier server, click Start, click Administrative Tools, click Services, select the TFSServerScheduler service, and then click Start,

4. On the Team Foundation application-tier server, open Internet Explorer.

5.    In the address bar, type the following address to connect to the ClientService Web service.

http:// applicationTierServerName:8080/WorkItemTracking/v1.0/ClientService.asmx

6.    Select the StampWorkitemCache Web method and then click Invoke

 

Note:

It is recommended that a TFS Project be created to verify TFS is working properly.  The TFSDeleteProject can be used to delete although Source Control information will remain.  See http://msdn.microsoft.com/en-us/library/ms181482(VS.80).aspx for more information.

 

Upgrading WSS 2.0 to WSS 3.0 after a TFS upgrade

How to setup Windows SharePoint Services 3.0 using a content database upgrade from WSS 2.0 to WSS 3.0  after a Team Foundation Server 2005 to 2008 Upgrade

 

Scenario: TFS 2008 upgrade process does not upgrade WSS 2.0 to WSS 3.0. Customer who want to take advantage of WSS 3.0 after they upgrade TFS 2005 to TFS 2008 would have the following options:

1.       Do an in place upgrade of WSS 2.0 to WSS3.0: The procedure is documented at http://msdn.microsoft.com/en-us/library/cc507614.aspx .

2.       Upgrade of WSS 2.0 to WSS 3.0 by upgrading the content database from WSS 2.0 to WSS 3.0. This document will detail out the required steps/procedures. One of the other objectives that this document also achieve & which is similar to what an in place upgrade does is to remove WSS 2.0 from the box & make sure that WSS 3.0 is set to use the same port numbers as the WSS 2.0 from a TFS usage point of view.

The side by side upgrade process would involve the following tasks:

1.       Take a full back up of the STS_Content_TFS data base. Please refer to http://msdn.microsoft.com/en-us/library/ms253070(VS.80).aspx for procedures to back up databases.

2.       Download the WSS 3.0 PreScan tool from the download center:
http://www.microsoft.com/downloads/details.aspx?FamilyID=e8a00b1f-6f45-42cd-8e56-e62c20feb2f1&DisplayLang=en

3.       Open a command prompt windows & change to the folder where you have downloaded the pre-scan tool. Run the pre-scan tool as:
 PreScan /ALL

4.       Unextend WSS 2.0 from the default web site:

a)      Open IIS Manager(Start->Administrative Tools->Internet Information Services (IIS) Manager).

b)      Browse the SharePoint Central Administration site.

c)       Under Virtual Server Configuration, select Configure Virtual Server Settings.

d)      On the Virtual Server List page, click Default Web Site.

e)      On the Virtual Server Settings page, click Remove Windows SharePoint Services from virtual server.

f)       On the Remove Windows SharePoint Services from virtual server page, Select Remove without deleting content databases. Click Ok.

5.       Close IIS.

6.       Uninstall WSS 2.0 from Add/Remove Programs.

7.       Install WSS 3.0 (with SP1 preferably). You can obtain WSS 3.0 with SP1 at:
http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en

a)      Run SharePoint.exe.

b)      Accept the terms of Agreement & click Continue.

c)       Click Advanced in the Choose the installation you want dialog. 

d)      Select Web Front End as the Server Type, confirm the installation location & click Install Now.

e)      Once the installation is complete, make sure the check box for Run the SharePoint Products & Technologies Configuration Wizard is selected & click Close. 

8.       Complete the SharePoint Products & Technologies Wizard to set up the WSS 3.0 central admin site & WSS 3.0 services on the box.

a)      Click Next on the Welcome page.

b)      Click Yes to allow the Wizard to Restart IIS & WSS services.

c)       In the Connect to a server farm dialog, select No, I want to create a new server farm & click Next.

d)      In the Specify Configuration Database Settings dialog box, give the SQL Instance name for your TFS, WSS_Config as the database name & the Domain\TFSService account name & password & click Next.

e)      In the Configure SharePoint Central Administration Web Application dialog, check Specify port number & provide 17012 as the port number for WSS Central Administration site. Make sure that authentication provider is set to NTLM(which is the default selection) & click Next. 

f)       In the Completing the SharePoint Products and Technologies Configuration Wizard dialog, confirm the settings & click Next.

g)      Once the wizard has successfully completed, click Finish. This would open up the WSS 3.0 Central Administration site.

 

9.       Create a Web Application & extend the Default Web Site with WSS 3.0.

a)      Click Application Management tab in WSS 3.0 Central Administration site. 

b)      In Application Management tab, under SharePoint Web Application Management, click Create or extend Web application.

c)       In the Create or Extend Web application page, click Create a new Web application. 

d)      In Create New Web Application page, select Use an existing IIS web site & select Default Web Site in the drop down list. In Application Pool settings, ensure that Create a new application pool option is selected & give TFSWSS30 as the name of the new application pool. Ensure that Configurable option is selected & give the Domain\TFSService account as the service account for the application pool. Ensure that Restart IIS automatically is selected. In the Database Server give the SQL Server instance name for TFS 2008. Give WSS_Content_Temp as the Database Name. Click OK to create the new web application with the default web site extened in WSS 3.0. 

10.   Delete the temporary content database using the command:

stsadm –o deletecontentdb –url http://<AppTierName> –databasename WSS_Content_Temp

     

      Upgrade the STS_Content_TFS database from WSS 2.0 to WSS 3.0 & attach it to the default web site. To do this open a command prompt window & change to the folder %Program Files%\Common Files\Microsoft Shared\web server extensions\12\BIN. Run the following command:
stsadm –o addcontentdb –url http://<AppTierName> –databasename STS_Content_TFS

11.   Install  TFS 2008 extensions for WSS 3.0 from <TFS Installation Location>\wssext folder by running the setup.exe. At the end of installation, after you have clicked Finish, you would be prompted with the dialog box for the WSS 3.0 web part configuration. Provide the http://ATName/sites as the WSS site, http://ATName/Reports as the reports site & http://ATName/ReportServer for the reporting services administrative site & click Apply. Click Exit.

 

12.   Connect to Team Foundation Server using Team Explorer & verify connectivity.

Team Foundation Server

We have two versions of Team Foundation Server available:

1. Team Foundation Server 2005

2. Team Foundation Server 2008

The Team Foundation Server 2005 comes with a Service Pack 1 as well.

 

The TFS install guide are the best source of information for understanding the deployment scenarios for TFS.

You can obtain the latest TFS 2005 install guide at:

http://www.microsoft.com/downloads/details.aspx?familyid=e54bf6ff-026b-43a4-ade4-a690388f310e&displaylang=en

 

You can obtain the latest TFS 2008 install guide at:

http://www.microsoft.com/downloads/details.aspx?familyid=FF12844F-398C-4FE9-8B0D-9E84181D9923&displaylang=en