Guidance on configuring Team Foundation Server to create project sites under a SharePoint 3.0 subsite, enabling a central intranet portal with project dashboards.
I have managed to install SharePoint 3.0 on my dev Team server box in side by side mode by using Brian Keller’s blog on “ Configuring Visual Studio 2005 Team Foundation Server with Windows SharePoint Services 3.0 ”.
I have not yet updated Team Server, but I got as far as having a working version of SharePoint 3.0 running side by side with 2.0. This has worked grate for me as I have had time to evaluate SharePoint as an Intranet for my department. What I would like to achieve is to have and intranet site on http://department.internal.company.com with a sub site called “projects”. I would then like Team Server to create all of its sites under this Projects site so as to provide a mini portal for my projects with links to documentation, best practices and tools on the parent http://department.internal.company.com/Projects site along with a reporting services dashboard, with customer reports that cover all of the projects, like RAG reports among other things.
Does anyone know if this is achievable?
My idea is that in the documentation I replace:
<RegistrationEntries>
<RegistrationEntry>
<Type>Wss</Type>
<ChangeType>Change</ChangeType>
<ServiceInterfaces>
<ServiceInterface>
<Name>WssAdminService</Name>
<Url>[protocol]://[WSS Server 3.0]:[WSS 3.0 admin port]/_vti_adm/admin.asmx</Url>
</ServiceInterface>
<ServiceInterface>
<Name>BaseServerUrl</Name>
<Url>[protocol]://[ WSS Server 3.0]:[port]</Url>
</ServiceInterface>
<ServiceInterface>
<Name>BaseSiteUrl</Name>
<Url>[protocol]://[ WSS Server 3.0]:[port]/sites</Url>
</ServiceInterface>
<ServiceInterface>
<Name>BaseSiteUnc</Name>
<Url>[ WSS Server 3.0]sites</Url>
</ServiceInterface>
</ServiceInterfaces>
</RegistrationEntry>
</RegistrationEntries>
With the information for the sub site:
<RegistrationEntries>
<RegistrationEntry>
<Type>Wss</Type>
<ChangeType>Change</ChangeType>
<ServiceInterfaces>
<ServiceInterface>
<Name>WssAdminService</Name>
<Url>[protocol]://[WSS Server 3.0]:[WSS 3.0 admin port]/_vti_adm/admin.asmx</Url>
</ServiceInterface>
<ServiceInterface>
<Name>BaseServerUrl</Name>
<Url>[protocol]://[ WSS Server 3.0]:[port]</Url>
</ServiceInterface>
<ServiceInterface>
<Name>BaseSiteUrl</Name>
<Url>[protocol]://[ WSS Server 3.0]:[port]/**Projects**/sites</Url>
</ServiceInterface>
<ServiceInterface>
<Name>BaseSiteUnc</Name>
<Url>[ WSS Server 3.0]**Projects**sites</Url>
</ServiceInterface>
</ServiceInterfaces>
</RegistrationEntry>
</RegistrationEntries>
**Anyone else have a better idea of what to try?**
**Any reason what this should not work?**
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
Milliman
Bistech
Slicedbread
Boeing
Lean SA
NIT A/S
Kongsberg Maritime
Flowmaster (a Mentor Graphics Company)
MacDonald Humfrey (Automation) Ltd.
Big Data for Humans
Teleplan
CR2
Deliotte
DFDS
SuperControl
Freadom
Qualco
Workday
New Hampshire Supreme Court
Nottingham County Council
Department of Work and Pensions (UK)
Washington Department of Transport
Royal Air Force
Ghana Police Service
New Signature
YearUp.org
Boxit Document Solutions
Epic Games
Big Data for Humans
Emerson Process Management