In new deployment scenarios you will need the TFS 2013 or 2012 on an windows 2012 R2 server, that will never support SharePoint 2010, so we need an SharePoint 2013 SP1, that support windows 2012 R2 for now.
Before Run all Windows Updates before installing SharePoint 2013, and get the CU updates of Sql2012 sp1 and SharePoint 2013 Sp1 .
If That box already has TFS 2013 on an windows 2012 R2 server . by Installing updates are the key steps that will prevent tantrums from SharePoint . Always, install of the required updates and ideally the optional ones also.
installation of SharePoint 2013 with Sp1
SharePoint Team They have really slicked up the installation process for SharePoint,
Instead use the auto-run that comes from running the DVD directly, or you can just run the “prerequisiteinstaller” from the root first.
When the prerequisites are complete you can start the installation proper and enter your key . If you get this wrong you will be next completing an uninstall to pick the right option. You can Avoid express at all costs and in this case we already have Team Foundation Server 2013 Sp1 installed and already have SQL Server 2012 sp2 installed.
Using configuration wizard will lead you through the custom config but if you are running on a local computer with no domain, like me, then you will have to run a command line to generate the database before you proceed.
Well, do not dispair because PowerShell –as always – is your friend. So just start the SharePoint 2013 management PowerShell console and use the cmdlet :
We have now a farm we can complete the configuration. Just work though the wizard as , although you are on your own if you select kerberos for single sign-on.
SharePoint 2013 SP1 will then run though its configuration steps and give you a functional, but empty SharePoint environment. At the end you get a simple Finish button and some instructions that you need to follow for getting your site to render in a browser.
Info: SharePoint 2013 works now in Chrome and other non Microsoft browsers…
Now you get almost 25 services that you can chose to install or not. If you leave them all ticked then you will get about 10-12 new databases in SQL, Its too hard to figure out what the dependencies are and what you need .
Configuring processes and extending can be long and will add solution into SharePoint. Will be a site template added but as it will likely look the nice new SharePoint 2013 Sp1 interface we will need to create the site manually.
Now that the SharePoint bits have been setup we will have a default link setup between SharePoint and Team Foundation Server. Although if we had a separate Team Foundation Server instance we would need to tell it where the TFS server is.
Info: You have to install the Extensions for SharePoint Products on every front end server for your SharePoint farm.
SharePoint 2013 Web Applications Configuration in Team Foundation Server 2013
Now we have installed and configured the bits for SharePoint as well as telling it where the TFS server is we now need to tell TFS where to go.
There is no account listed as an administrator! I am using the Builtin\Administrator user as both the TFS Service Account and the SharePoint Farm Admin you don’t need one.
Site Configuration Collections
In order to have different sites for different collection and enable the ability to have the same Team Project name in multiple collection then you need to create a root collection site under the main site. Some folks like to create this at the ^/sites/[collection] level, but I always create the collection site as a sub site of the root. This have the benefit of creating automatic navigation between the sites…
This final test as when you click OK the Admin Console will go off and try to hook into, or create a site for us. if you do want to have a greater degree of separation between the sites and have them in different collections you can indeed do that as well. You may want to do that if you are planning to separate collection to multiple environments, but I can think of very few reasons that you would want to do that.
Using the new Team Project Site
If we create a new team project the template from the Process Template that you selected will be used to create the new site. These templates are designed to work in any version of SharePoint but they may look cool.
This team project was created before there was ever a SharePoint server so it has no portal. Lets go ahead and create one manually.
They have moved things around a little in SharePoint and we now create new sub sites from the “View Content” menu.
This, while much more hidden is really not something you do every day. You are much more likely to be adding apps to an existing site so having this more clicks away is not a big deal.
When we care the new site we have two options. We can create it using the provided “Team Foundation Project Portal” bit it results in a slightly ugly site, or you can use the default “Team Site” template to get a more native 2013 feel.
This is due to the features not yet being enables… so head on over to “cog | Site Settings | Site Actions | Manage site features” to enable them.
You can enable one of:
- Agile Dashboards with Excel Reporting – for the MSF for Agile Software Development 6.x Process Template
- CMMI Dashboards with Excel Reports – for the MSF for CMMI Software Development 6.x Process Template
- Scrum Dashboards with Reporting – for the Visual Studio Scrum 2. Recommended Process Template
The one you pick depends on the Process Template that you used to create the Team Project. I will activate the Scrum one as I used the Visual Studio Scrum 2.0 Recommended Process Template which I heartily recommend. You will have noticed that here are 2 or 3 for each of the “Agile | SMMI | Scrum” monikers and this is due to the different capabilities that you might have. For example:
- Agile Dashboards – I have TFS with no Reporting Services or Analysis Services
- Agile Dashboards with Basic Reporting – I have Reporting Services and Analysis Services but not SharePoint Enterprise
- Agile Dashboards with Excel Reporting – I have Everything! Reporting Services, Analysis Services and SharePoint Enterprise
If you enable the highest level of the one you want it will figure out the one that you can run and in this case I can do “Scrum Dashboards with Reporting”.
Scrum template does not have any built in Excel Reports, but it does have Reporting Services reports. Now when I return to the homepage I get the same/similar portal you would have seen in old versions of SharePoint 2010.
Team Foundation Server 2013 & 2012 works with SharePoint 2013 Sp1 on Windows server 2012 R2 and we have manually created our Team Project Portal site.