Sep 10

Few customers have seen failures in upgrading WSS2.0 to WSS3.0. When they run the upgrade utility the process fails after step 2. It is helpful to take a look at the log file but in many cases the upgrade has succeeded if you run the upgrade with forceupgrade option. Here is a command that was tried by one customer and they were able to successfully upgrade the WSS server.

In place upgrade:

%commonprogramfiles%\Microsoft Shared\Web Server Extensions\12\Bin stsadm -o upgrade -forceupgrade -url http://companyweb – inplace

Side by Side Upgrade:     

%commonprogramfiles%\Microsoft Shared\Web Server Extensions\12\Bin stsadm -o upgrade -forceupgrade -url http://companyweb – sidebyside

 
 

Aug 03

Many customers have WSS3.0 farms in house and they want to use these farms with TFS. In TFS 2005 you had to use WSS2.0 on TFS machine and you could not leverage the existing farms in the company. With TFS 2008 or Orcas you can use existing WSS3.0 farm. This is well known fact now but I have received many questions about upgrading the TFS 2005 with WSS2.0 environment to TFS 2008 with existing Share Point Farm. Following are detailed steps to achieve this

Detailed instructions

  • Upgrade TFS:  Run Orcas Installer to upgrade the VS 2005 TFS server to Orcas Beta2.  Please follow the instructions in the latest installation guide (or in the document I sent you previously). At end of this process you should have Orcas server with WSS2.0 configured.
    • Please do a quick sanity check to make sure everything is working normally.
  • In-place upgrade of WSS2.0:  Next follow the instructions in http://technet2.microsoft.com/windowsserver/WSS/en/library/91046a84-57a1-40cb-a32c-ff3395073dc91033.mspx?mfr=true, paying attention to the topics on Plan and Prepare for Upgrade, Perform Pre-Upgrade steps and Perform and in-place upgrade
  1. Run WSS prescan.exe tool to verify if you can upgrade WSS from 2.0 to 3.0
  2. Run WSS3.0 Installer and select the upgrade option
  3. The installer will ask you for new Administration Port. You cannot use the old port(17012). You need to select new port number.
  4. Complete all the installation and upgrade steps for WSS3.0
  5. Now you should have Orcas server with WSS3.0
  • Migrate team sites:  Migrate your TFS team project sites by exporting your existing team project site collections from the Sharepoint 3.0 server on the application tier, and importing into your remote WSS3.0 farm
  • Update Sharepoint 2007 farm:  Next you’ll need to update the remote Sharepoint farm to allow new team sites to be created as part of project creation (new TFS site templates) and the Reporting redirector for the reporting web part.
    •  On the remote Sharepoint 2007 farm, install the Sharepoint extensions for TFS
    • Run Share Point Extensions for TFS setup. This should be located at InstallMedia\WssExt directory. This will upload the new site templates for WSS3.0.
  • Link Orcas TFS and remote WSS3.0 farm:  Now you have Orcas TFS and Remote WSS3.0 setup. But you still have to link them up to work together.
    • You can do this by using TFSAdminUtil command on the application tier machine,  where you need to replace <wssserver> with the name of you server farm (or it’s virtual name). Here is  the command to perform this task.
      • TFSAdminUtil configureconnections /SharepointURI:http://<wssserver>:80  /SharepointSitesUri:http://<wssserver>:80/sites /SharepointAdminUri:http://<wssserver>:adminport /SharepointUnc:\\<wssserver>\sites
      • Please do a sanity check to make sure everything is working properly.  You should be able to go to a team project in Team Explorer, right-click on the project node and select “Show project portal”, and this should take you to the correct team site on the remote Sharepoint 2007 farm

 

I hope this is helpful. Please let me know if you have any questions or concerns

Jun 25

In my previous posts around TFS and Windows SharePoint Services I explained how you could use WSS3.0 or WSS2.0 with TFS. In many companies you already have a corporate SharePoint Farm. You may want to use that with TFS so you don’t have to maintain 2 different sets of portals. This post tries to explain how you could achieve this.

TFS requires

  • SQL Reporting services to be present on TFS AT machine
  • WSS can be installed on any machine on the network.

Relationship:

There is a circular relationship between TFS, WSS and Reporting. What do I mean?

  • TFS uses WSS as the Team Portal. All the documents and process guidance is hosted within WSS.
  • When users access their team portal they also want to have access to their reports on the portal so we have links to the reports on the portal. This requires us to know the reporting server URL to redirect the requests made by users.
  • TFS also needs to keep track of Reporting and SharePoint URLs for various tasks.

In short:

  • TFS needs to know where WSS and Reporting are located
  • WSS needs to know where Reporting server is located for a TFS Instance.

Sharing same SharePoint Farm for multiple TFS Instances:

To achieve this we require every TFS instance to have its own Managed path. You can create managed paths using the WSS admin site. As shown in the diagram below TFS_001 TFS Instance should have its unique managed path for e.g. TFS001. Similarly for TFS_002 you should have TFS002.

Shareing Share point Farms

Following are steps you can use to setup this environment

  • Create a managed path for your TFS Instance using WSS admin site.
  • Once the managed path is created you can install TFS. In TFS setup for WSS information provide
    • The root site URL which is the URL for your managed path e.g. http://<sharpointservername>/TFS001
    • Admin site URL for the farm at time
  • You have to install WSS_Ext SKU on SharePoint Farm Machine.

TFS WSS config tool

Note: You can run this tool again for 2nd TFS server by running <TFSInstallDirectory>\tools\TFSWSSConfig

Jun 01

Note: This post is relevant only to Dual server configurations of TFS.

Many customers have asked me if TFS Setup account needs to be Administrator on TFS Data Tier. For Orcas the answer is “NO”. Let me provide some details on this topic.

In VS 2005 we had a DT SKU that was installed on DT machine. Therefore you had to be administrator to install the DT SKU. Based on tons of feedback we got from our customers we removed that SKU in Orcas and now you just have 1 SKU or installer for both single server and dual server setup. The advantage is you do not need to be administrator to install TFS in dual server environment. You still need to be a SQL Administrator so we can create TFS databases.

Following are tasks we perform as TFS Setup on the Data Tier machine.

  1. In System Health Check we try to connection to DT machine and check if all the services are up and running. This will fail if you are not administrator on DT and will generate few warnings for you. You can ignore the warnings.
    1. Just make sure the TFS Setup account has permission to create Databases on the SQL instance you are using.
  2. We create TFS Databases and provide access to TFS Service account to these databases. This should be successful even if you are not Admin on DT machine.

Hope this provides some more understanding around TFS Setup account.

May 31

As I mentioned earlier we now support running TFS service as network service. The primary advantage of using network service is, you don’t have to worry about managing the password for the account. If you are using VS 2005 TFS running under domain account and want to move to Orcas with TFS Service running under Network Service following are the steps.

Steps to upgrade TFS 2005 with Domain account to Orcas with Network Service

  • Run Orcas TFS installer to upgrade from VS 2005 TFS to Orcas TFS. At end of the setup you will your TFS environment upgraded to Orcas with TFS service running under the service account used in Orcas.
    • We do not recommend you to change the service account at time of upgrade
  • After the upgrade is over you can use TFSAdminUtil to change the service account. The command to change the service account is as follows
    • TFSAdminUtil changeaccount OldDomainAccount “NT Authority\Network Service”

Now you should have your Orcas environment up and running with Network Service.

Please give us your feedback. Is this good enough solution or do you want us to improve this experience.

May 31

Orcas supports Named Instances of SQL Server. In VS 2005 we only supported default instance of SQL Server this was a major pain point for customers using SQL farms. We fixed this in Orcas and now you can use named instances of SQL. This post is about how to upgrade from VS 2005 TFS using default instance to Orcas using Named Instances.

As I mentioned in my last post related to Upgrade. We want you to make sure you have a working Whidbey before trying to upgrade to Orcas. We don’t want you to change the configuration of the server.

The steps to upgrade are as follows.

  • Run Orcas TFS installer to upgrade your VS2005 TFS server using Default Instance. At end of this process you should have Orcas server with default instance.
  • Next take full backup of all the TFS Databases. You can refer to http://msdn2.microsoft.com/en-us/library/ms253070(VS.80).aspx for the process of taking backup. Easiest way is to use SQL Management studio.
  • Restore all these backed up databases on Named Instance of SQL Server you want to use with TFS. Now you should have all the databases moved to new instance. You can refer to http://msdn2.microsoft.com/en-us/library/ms252458(VS.80).aspx for more details on restoring databases.
  • We have some information in sysmessages table in masterdb and SQL jobs in MSDB. These are not restored by previous step. To get these you can either run repair or you can run tfsdb.exe from your tools directory
    • TfsDb.exe install /server:”<servername>\<instancename>” /property:”TFS_SERVICE_ACCOUNT=<TFSSERVICEACCOUNT>;TFS_REPORTING_ACCOUNT=<TFSREPORTSACCOUNT>;LCID=1033″ /log:d:\logfile.txt
  • At this point TFS is not going to work as TFS AT does not know anything about the new location of the databases.
  • You can use TFSAdminUtil to update the system with new SQL Instance information.
    • Command: TFSAdminUtil RenameDt NewDTServerName\InstanceName

Now you should have your TFS configuration ready to go. You can also refer to Renaming TFS Server topic.

May 31

Please read http://blogs.msdn.com/sudhir/archive/2007/08/03/upgrade-tfs-2005-with-wss2-0-to-tfs-2008-orcas-with-existing-wss3-0-farm.aspx if you want to upgrade to existing WSS3.0 farm.

This topic is very similar to the previous topic(http://blogs.msdn.com/sudhir/archive/2007/05/31/upgrade-2005-with-wss2-0-to-orcas-wss3-0.aspx). The primary difference is how will you move to WSS3.0 on remote machine.

The steps remain same. In short

  1. Run Orcas Installer to upgrade the VS 2005 TFS server to Orcas
  2. Create your WSS 3.0 environment on remote machine. Migrate your TFS sites to new environment. You can find details on this topic at http://technet2.microsoft.com/windowsserver/WSS/en/library/91046a84-57a1-40cb-a32c-ff3395073dc91033.mspx?mfr=true.
  3. Now you have Orcas TFS and Remote WSS3.0 setup. But you still have to link them up to work together.
  4. You can do this by using TFSAdminUtil command. Following is the command to perform this task.
  • TFSAdminUtil configureconnections
  • /SharepointURI:http://wssserver:80 
  • /SharepointSitesUri:http://<wssserver:80/sites
  • /SharepointAdminUri:http://wssserver:adminport

/SharepointUnc:\\wssserver\sites

May 31

One major scenario for most of our customers who are using Visual Studio 2005 Team Foundation Server is moving to Orcas and leveraging the new features around WSS3.0. The upgrade path to this is very simple and straight forward. This post is focused on performing in-place upgrade of WSS. That means you upgrade WSS2.0 to WSS3.0 on the TFS server itself.

As I mentioned in my last post related to Upgrade. We want you to make sure you have a working Whidbey before trying to upgrade to Orcas. We don’t want you to change the configuration of the server.

The steps to upgrade are as follows.

  • Run Orcas TFS installer to upgrade your VS2005 TFS server. At end of this process you should have Orcas server with WSS2.0 configured.
  • Next Run WSS prescan.exe tool to verify if you can upgrade WSS from 2.0 to 3.0
  • Run WSS3.0 Installer and select the upgrade option
  • The installer will ask you for new Administration Port. You cannot use the old port(17012). You need to select new port number.
  • Complete all the installation and upgrade steps for WSS3.0
  • Now you should have Orcas server with WSS3.0. You still cannot use the system as you still need to tell TFS about the new URLs for WSS and also upload the new site templates for WSS3.0
  • Run Share Point Extensions for TFS setup. This should be located at InstallMedia\WssExt directory. This will upload the new site templates for WSS3.0.
  • The upgrade changes the WSS admin site URL. To make this change in TFS you can use TFSAdminUtil . Following is the command you can use.
    • TFSAdminUtil configureconnections /SharepointAdminUri:http://wssserver:adminport  

Note: You can use TFSAdminUtil to update all the different URL’s for WSS. Following is the syntax for updating all WSS related attributes in TFS.

  • TFSAdminUtil configureconnections
    • /SharepointURI:http://wssserver:80 
    • /SharepointSitesUri:http://<wssserver:80/sites
    • /SharepointAdminUri:http://wssserver:adminport
    • /SharepointUnc:\\wssserver\sites

Hope this post is helpful. Please let me know your experiences.

May 31

We have put in a lot of effort on getting our Upgrade experience right. It is not perfect but I think it is great. This post is first in the series of posts around upgrade. You can have so many scenarios around upgrade; I will take one scenario at a time to provide more details. For now let’s talk about basic upgrade from VS 2005 TFS to Orcas Beta 2 or higher. The experience for you should is same as new setup. Our upgrade is completely integrated into setup. Setup will ask for your database server name. We probe the database server to check if it is a existing database from VS 2005. If it is we upgrade it to Orcas. You can either have VS2005 RTM or SP1 version.

We also realized some customers may uninstall VS2005 before running Setup for Orcas and therefore we have made sure the Orcas setup can handle that scenario. Following are few pre-requisites for upgrade to work flawlessly.

  1. You should have had a running VS 2005 before you started the upgrade process. It does not matter if you uninstalled VS2005, but before you uninstalled the VS2005 TFS server must be in healthy and running state.
  2. You are not allowed to change the service accounts at time of upgrade. You have to use the same TFS service and data sources account that was used to run TFS before upgrade.
    1. You can change the accounts after upgrade is successful using TFSAdminUtil tool.
  3. You should not try to change the name of TFS servers or database location at time of upgrade all this can be done after the upgrade is successful.

Having spoken about limitation now let’s talk about some key scenarios you all will be interested in. You all want to use the new features provided in Orcas. How do you get your VS 2005 TFS Server to run with all the new features of Orcas TFS? Following are the major scenarios

  1. How do I upgrade from VS 2005 with default instance of TFS to Orcas with SQL named instance?
  2. How do I upgrade from VS 2005 with WSS2.0 to Orcas with WSS3.0?
  3. How do I upgrade from VS2005 with WSS3.0 to Orcas with remote (existing) WSS3.0 farm?
  4. How do I upgrade from VS 2005 with domain account for TFS service to Orcas with Network Service?

I will try to explain each of these scenarios in next few posts. The key here is the standard upgrade will only upgrade you from VS 2005 TFS with WSS2.0 to Orcas TFS with WSS2.0. We have to perform some extra steps to achieve above 4 scenarios. It is not difficult but just few more steps.

You should see additional posts soon…

May 31

After V1.0 we got a lot of feedback around SharePoint. Following are few things we heard a lot

  1. Why can’t you install WSS for us?
  2. Why can’t you just use my existing WSS farms? Why do I have to dedicate a WSS installation for TFS?

We heard you all. We fixed these 2 major issues for you. Orcas Beta 2 installer will have support for WSS 3.0. Following are few things we support.

  1. Orcas TFS setup can install WSS3.0 for you. We ship WSS 3.0 on our media therefore you don’t have to worry about anything. We will install it, Provision it and upload the site templates we need for TFS.
  2. We also support use of existing Share Point Farms. You can either use WSS2.0 farms or WSS3.0 farms. The only thing we expect from you is
    1. Have a pre-provisioned WSS environment. That means you should have configured your WSS. Have it up and running.
    2. We require the Sites URL and Admin URL for your existing farm. Make sure you can get to these URL from your browser.
    3. If you are using WSS on any other machine than your TFS Server you also need to run setup for Share Point extensions for TFS. This setup has to be run on your WSS server.

Orcas Setup will ask your preference on WSS page and you can choose one option, either install or use exiting WSS. We really did not want to tell you how to configure your WSS environment and therefore we are not going to document the provisioning steps for WSS on TFS MSDN site. Finally who are we to tell you how to setup and configure your environment? Having said that I can share with you the steps we follow to provision our test WSS environments. These are scripts which we use to provision WSS for internal testing of TFS installer.

This is not guidance just a sample of what we do…

Provisioning of WSS3.0

  • SETLOCAL
  • SET WINFXPATH=WINFX_INSTALL_PATH
  • SET WSSINSTALLPATH=WSS_INSTALL_PATH
  • SET WSSTEMPPATH=%USERPROFILE%\Local Settings\Temp\wss.tmp
  • SET WSSBINPATH=C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin
  • SET WSSOWNERLOGIN=WSS_SERVICE_ACCOUNT_DOMAIN\WSS_SERVICE_ACCOUNT_USER
  • SET WSSOWNERPASSWD=WSS_SERVICE_ACCOUNT_PASSWORD
  • SET WSSDBINSTANCE=DATABASE_SERVER
  • SET WSSWEBSITEDESC=Default Web Site
  • mkdir “%WSSTEMPPATH%”
  • CALL “%WINFXPATH%\DotNetFX3.exe” /q /norestart
  • “%WSSINSTALLPATH%\SharePoint.exe” /extract:”%WSSTEMPPATH%” /quiet
  • “%WSSTEMPPATH%\setup.exe” /config “config.xml”
  • “%WSSBINPATH%\stsadm.exe” -o setconfigdb -databaseserver “%WSSDBINSTANCE%” -farmuser “%WSSOWNERLOGIN%” -farmpassword “%WSSOWNERPASSWD%”
  • if NOT %ERRORLEVEL%==0 then goto eof
  • “%WSSBINPATH%\psconfig.exe” -cmd adminvs -provision -port 17012 -windowsauthprovider onlyusentlm
  • “%WSSBINPATH%\stsadm.exe” -o extendvs -exclusivelyusentlm -url http://%COMPUTERNAME%:80 -ownerlogin “%WSSOWNERLOGIN%” -owneremail “admin@localhost” -sitetemplate sts -description “%WSSWEBSITEDESC%”
  • if NOT %ERRORLEVEL%==0 then goto eof
  • “%WSSBINPATH%\stsadm.exe” -o siteowner -url http://localhost:80 -secondarylogin %userdomain%\%username%
  • if NOT %ERRORLEVEL%==0 then goto eof
  • iisreset
  • ENDLOCAL

 
 

Provisioning of WSS2.0

  • SETLOCAL
  • REM Variables you need to set are here:
  • SET StsAdm=“D:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\Bin\Stsadm.exe”
  • SET ServiceUser=”ServiceAccountDomain\ServiceAccountUser
  • SET ServicePassword=”ServiceAccountPassword
  • SET DataTierInstance=”DataTierInstance
  • REM DataTierInstance can also be “Machine\Foo” or “Machine,1234” for named instances
  • REM Set the admin port to the value we typically use:
  • %StsAdm% -o setadminport -exclusivelyusentlm -port 17012 -admapcreatenew -admapidname TFSWSSADMIN -admapidtype configurableid -admapidlogin %ServiceUser% -admapidpwd %ServicePassword%
  • if NOT %ERRORLEVEL%==0 then goto eof
  • REM Create/assign the config database:
  • %StsAdm% -o setconfigdb -databaseserver %DataTierInstance% -databasename “STS_Config_TFS”
  • if NOT %ERRORLEVEL%==0 then goto eof
  • REM Create the Virtual Server:
  • %StsAdm% -o extendvs -exclusivelyusentlm -url http://localhost:80 -ownerlogin %ServiceUser% -owneremail “admin@localhost” -dn “STS_Content_TFS” -apcreatenew -apidname TFSWSS -apidtype configurableid -apidlogin %ServiceUser% -apidpwd %ServicePassword% -sitetemplate sts
  • if NOT %ERRORLEVEL%==0 then goto eof
  • REM Delete and recreate the SQL RS path exclusions
  • REM Note, the deletes will error if they don’t already exist – you can ignore those errors:
  • %StsAdm% -o deletepath -url http://localhost:80/ReportServer
  • %StsAdm% -o addpath -url http://localhost:80/ReportServer -type exclusion
  • if NOT %ERRORLEVEL%==0 then goto eof
  • %StsAdm% -o deletepath -url http://localhost:80/Reports
  • %StsAdm% -o addpath -url http://localhost:80/Reports -type exclusion
  • if NOT %ERRORLEVEL%==0 then goto eof
  • REM Force the Virtual Server instance to the correct version (of ASP.Net etc.)
  • %StsAdm% -o upgrade -forceupgrade -url http://localhost:80
  • if NOT %ERRORLEVEL%==0 then goto eof
  • ENDLOCAL

 
 

Hopefully this information is useful. Please let me know if you need any additional information.