In this post, we’re going to install SharePoint Server 2013 on the same server as TFS and SQL Server.
We’re going to install SharePoint after we install SQL Server, so that we can use the same Database Engine instance we installed for TFS for our SharePoint deployment (although using the same SQL Server instance for both SharePoint and TFS is certainly not a requirement).
In most single-server TFS installations, you would simply use the TFS installer to setup SharePoint. However, TFS 2012 comes with SharePoint Foundation 2010, which is not compatible with Windows Server 2012. So we’re going to have to manually install a version of SharePoint compatible with Windows Server 2012.
TIP: Installing SharePoint on the same server as TFS isn’t a requirement. TFS is very flexible with regard to the topology of your SharePoint installation. See What If I Already Have SharePoint?
Do I Even Need SharePoint?
Maybe. SharePoint is a collaboration website product that offers deep integration with Office productivity products like Word, Outlook and Excel. Although it’s not a TFS requirement, some teams do find its features useful. SharePoint is different from the Team Web Access site that comes with TFS. Team Web Access is a web site that mirrors Visual Studio features and offers functionality for certain specialized team collaborations that have to do with creating software projects. You get Team Web Access by default when you install TFS.
What Will I Need?
Assuming you still want SharePoint in your TFS deployment, you’ll need a single domain account to act as the TFS Report Reader account. TFS uses this account to generate reports. We’re going to use the report reader account that way too, but we’ll also put it to use as the Farm Administrator account for our SharePoint installation, just as TFS would do during the standard install of TFS on Windows Server 2008 or R2.
TIP: Don’t put the report reader account in the Windows Administrators security group. It just needs the Allow log on locally permission, which all domain accounts have by default.
Free SharePoint vs. Paid-For SharePoint
For each version of SharePoint, Microsoft delivers a free version and a paid-for version with additional functionality. TFS always comes with one of the free versions. However, we support both versions and the instructions for installing either on Windows Server 2012 are very similar and included in this guide.
If you use SharePoint Server, as we are going to in this guide, you must make a few SharePoint configurations after you install SharePoint (and before you install TFS) to enable TFS dashboard functionality on your SharePoint installation. If you install the free version, you can skip the dashboard configurations. You’ll still get some dashboard functionality, but not as much as if you had the paid-for version of SharePoint.
What If I Already Have SharePoint?
If your existing SharePoint installation meets the TFS requirements for SharePoint, you can certainly use your existing installation of SharePoint for TFS. Make sure it meets the SharePoint requirements for TFS.
TIP: You can use a remote SharePoint installation—an instance of SharePoint that is not installed on the TFS server—but to do this you’ll need to install the TFS extensions for SharePoint on the SharePoint server. See (on MSDN): How to: Install Remote SharePoint Products for Team Foundation Server.
To perform this procedure, you must be a member of the Windows Administrators security group on the computer where you install SharePoint Products and where you host its databases.
To install SharePoint 2013 Products for TFS
Whatever SharePoint 2013 product you’re installing, you should first run the SharePoint 2013 Products preparation tool. After you prepare the server, install SharePoint, and then do the post installation configuration tasks appropriate for the product you just installed.
Remember that you’ll need a single domain account to act as the TFS Report Reader account to install SharePoint Server 2013. See What Will I Need?
Run the preparation tool
1) Insert the SharePoint Server 2013 DVD and launch default.hta, or download SharePoint Foundation 2013 and run sharepoint.exe.
You can find more detailed information about SharePoint requirements for Team Foundation Server on MSDN, but this instruction will guide you through typical installations on Windows Server 2012.
2) Choose Install software prerequisites.
3) On the Welcome page, choose Next.
4) On the license agreement page, accept the terms of the license and choose Next.
Depending on the state of your computer, the installer might prompt you to restart the machine. Follow any instructions.
Upon resume after a restart, you may have to run the SharePoint Products prep tool again, if it doesn’t start automatically. Keep running it (performing the previous four steps for manual restarts) until you get a success message.
5) At completion, choose Finish.
Run the SharePoint installation
Once the SharePoint Products Perpetration tool completes, you might have to launch the SharePoint installer again, especially if you had to restart your computer.
Remember that you’ll need a single domain account to act as the TFS Report Reader account to complete this section. See What Will I Need?
1) Insert the SharePoint Server 2013 DVD and launch default.hta, or run sharepoint.exe (for SharePoint Foundation installations).
2) Choose Install SharePoint Server this time (or Install SharePoint Foundation).
If you are installing SharePoint Server, type your product key, and choose Continue.
3) On the Read the Microsoft Software License Terms page, read the agreement. If it is acceptable, select the I accept the terms of this agreement check box, and then choose Continue.
4) On Server Type tab, choose Complete.
5) Choose Install Now.
When the installation wizard finishes, a dialog box appears that prompts you to complete the configuration of your server.
6) In that dialog box, verify that the Run the SharePoint Products and Technologies Configuration Wizard now check box is selected.
7) Choose Close to start the configuration wizard.
8) On the Welcome page, choose Next.
NOTE: A warning about restarting certain services will appear. Choose Yes. Some services might need to be restarted during the configuration phase.
9) On the Connect to a server farm page, choose Create a new server farm, and then choose Next.
10) On the Specify Configuration Database Settings page, perform the following steps and then choose Next:
A) Type the name of the server that is running SQL Server. Accept the default value for database name.
TIP: If you used a named instance in step 11 of SQL Server install, type the named instance here. For example, timel-s12-01\InstanceName.
B) Type the name for the report reader account and its password.
TIP: You can use the same account here that you will use for the report reader account.
11) Type a password in Passphrase, confirm the password by typing it again in Confirm Passphrase, and then choose Next.
12) On the Configure SharePoint Central Administration Web Application page, select the Specify port number check box, and type 17012.
You can use the randomly generated port number, but Team Foundation Server has always used 17012 as the port for the SharePoint Products administration site.
13) Choose NTLM and then Next.
14) Review the information, and then choose Next.
15) Choose Finish.
Once the installation routine finishes, it launches the SharePoint administration site, open to the initial configuration wizard.
Run the SharePoint Configuration wizards
No matter which version of SharePoint you install, you must run the SharePoint Configuration wizard. Special instructions appear in step 3 if you’re installing the Enterprise edition of SharePoint Server 2013.
1) Choose Start the Wizard.
2) Select Use existing managed account and choose the report reader account.
3) If you’re installing SharePoint Server Enterprise edition, as we are, then you’ll need to select Excel Services and Secure Store Service.
TIP: Secure Store Service is optional, but you should select it.
If you’re installing the Standard edition of SharePoint Server 2013 or SharePoint Foundation, none of the listed services are required, but you must run the wizard to succeed with your TFS installation. Even if you select no services, SharePoint will configure a site collection and some other services.
Select any services you want to set up. Unselect any you don’t want set up.
SharePoint selects all of them by default.
TIP: Remember that you can always come back later to run the configuration wizards, but you have to run it once after the SharePoint installation to succeed with your TFS installation.
4) Choose Next.
3) Type a Title and choose Next.
4) Choose Finish.
Configure Excel Services (SharePoint Server 2013 only)
For TFS reports to operate correctly, you must also configure a trusted file location for Excel Services.
1) In SharePoint Central Administration, under Application Management, choose Manage service applications.
2) On the Manage Service Applications page, choose Excel Services Application.
3) On the Manage Excel Services Application page, choose Trusted File Locations.
4) Choose Add Trusted File Location.
5) In Address, enter the URL of the root site of the web application that you will use with Team Foundation Server.
You should specify the web application that you created for Team Foundation Server.
6) In Location Type, choose Microsoft SharePoint Foundation.
7) In Trust Children, select the Children trusted check box.
8) In the External Data section, under Allow External Data, choose Trusted data connection libraries and embedded.
9) (Optional) Clear the Refresh warning enabled check box.
10) In Maximum Concurrent Queries Per Session, change the number to 20 and choose OK.
The trusted file location you just created appears in the Excel Services trusted file location list.
Configure secure store service (SharePoint Server 2013 only – optional)
To configure the secure store service, you must create a target application for the secure store.
1) In SharePoint Central Administration, under Application Management, choose Manage service applications.
2) On the Manage Service Applications page, choose Secure Store Service.
3) Choose New to create a secure store target application for Team Foundation Server.
TIP: If you have not created a key, SharePoint Products prompts you to create one by choosing Generate New Key. Without a key, you cannot create a target application for the secure store.
4) On the Create New Secure Store Target Application page, in Target Application ID and Display Name, enter TFS (pictured below).
TIP: You do not have to use TFS for Target Application ID or Display Name, but take note of whatever you use here, because you will need it to configure Team Foundation Server later.
5) In Contact E-mail, type the e-mail address of the person or group you want email messages about this application to be sent to (pictured below).
6) In the Target Application Type list, choose Group (pictured below).
7) In Target Application Page URL, choose None (pictured below), and then choose Next.
8) In Specify the credential fields for your Secure Store Target Application, choose Next to accept the default settings for the credential fields.
9) In Target Application Administrators, type the administrative account for the application.
10) In Members, enter the global security group from the domain that contains all the users to whom you want to grant access to dashboards and reports in Team Foundation Server, and then choose OK.
11) On the Secure Store Service Application page, select the check box for the target application that you just created (named TFS if you used the naming guidance that was provided earlier in this topic), and then choose Set Credentials in the ribbon.
12) In the Set Credentials for Secure Store Target Application (Group) dialog box, enter the name and password, confirm the password of the report reader account for Team Foundation Server, and then choose OK.