Ok now that we’ve successfully installed Team Foundation Server, its time to validate that it’s running. We’ll do this by checking some basic things on the system. Then we’ll look at TFS security and how the leverage it to save administration

We’ll cover:

· Validating TFS URLs

· Validating TFS Services

· A few words on the installation logs

Installation Validation

We are all excited to jump in and start in using a new set of tools, but first we probably should make sure the installation went ok first and it's fairly simple. Next we will dive into a few steps that will help us with this. I'll give a couple of tips for upgraders at since that’s fairly specific to your environment.

Validate Team Foundation Server URLs

This one is easy and determines a whole host of services and web sites have been configured correctly. Let's start by looking at the main URLs for the Team Foundation Server (you can get the first one from the "Success" window from your install if that is still up, or if you closed it just following the steps below).

1. Get the URL. Go to the Start Menu ➤ Team Foundation Server 2013 ➤ Team Foundation Server Administration Console.

2. Once you have the console open go to the Application Tier node in the selection tree as indicated in the screen below in Figure 3-1. Note the Web Access URL on this page. It will be in the format of http(s)://<server name>:<port, normally 8080>/tfs

Figure 3- 1 TFS Web Access URL

3. Now that we have that we can check the Web Access services with the URL. (Note the Server URL would also be able to perform this quick test on the local server). Put that URL into a browser window on the TFS server. You should see windows displayed similar to the ones below in Figure 3-2. Click on the Administer panel and this window should pop up as in Figure 3-3. We'll visit this window again later.

Figure 3 - 2 TFS Web Access main page

Figure 3- 3 TFS Web Access Admin screen

Validate TFS Services

Another important step in making sure your install went smoothly is examining the services installed by Team Foundation Server. Most of the time (actually since TFS 2010) if you make it to the installation confirmation window with a page of green check marks you are usually good to go. However it never hurts to double check a few things. Since Team Foundation server runs on the standard Windows Sever stack it depends upon a slew of "standard" services, and a few specialized ones to be running to do its job including but not limited to:

· World Wide Web Publishing Service

· SQL Server (for both TFS and SharePoint)

· SQL Server Reporting Services

· Visual Studio Team Foundation Background Job Agent

The above system level services are to be expected on a Standard Single Server install like we performed elsewhere in this book. If you have another configuration or a scaled out deployment your individual servers would not necessarily run all of these. These are fairly easy to identify in the Service applet and should be running and should be set to Automatic start. There are a bunch of others that will be seen in a fully configured TFS server as other featured are added (as in the Build Service we'll check out next) but these are good to start with. An interesting service worth mentioning is the last one on the list. You'll only know something is wrong with the "Visual Studio Team Foundation Background Job Agent" when things you did in the system don’t seem like they took properly (permissions for instance) so it bears both initial checking and monitoring on occasion since it can be confusing when you are setting things up properly and it doesn’t seem to be working through no fault of yours.

1. Start the Services applet. Go to Start ➤ Administrative Tools ➤ Services.

2. Verify key services are running and Set to Automatic Start as in Figure 3-4.

Figure 3- 4 Windows Services applet highlighting the Visual Studio Team Foundation Background Job Agent

Installation Logs

So I'm sure someone at Microsoft will be upset with me saying this but the Installation Logs are of limited usefulness in validating if an install happened correctly in the absence of any real errors presented during the installation. Why? There is just too much information in the files appearing as a potential error that in reality is just information. However if you are tracking down a stubborn installation error and can focus on that or if you are working with Microsoft Technical Support they can be useful. The location is here:

C:\Users\<install account>\AppData\Local\Microsoft\Team Foundation\Setup\Logs

So if you were installing under the account TFSADMIN you would look in:

C:\Users\TFSADMIN\AppData\Local\Microsoft\Team Foundation\Setup\Logs

Here is a typical view in Figure 3-5 of files you might find in that directory for the curious. Note the use of the Hidden flag on the View menu in File Explorer. Without selecting that you'll be staring at an empty directory:

[Douglas5]

Figure 3- 5 File Explorer in the TFS Logs directory

Installation Experience

Using the Standard Single Server installation wizard I'm going to step through the installation process. I'm using this configuration because it's fairly simple for documentation purposes and one of the more popular layouts for Team Foundation Server. I'll cover the steps here:

1. Select the media. Choose the DVD / ISO file for the TFS install as depicted here in Figure 2-5 below

Figure 2- 5 Media Selection

2. You'll need to pick a location next, most people just leave the default and keep going. You'll need to accept the license terms as in the Figure 2-6 below to continue, then you’ll be presented with a screen similar to Figure 2-7.

Figure 2- 6 Pick a location for the installation

[Douglas4] [GG5]

Figure 2- 7 First progress screen, you are on your way

3. Next we need to pick a wizard. As we said earlier we are going to choose the Standard Single Server as in Figure 2-8

Figure 2- 8 Standard Single Server Wizard

4. Next we'll be prompted to enter some account information. Note the yellow triangles in Figure 2-9, this is how the wizard will prompt you for information throughout the install. Incidentally, it’s the same symbol used to warn you of warning level issues. Here's where you get to use the checklist from the previous chapter. Get the account credentials you identified as the SQLSERVICE account and enter it here.

5. After that we'll need to configure reporting services, if it wasn't already done. The installation wizard will detect if it is or not and alert you, as we see in the figure below. We are going to jump there next.

Figure 2- 9 entering the Service Account credentials

6. Back to your checklist from the previous chapter, enter the Reporting Services server here as in Figure 2-10.

Figure 2- 10 SQL Server and Reporting Server Instance

7. Select or enter the service account for Reporting Server service from the checklist in the last chapter as depicted in Figure 2-11.

Figure 2- 11 Report Server service account

8. Next we need to configure the Web Service URL as shown in Figure 2-12. If it wasn’t already configured you'll be prompted to create it, which is what I did here.

Figure 2- 12 Create or Configure web service URL

9. Reporting Services DB configuration is next. You can also create a new DB here as well.

Figure 2- 13 DB Setup and Configuration

10. The next two steps are fairly explanatory, but pay attention to the Execution Account screen in Figure 2-14, you will want to enter the account you selected for the TFSREPORTS account. Pay careful attention to the format because it's very particular. It must be in a DOMAN\ACCOUNT format, even for a local account. .\TFSREPORTS for a local account for an example.

Figure 2- 14 Setting the Execution Account

11. Once you are done here, you'll be back at the TFS Server Standard Configuration wizard as in Figure 2-15 and being prompted to confirm your configuration settings. Click Next.

Figure 2- 15 Confirm your configuration

12. Next you'll see a screen like this below as the wizard progresses through its readiness checks as in Figure 2-16, when complete you'll get the second screen complete with any warnings or errors. In this case I'm being warned that my Application Tier needs 50GB of free disk space. Ordinarily this would be something I'd want to take care of now or follow the advice listed post install but this is an example so we can safely continue so we'll hit the Configure button.

Figure 2- 16 Readiness checks in progress

Figure 2- 17 Readiness Checks Complete

13. Success! Hopefully at the end of all the configuration, this next screen in Figure 2-18 is what you will see. If not, follow the warnings and resolve the issues.

Figure 2- 18 Configuration Success!

14. Finally you have completed configuration and will be presented with the summary screen below in Figure 2-19. Some important things to note on this screen.

· TFS Server URL: http://<server name>:<port>/tfs

· Detailed Results: What you will find here will vary based on how the configuration went. A couple of typical notes here include a note on enabling compression, the port on the firewall that was opened, and a resetting of the Windows service timeout.

· Link to the configuration log. It would be a great idea to thoroughly check this log for any errors before continuing.

Figure 2- 19 Configuration Results

SharePoint compatibility issue One thing worth mentioning is an issue that exists as of this writing between SharePoint Foundation 2013 and Windows 8.1 or Windows Server 2012 R2. Though this will affect all installations, it will stop the standard wizard dead in its tracts if you didn't already take care of it, and it detects that it still needs to install SharePoint you will get the error screen depicted below. To get around this you will need to install SharePoint Foundation 2013 with SP1 which can be downloaded here http://www.microsoft.com/en-us/download/details.aspx?id=42039.

 

Install Categories

As mentioned in the previous chapter, there are scaling considerations to consider. This is especially true if you are in an existing environment that is maxed out and this update is part of your plan to add capacity. Most people however, they are looking at single server environments or close to that.

In order to satisfy the broadest audience that is the model we will follow in this book. If I get into a section where a scaling or high-availability touch point exists, I will mention it in a call out or note towards the end of the chapter. To begin with we should review the main installation types that are available. There are two broad categories that we need to see which we’ll fall into:

New Install

A new installation is the most straight forward installation type. We have no earlier versions of Team Foundation Server to contend with and other than the normal prerequisites, we can begin the installation. Here we are going to assume you are using a single server configuration and haven’t chosen scale the environment to multiple servers (see Chapter 1 for more details on scaling and performance).

Which Wizard to Use?

Once you get into the install you'll run into this choice pretty quick, so best if we talk about it prior. The Team Foundation Server Configuration Center offers you the following installation / configuration choices:

· Basic - this will install (as the name implies) just the basic services for running TFS. It will also either install SQL Express, or let you connect to existing SQL Server Standard or Enterprise but won't install them for you. You'll get Source Control, Work Item Tracking, and Build Services. You will not however get SharePoint or Reporting Services Integration configured. All default options will be selected for you.

· Standard Single Server - This wizard also is also intended for a single server with the default options. The big difference with this one is that it will also install SharePoint Foundation 2013 (or configure it), and configure SQL Server Reporting Services. This is the one recommended for most single server installs of TFS, and the one we'll walk through in this book. The big caveat with this one is that you need to use the default instance of SQL Server (which is ok most of the time, unless you are using SQL for something else that commandeered it on you). You also can't use this wizard if you want to use remote SQL, Reporting, or SharePoint servers. Additionally if you want to use Negotiate (Kerberos) authentication, or if you need to install the Application Tier onto and existing web site set it up to use a different port, you'll want to use the Advanced wizard instead.

· Advanced - If you need full control over all aspects of the install, this is the one for you. It only runs on Windows Server OS's (so no client OS installs with this one). It can do everything the Standard one can do plus support using remote SharePoint, SQL, or SQL Reporting Servers. You can also install the Application Tier on a different port, us a non-default instance of SQL Server or Reporting Services, or if you want to skip SharePoint or SQL Reporting Services integration. Additionally you can use Negotiate (Kerberos) authentication with this wizard. The only thing you wouldn’t want to use this for is just installing or reinstalling the Application Tier on its own (look below for that).

· Application Tier Only - As the name implies, it is used mainly to install an additional Application Tier (Team Foundation Server) to your existing Team Foundation deployment. You can use it on Client and Server OS's. It's also very useful for moving a TFS from one server to another and for disaster recovery. Don’t use this wizard to set up your first Team Foundation Server.

· Upgrade - This is the wizard to use to upgrade from an older Team Foundation Server version. It supports both client and server OS's. Please remember to back up your server prior to starting this wizard. This wizard has come a long way from when they introduced it in TFS 2010 but it still never fails to inspire panic since one of the first things it does is remove the old version and if it fails it will not reinstall the old one for you.

Here we will want to install using the Standard Configuration. This makes sense if you want to install Team Foundation Server on a single server with reporting and a team portal. It makes installation much simpler. The workflow we are going to follow here is very simple and I’ll detail it here in Figures 2-1, 2-2 for your reference.

Figure 2 - 1 TFS Installation Workflow

Figure 2 - 2 Items configured in a Standard Single Server installation

Active Directory

You can install Team Foundation Server on multiple servers if they are all in an Active Directory Domain, and that domain is at the functional level that Team Foundation Server Supports. A single server on a workgroup is also supported. You cannot however install Team Foundation Servers on severs who’s domain controllers are running Windows NT Server 4.0 (yes there are still a few around). The Table 1-6 below shows the functional levels that are NOT supported. All others are considered fair game at this point for TFS 2013:

Table 1-6 Functional Levels and Active Directory

Functional levels for Active Directory domains	Supported
Windows 2000 mixed mode Domain controllers that are running Windows NT Server 4.0, Windows 2000, Windows Server 2003, and Windows Server 2003 R2.	No
Windows Server 2003 interim mode Domain controllers that are running Windows NT Server 4.0, Windows Server 2003, and Windows Server 2003 R2.	No

Ports

You will likely need to open some ports on your firewall so Team Foundation Server can communicate with the various interfaces it needs. My table below shows the default ports you will need to make sure are open. If you have modified your installation you’ll need to verify what these are set to in your environment. This may require you speaking with your IT department if you are in a larger company.

Also, if you are using Windows Firewall the install process will set the ports for you. If you are using another firewall you’ll need to check the documentation or with your local IT person to figure out how to get these open.

Table 1-7 Ports

Service	Default TCP Port	Alternate Port?
SQL Service (Database Engine) Note: This is used for the default instance (the first one), for named instances it uses a dynamically assigned port. Use the SQL Server Configuration Manager to find out	1433	· Alternate Port:
SQL Browser Service (Database Engine)	1434	· Alternate Port:
SQL Server Analysis Services Redirector	2382	· Alternate Port:
SQL Server Analysis Services	2383	· Alternate Port:
SQL Server Reporting Services	80	· Alternate Port:
Report Server (if it’s not on the Team Foundation Server)	Windows Management Instrumentation(WMI)	· Shared Service Host, ports assigned through DCOM.
Default Web Site (For SharePoint, Hint: if you aren’t sure you can use Internet Information Services (IIS) Manager to check)	80	· Alternate Port:
SharePoint Central Administration (If you aren’t sure just start the app and check. If you need to change it you will need to do it in both the here and in the Bindings for the site in IIS).	17012	· Alternate Port:
Team Foundation Server	8080	· Alternate Port:
Team Foundation Server Proxy	8081	· Alternate Port:
Release Management Server (if you are using this)	1000	· Alternate Port:

If anything, the supported OS’s got tighter this release with the elimination of some platforms. You can use:

Server OS’s (Server Core Installations not supported):

· 64-bit versions of Windows Server 2012 R2 (Essentials, Standard, Datacenter)

· 64-bit versions of Windows Server 2012

· 64-bit versions of Windows Server 2008 R2 (Standard, Enterprise, Datacenter)

· Windows Small Business Server 2011 (Standard, Essentials, Premium Add-On)

For the love sanity, if you choose to go the SBS route, make sure you calculated your fully configured SBS server with all its components (Exchange, etc.) the ADD the Team Foundation Server requirements in addition to those. Better yet would be to use it in your deployment, but not as a single server TFS solution.

For installations of TFS or SQL Server with Windows Server 2008 R2, you need .NET Framework 3.5 installed. On Windows Server 2008 R2, you can install .NET Framework 3.5 by using the Add Features Wizard from Server Manager.

Supported Client Operating System Requirements:

· Windows 8.1 (Basic, Professional, Enterprise)

· Windows 8

· Windows 7 (Home Premium, Professional, Enterprise, Ultimate, SP1 minimum)

Best to use a client OS only as a test install for a proof of concept. You will not be able to install SharePoint, Reporting, TFSProxy. What does this mean for you? No website to collaborate, no HTML project reports, and you won’t be able to proxy source files. Move to a server OS above for any production use. I always find it amazing when I see questions on “performance issues”, then find someone using a client operating system. Also, the “Standard” install isn’t supported on a client OS since it installs SharePoint. Have I talked you out of trying to do this on the cheap with a client OS yet? Very good.

Performance and Planning

Nothing gets more hotly contested in systems engineering circles than performance recommendations. The recommendations in the table below come directly from Microsoft. They are the minimum. Take special note of the new hard disk requirements. Also, the numbers below do not include recommendations for SharePoint installed on the same server, those recommendations are in the next section. My notes from my personal experience are in a note below.

Hardware

The following table reviews the general hardware recommendations for Team Foundation Sever, broken out by tier or role. These are good starting recommendations but you need to keep in mind any local considerations that may increase these.

Table 1-3. Scaling and Performance Recommendations

Number of users	Role	Configuration	CPU	Memory	Hard disk
Less than 250 users	TFS Server	Single-server (Team Foundation Server and the Database Engine on the same server).	1 single core processor at 2.13 GHz	2 GB	1 disk at 7.2k rpm (125 GB)
250 to 500 users	TFS Server	Single-server (Team Foundation Server and the Database Engine on the same server).	1 dual core processor at 2.13 GHz	4 GB	1 disk at 10k rpm (300 GB)
500 to 2,200 users	TFS Server	Dual-server (Team Foundation Server and the Database Engine on different servers).	1 dual core Intel Xeon processor at 2.13 GHz	4 GB	1 disk at 7.2k rpm (500 GB)
	Database Server	This is for the Database Engine portion with 500 to 2,200 users. (For above configuration)	1 quad core Intel Xeon processor at 2.33 GHz	8 GB	SAS disk array at 10k rpm (2 TB)
2,200 to 3,600 users	TFS Server	Dual-server (Team Foundation Server and the Database Engine on different servers).	1 quad core Intel Xeon processor at 2.13 GHz	8 GB	1 disk at 7.2k rpm (500 GB)
	Database Server	This row is for the Database Engine with 2,200 to 3,600 users. (For above configuration)	2 quad core Intel Xeon processors at 2.33 GHz	16 GB	SAS disk array at 10k rpm (3 TB)

Scaling Tips – 1 to many

So you need more performance out of your Team Foundation Server 2013 installation. First step would be sure you meet the minimum requirements in this chapter. Since there are a lot of scenarios here, let’s consider this one: you’re starting to max out on your singe server installation. The one axiom you will note in any system performance recommendation chart is that you can never have enough RAM, fast enough processors, or fast enough disk subsystems to support everything on one system. So what in general should you scale out to? It really depends on what components in the Team Foundation Server are the heaviest used. For a lot of people, that ends up being the SharePoint Sever. After that move your databases to a separate SQL Server and Reporting Services server. Now I covered a very select scenario here, and yours may be different. For more advanced considerations I’d highly recommend reading up on Team Foundation Server performance recommendations in the Visual Studio ALM Rangers guide here http://vsarplanningguide.codeplex.com/ .

In case everyone is wondering why I’ve been light on the blogging lately, this is it.  Just got done with publishing my first book with Packt Publishing.  It is titled Team Foundation Server 2012 and Project Server 2010 Integration How-to, and is available on Amazon here: http://www.amazon.com/dp/1849688540/?tag=packtpubli-20

The publisher also wanted me to share this link http://bit.ly/ZulWBG but it really will just bring you to their site for an ebook only ordering page.  I’ll post some excepts from the book here as well as some cool info the the MVP 2013 Global Summit.

Just got back from the 2012 Microsoft MVP Global Summit in WA.  While the Windows 8 Consumer Preview got most of the media attention, as an MVP in ALM my attention was on what Microsoft was doing with Team Foundation Server 11 and Visual Studio 11.  Some of what we learned on future direction was covered under strict NDA, but we are allowed “released” info, which in this case is the VS 11 / TFS 11 beta.  So as always, your mileage may vary a little since I’m basing this off the beta.

Overview

There is a lot to be excited about for all the roles in an organization in the new releases.  Developers and Testers will be especially pleased, but I wanted to cover some the new items that Project Managers and Product Owners will be particularly excited about.  Though certainly a developer centric toolset, Microsoft is starting to realize that getting world class software products out the door requires more than just well equipped developers, and they want Visual Studio to be at the core of it.

First the Upgrade

A quick note here on the Upgrade.  I upgraded one of my combination TFS2010/VS2010 virtual machines right in the Summit (figured I could get some help that way if anything popped up ).  My only surprise here was I needed to fully uninstall TFS before continuing.  This is one of the reasons you always need to have a solid machine and DB backup before attempting this.  I would have figured the upgrade wizard could have handled this, and a roll-back if it failed, but its just something to keep in mind.  If you are working on a scaled out TFS installation, you will need to touch each server.  I’d never recommend running out and upgrading a production TFS instance on a beta release but it is encouraging that Microsoft will be supporting that upgrade path right through to RTM release though.    I’ll cover more details of the upgrade process in another post.

Deeper into Agile

One encouraging theme I picked up on while at Microsoft was an definite embracing of Agile and Scrum specifically.  Anyone who has used TFS for any length of time knows you can configure it for almost any process, however who wants to spend the time doing this for each team you work with.  If you are one of the many organizations jumping on the Agile/Scrum bandwagon (if you aren’t you should ask why) you’ll be very happy with this release.  The Visual Studio team has put out upgraded Scrum, Agile, and CMMI Process Templates (final names not decided, but in beta its Microsoft Visual Studio Scrum 2.0 – Preview 3, for the new Scrum one and MSF for Agile Software Development 6.0 – Preview 3).  If you are starting out with a new Team Project you’ll get to dive right into the new stuff, but as in the last release, if you are working with a 2010 project you’ll need to do some import / export work in the Process Template Editor.  The good news is though you can continue with your existing template until you are ready. I’ll cover the template upgrade process in a later post.

Sprints, Backlog Management, Burndowns, Task Boards and Teams

These sets of features should get you excited if you run software development projects.  Sure we had some of these in TFS2010, but you had to work with a combination of Work Item configuration and some spreadsheets (Iteration Backlog, Product Planning) that were shipped originally with the old Agile template and had some serious bugs in them. 

Now all of this functionality is in the core product and fully accessible from the new Team Web Access web site and Visual Studio, with drag and drop support.  What this means is if you are starting out a new Team and Team Project this wont take you hours of work like it used to.  I’ll add some screen shots of these here shortly.  If you were already using the Agile or Scrum template and customized your User Story work item you may have some adjustments to make with the new template.  Same situation if you went wild with States.  The new Template really only supports 3 of them, you’ll  need to map to these.

The Task Board is a brand new item.  If anyone has looked at VersionOne’s task board, then this one will look real familiar.  Basically it is an electronic Story Board or Kanban board for instant status on where your User Stories and supporting Tasks are at.

Also new are the support of product teams.  This allows the proper status of the Tasks as they may relate to multiple product teams.  Again this is something we can configure right in Team Web Access.

Storyboarding

Another new tool on the horizon is the Storyboarding Power Point plug in.  This item warrants its own post, but in summary it will allow an analyst (i.e. a non-programmer) to put together an animated collection of proposed product screens quickly to avoid the dreaded “that’s not what I wanted” statement.

I’ll be adding to this post as I get more screen shots and the rest of my notes together from the MVP summit.

The Team Portals in TFS 2010 were a huge bonus for any PM or Scrum Master looking to point stakeholders and teams to one spot for critical project communication and documentation.  The Team Portals are designed at a Team Project level. The problem you quickly run into with the Team Portals however if you further divide your Team Projects up by Areas for each solution.  You could certainly customize the templates or use the API to develop a tool to do solution level portals but that may be more work than you really want to do.

If your Team Project is already created, and you really need a portal for each area, the simplest solution would be to just manually create a portal using the sam design elements (very easy), copy the reports folder to a new one for just your area (to cusomize later) and create a team query to display the common lists by area and set the lists to use these. If you need to set the burndown (if you are using an Agile process template) to just use that area you'd need to also change the default filter on SSRS reports to reflect just the area you need.

I will update this post in the future with some specific instructions for doing this.

I get this question a lot, usually from a “pilot” project that turns into more and needs to fall under enterprise configuration guidelines. 

About half the problems I see with installs / re-configurations end up relating back to the accounts not set up properly for the tiers so please check the install guide to make sure your service accounts have the correct rights before you do this next step. Changing the accounts in TFS 2010 is relatively simple and the instructions are located here: http://msdn.microsoft.com/en-us/library/bb552178.aspx

You can either use the GUI or the command line TFSConfig. Instructions for both are located at that MSDN link. I summarized the TFSConfig instructions here:

To use the TFSConfig utility to change the service account

1. On the application-tier server, open a Command Prompt window and change directories to the directory that contains the TFSConfig utility.

   By default, this utility is located in Drive:\Program Files\Microsoft Team Foundation Server 2010\Tools.

2. At the command line, type:
   TFSConfig Accounts /change /accountType:ApplicationTier
   /account:AccountName /password:NewPassword, and then press ENTER.

I recently got a question on this and it seemed useful enough for a post to my blog.  They installed TFS without initially integrating with SharePoint. They had many projects that don't contain SharePoint portals. Then they integrated SharePoint with TFS and can only set up a SharePoint portal with new projects created. Is there any way to create a SharePoint portal for existing TFS projects? Are there any workarounds to achieve this goal?

The answer is yes and yes, and there are a few options to get this done:

Depending on how many you have to do there are two basic approaches that I've used. To begin you need to be in the Project Administrators group or have the View Collection-Level Information and Edit Collection-Level Information permissions set to Allow.

Manual Method, good if you just have a few. Follow the instructions one MSDN here: http://msdn.microsoft.com/en-us/library/dd386320.aspx . Basic steps are:

1.In Team Explorer, right-click the name of the project, point to Team Project Settings, and then click Portal Settings.
2.On the Project Portal tab, select the Enable project portal check box.
3.Click Use this SharePoint site, and then click Configure URL.
4.In the Web application list, click a SharePoint Web application.
5.In Relative site path, type the relative path of an existing SharePoint site.As you type the path, it appears at the end of the value in URL.
6.In URL, click the link, verify that the path is correct, and then click OK.
7.If you want this SharePoint site to show data for this project, select the Reports and dashboards refer to data for this team project check box.
8.Click OK.

Scripting with File.BatchNewTeamProject, more complex but creates the reports as well and good if you have a bunch to do at once. I did a few hundred in fairly short order using this method. Follow the detailed steps here http://msdn.microsoft.com/en-us/library/ff462695.aspx .