Udostępnij za pośrednictwem

TFS 2012 - Installing Remote SharePoint Extensions on a standalone SP server on Windows 2012

  • Artykuł

 

Issue

One of my friends had an issue with installing the Remote extensions for SharePoint which comes with the TFS 2012 media on a SharePoint 2013 (note only 2013 is supported on Windows 2012) that he had on a Windows Server 2012 machine. The SP 2013 is separate Windows Server 2012 instance, from the rest of the other TFS components. [also see my side-note at the end]

Testing

So I tested this out, by standing a Windows Server 2012, with SQL 2012 and then installed SP 2013 on it.

Following are not shown

1. Install Windows Server 2012
2. Install SQL 2012
3. Install SP 2013

 

 

Installing Remote SharePoint Extensions and configuring on a standalone SP 2013 Server using the TFS 2012 Media

The following are the screen shots showing the Remote SharePoint Extensions installation and configuration.

1. Launch the TFS Share Point Extensions

image

image

2. Install the Share Point Extensions all the way through

 

image 

image

image

image

 

3. SharePoint extensions successfully installed

 

image

 

4. Configuring the SharePoint Extensions

image

image

image

 

image

image

 

5. SP Extensions Configurations complete

image

image

6. Using TFS Admin Console to now wire up TFS to SharePoint

image

image

7. Wiring up TFS to SharePoint

In the below screen you will have to enter the correct details for the TFS Server URL and the SP Web Application.

image

 

 

 

Side-Note

I had run into previous issues when I was upgrading a 2010 TFS installation, (which used the default WSS 3.0 based SharePoint, which comes with the TFS 2010 media) as its SP content database. In that situation I had to overcome the problem whereby WSS 3.0 based content DGBs cannot be straightway upgraded to SP 2013 content DBs. One has to set up a standalone SP2010 Server, then do an interim upgrade of the WSS 3.0 content DB to SP 2010 based DBs, and then use these upgraded SP 2010 content DBs to be accepted by the SP 2013 installation. Anyway it was a bit of a pain, that one had to set up a separate server just because there is no straight upgrade path from WSS 3.0 to SP 2013.