upgrading SharePoint 2007 master page to SharePoint 2010 - sharepoint-2007

I am getting ready to upgrade a SharePoint 2007 Master page to a SharePoint 2010 master page. Does anyone have any experience doing this? I could use some suggestions on how to finish the upgrade smoothly.
Thanks

Check out: Upgrading an Existing Master Page to the SharePoint Foundation Master Page

Related

Unable to see documents in Team Explorer 2013 after upgrade

We have upgraded TFS2008 to 2013 on a new server and source control/workitem tracking is okay - we can use all that from within VS2013 Pro.
We have also upgraded Sharepoint (containing all the project documentation) to a new database server and using the TFS 2013 Adminisration Console we can see the Team Projects listed there.
However although from the VS2013 Team Exlorer we can add the team projects and open the 'web portal' for each team project, we cannot see any of the documents nor can we (seemingly) view in a browser the portal that in VS2008 shows the document libraries.
Are we missing something in the unfamiliar interface, or can anyone advise what the cause might be and how to fix it?
You need to "wire up" the Team Projects to the Sharepoint sites. It sounds like they have been detached through the order of the upgrade.
Sharepoint needs to be upgraded and available during the upgrade process or this happens
You can however easily wire them back up. In the Team Project in Visual Studio go to the Team Explorer and do "Settings|Portal".
You should have a dialog for wiring up The existing Sharepoint to the Team Project.
If you don't you may have Tbeen disconnected at the collection level. In which case you can open the TFS Administration Console and follow: http://nakedalm.com/integrate-sharepoint-2013-with-team-foundation-server-2013/

Finding the URL for Basic installation in TFS 2013

Hi I am very new to TFS and have not installed it before. I just installed TFS 2013 using the Basic Installation that was given in the wizard. Everything is done and the installation is complete. It has created a new Server in SQL Server and hs opened up the TFS Admin Console. All the details for the server and the collections are shown here, but when I try to connect to the server from visual studio it does not connect. It says server unavailable. The state in the TFS Admin console is "Online". I am not able to modify the url in the TFS Admin Console too. I am really not sure what is going wrong here and what should be done. Am clueless about the next step. Any help is appreciated.
Thanks
In a web browser or in the Connect dialog in VS, it is http://<ServerName>:8080/tfs/
You can find instructions for both the web and VS on MSDN.

Can't connect to upgraded TFS 2008 Project Collection in TFS 2012

I have successfully installed TFS 2012 and migrated my TFS 2008 databases into TFS 2012. From within Visual Studio I am able to connect to the new TFS server through my source control plugin and can see all of the projects that were imported from TFS 2008. The problem is that when I click 'Connect' I am getting an exception that an HTTP 500 error has occurred. On the server I am getting a warning in the Event Viewer because of this URL:
http://[servername]:8080/tfs/tfs2008projectcollection/services/v3.0/locationservice.asmx/TeamFoundation/Administration/v3.0/LocationService.asmx
If I manually go to the above URL minus '/TeamFoundation/Administration/v3.0/LocationService.asmx' the page loads fine. Additionally if I remove '/tfs2008projectcollection/services/v3.0/locationservice.asmx' and navigate to http://[servername]:8080/tfs/TeamFoundation/Administration/v3.0/LocationService.asmx the page loads fine.
Thing is this only happens with the project collection that I imported from 2008. I created a new project collection directly in TFS 2012 and I can connect to that project just fine within VS 2012. Has anyone ran into this issue and, if so, what is the best way to correct it?
It is unclear what caused / is causing this problem but after a TFS server reboot the issue is no longer manifesting itself.
I'm am also having this issue. I have Update 4 and this is a fresh machine. I see the issue here, have tried the fix and no luck. I've also tried a reboot with no luck. I see the issue here and it appears that Microsoft's only suggestion is to 2013. Unfortunately they do not supply a migration path directly between 2008 and 2013, so I have to cross my fingers and hope that upgrading the machine after importing from 2008 even with the error will solve the issue.
Can anyone confirm the issue is actually resolved in 2013?

TFS 2010 Project portal shows "Login failed for user <DOMAIN>\sharepoint.admin" error message. How do I fix this?

At the bottom of every project portal dashboard page for my newly created TFS 2010 project portal (MSF Agile v5.0 template) I get the message "login failed for [DOMAIN]\sharepoint.admin" (see picture)
If I edit any of the dashboard pages (site actions of edit page) this message is still there, but not inside a web part which leads me to belive this is not a web part that is showing this message. But what is it? More to the point what do I need to do to fix it?
I presume I have some permissions or configuration issues, but currently both I and my companies internal support people are without a clue as to how we go about diagnosing never mind resolving this issue.
It should be pointed out that i/we are TFS 2010 newbies AND sharepoint 2007 newbies.
Any help would be much apreciated.
Thanks for the solution Roel (aswered via sharepoint stack overflow site).
Setting sharepoint.admin as a TFS contributor seems to have done the trick; once enough time was elapsed to have the warehose refresh.

TFS 2008 to TFS 2010 upgrade to exclude sharepoint

I'm currently planning to upgrade our TFS 2008 server to TFS 2010 with the condition below:
1. upgrade everything except for the sharepoint
2. upgrade everything including sharepoint but sharepoint will be enabled only at later stage. will this stop us from using TFS for our development?
Thanks,
Chen
Sharepoint shouldn't be a requirement unless you have a strong need to have project portals. Everything else (workitems, source repository, etc. should work fine).

Resources