SharePoint Support

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

Why can't you install WSS for us?
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.

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