Upgrade TFS 2010 to TFS 2012 with Migration to a New Hardware – Part 4 – Install TFS 2012 Update 1 & Backup DBs and Reporting Key

In this blog series I start to explain step-by-step tutorial on how to upgrade existing TFS 2010 to TFS 2012 Update 1 with the migration to a new hardware, the series will include videos and images as well. In the last post I will include one video that collect all parts for one-shot view, this series consist of following parts:

• Part 1 – Introduction.
• Part 2 – Prepare SharePoint for the new system.
• Part 3 – Prepare the new machine and install SQL Server.
• Part 4 – Install TFS 2012 Update 1 & Backup DBs and Reporting Key.
• Part 5 – Restore DBs and Reporting Encryption Key.
• Part 6 – Configure TFS 2012.
• Part 7 – Verify upgrade success and other configuration.
• Part 8 – Upgrade TFS 2012 Build Service.
• Part 9 – Summary.

Each part consist of one or many sections as needed.

============================================================================

Part 4 – Install TFS 2012 Update 1 & Backup DBs and Reporting Key

• Install TFS 2012 Update 1 and run windows update.
• Run TFS 2012 Backup Tool and backup the old DBs.
• Backup the old Reporting Service Encryption Key.

The following is the video that explain this blog post.

 

Install TFS 2012 Update 1 and run windows update.

In this section I will explain how to install TFS 2012 Update 1 on a new machine, I will also make sure to run windows update for Windows and other Microsoft Products, it is very important to run any update before the configuration of TFS components.

Insert the TFS 2012 Update 1 DVD into your driver.

Select I accept the license and terms and click Install Now.

After the installation complete close Configuration Center and navigate to System and click Window Update.

Install all available update and restart the machine if needed.

Run TFS 2012 Backup Tool and backup the old DBs.

There are some new tools come with TFS 2012 that used to Back up and Restore Data for TFS, so we will navigate to the folder of the tools and copy that path. “Program Files\Microsoft Team Foundation Server 11.0\Tools“.

Open the command line as administrator.

Type cd and paste the copied path.

Type TFSBackup and press enter.

The TFSBackup tool will launch, type the name of the old server (TFS2010), don’t connect, we need to stop the Firewall first on the TFS2010 machine.

Go to the TFS2010 machine and temporary stop the Firewall so the TFSBackup tool can connect to SQL Server DB.

Get back to TFS12UP machine and click Connect, the tool will retrieve and select by default all needed DBs, in the Backup Database to, type the path of the shared folder that we created earlier, of course we may don’t need WSS_Content as we will use another SharePoint Server but I prefer to take all, review that there are 7 DBs selected as the following image.

Review the success of the backup.

Backup the old Reporting Service Encryption Key.

Go to the TFS2010 machine and click Start and navigate to Reporting Service Configuration Manager.

Click connect to the TFS2010 and then click on Encryption Key tab, after that click on Backup button, in the File Location, type the path of the shared folder that we created earlier, type a password and re-type it again, remember you will use this password when we restore the key.

Review and make sure that the backup success.

Upgrade TFS 2010 to TFS 2012 with Migration to a New Hardware – Part 2 – Prepare SharePoint for the new system

In this blog series I start to explain step-by-step tutorial on how to upgrade existing TFS 2010 to TFS 2012 Update 1 with the migration to a new hardware, the series will include videos and images as well. In the last post I will include one video that collect all parts for one-shot view, this series consist of following parts:

• Part 1 – Introduction.
• Part 2 – Prepare SharePoint for the new system.
• Part 3 – Prepare the new machine and install SQL Server.
• Part 4 – Install TFS 2012 Update 1 & Backup DBs and Reporting Key.
• Part 5 – Restore DBs and Reporting Encryption Key.
• Part 6 – Configure TFS 2012.
• Part 7 – Verify upgrade success and other configuration.
• Part 8 – Upgrade TFS 2012 Build Service.
• Part 9 – Summary.

Each part consist of one or many sections as needed.

===========================================================================

Part 2 – Prepare SharePoint for the new system.

• Examine the existing TFS 2010 system and the new machine.
• Uninstall all TFS 2010 components.
• Install and configure TFS 2012 Remote SharePoint Extensions.

The following is the video that explain this blog post.

 

Examine the existing TFS 2010 system and the new machine.

In this section we will just examine the old system to review its current state. We will see that, there are three machines for our scenario, TFS2010, of course this is the TFS machine with all TFS components, TFS2010-DC, this is the Domain Controller machine and TFS2012-Upgrade, this the new machine that will be used to migrate and upgrade TFS 2010, see the following image.

The first machine has the following information, VM name (TFS2010-DC), computer name DC08.com, it has Active Directory and DNS, it also has the needed TFS Service Accounts configured with all settings and needed permission for all TFS configuration, for more information about how to create TFS service accounts, click here.

The second machine has the following information, VM name (TFS2010), computer name TFS2010, it has MS SQL Server 2008 R2 SP1 Enterprise Edition, with Analysis Service and Reporting Serveries, it also has MS SharePoint Server 2010 and it is configured with excel service for reporting, see the following images.

TFS 2010 configured with SharePoint 2010, Reporting Service and  Build Serveries 2010.

MS SQL Server 2008 R2 with Analysis Service and Reporting Service.

MS SharePoint Server 2010 with Excel Service.

Uninstall all TFS 2010 components.

In this section I will uninstall all TFS components.

Install and configure TFS 2012 Remote SharePoint Extensions.

In this section I will install Remote SharePoint Extensions from the TFS 2012 Update 1 DVD, because we will use this machine as a SharePoint Server to work with the new environment.

Insert TFS 2012 Update 1 DVD into your driver.

Navigate to Remote SharePoint Extensions folder on the DVD.

Double click on the SharePoint Extension installation file.

Select the check-box I accept the license and condition after that click Install Now.

When the installation complete the Configuration Center will appear, click on Start Wizard.

The Readiness Check will run, you may find warning like it needs 10 GB of RAM, it’s OK, it can work with less RAM especially it’s not on the same machine with the TFS, but of course it’s always better to have 10 GB of RAM.

Review the success of the configuration.

In the TFS Administration Console, click on Extension for SharePoint Products, select the existing TFS and click Modify access, we will not change anything now but remember that we will change that after we configure the new server (TFS 2012).

Install SharePoint 2010 with MS SQL Server 2012 on Windows Server 2012

When I start my journey of install Team Foundation Server 2012 (TFS) on Windows Server 2012 with MS SQL 2012, I knew that we can’t install SharePoint Foundation 2010 on Windows Server 2012, this by design and sure the Team Foundation Server (TFS) standard configuration will not be able to do that

And if we want to install SharePoint Server 2010 with Team Foundation Server (TFS) 2012 we have 2 options

1. Use Windows 2008 R2 so we can install SharePoint 2010 Foundation
2. Use SharePoint Server 2010  so we can be able to install it on Windows Server 2012

So I try to install SharePoint prerequisites but it fails and give me the following error

There was an error during installation.

The tool was unable to install Application Server Role. Web Server (IIS) Role. configuration error, installation skipped

This happen for many reason, for example most of the prerequeist not supported for Windows Server 2012 because some of them become part of the Windows Server 2012 and some of them become par of the MS SQL 2012 as we will see later in this post.
So I try to install SharePoint and skip the prerequiest  and I found the following errors

This product requires the windows identity foundation
This product requires Microsoft Sync Framework Runtime v1.0(x64)
This product requires Microsoft SQL Server 2008 Native Client. Install SQL Server 2008 Native Client and re-run setup.
Windows Features or Role Service required by this product are not enabled. For a complete list, refer to the link below.
This product requires Microsoft Filter pack 2.0
This product requires internet information services (IIS) 7.0 or higher, with ASP >NET v2.0 set to ‘Allow’ in the list of IIS Web Server Extensions.
This product requires the IIS 6 Management Compatibility component to install
This product requires Microsoft Chart Controls for Microsoft .NET Framework 3.5 to be installed.

For more info about MS SQL Server 2012

For more info about Windows Server 2012

So Windows Identity Foundation become a Windows Server 2012 Role, so we just enable this Role on Windows 2012 Server

Also the Reporting Service SharePoint add-in become a component in MS SQL Server 2012

Note: Only SharePoint 2010 SP1 supported for MS SQL Server 2012 and even if the installation success without SP1 the configuration will fail.

So the steps to install SharePoint 2010 Server on Windows Server 2012 with MS SQL Server 2012 will be as the following

• Install MS SQL 2012 with SharePoint add-in
• Configure some Windows 2012 Roles and Features manually
• Return specific Environment.Exit code
• Run SharePoint 2010 prerequiest  and install them from SharePoint 2010 Server SP1 (Only SharePoint 2010 SP1 support MS SQL Server2012)
• Install SharePoint 2010 Server SP1
• Set the default app pool to v 2.0 instead of 4.0 because this what SharePoint 2010 needs
• Configure SharePoint 2010
• provision the installation and configuration

Note: you may want to setup SharePoint 2010 with SQL Server 2012 on Windows Server 2008 R2, it’s OK, you can follow the same steps.

Here is the video of the installation

If you prefer to follow steps with screen shots, review the following steps

• Install MS SQL 2012 with Reporting Service for SharePoint add-in

• Configure some Windows 2012 Roles and Features manually

We will choose 2 Roles and 1 feature and for each Role we will choose it’s features and so the feature, we will choose it’s components

• Web IIS (Role)
• Application Server (Role)
• Windows Identity Foundation 3.5 (Feature)

• Return specific Environment.Exit code

We will just give installation what it need, it just check for exist code 1003 so we will give this to SharePoint installation app, this was provided by Steve, well done Steve, its really helpful, so we will download the exe or just compile the source and put it in System32 Folder

• Run SharePoint 2010 prerequiest  and install them from SharePoint 2010 Server SP1 (Only SharePoint 2010 SP1 support MS SQL Server2012)

• Install SharePoint 2010 Server SP1

• Set the default app pool to v 2.0 instead of 4.0 because this what SharePoint 2010 needs

If we didn’t set this the configuration will fail as the following

If this happen we will need to the change the app pool for crated pools related to SharePoint, after SharePoint configuration failed

Start SharePoint CA

• Configure SharePoint 2010

• provision the installation and configuration, just open CA

What’s New in TFS 2012?- Project Management Tool

In this series I will start introducing what’s new in Visual Studio 11 and Team Foundation Server 11 ( TFS 11) or as we expect to be Visual Studio 2012 and Team Foundation Server 2012 (TFS 2012)

1. Introduction
2. Project Management Tool
3. SSDT (SQL Server Developer Tool)
4. Team Explorer
5. My Work
6. Code Review
7. Suspend and Resume
8. Local Workspace
9. Pending Change
10. Diff and Merge tool
11. Unit Testing Improvement
12. Code Clones
13. Build Improvement
14. Storyboarding
15. Microsoft Feedback Client
16. Exploratory Testing Improvement
17. IntelliTrace in Production
18. Alerts
19. Administration

 

——————————————————————————————————————————————-

Project Management Tool

In this post I will talk about the following improvement in the Project Management tools for TFS 11 (Team Foundation Server )

1. Teams

2. Team Web Access For Agile Management

• Teams

What is team feature?

The team feature is the third dimension of the team project.

1. Iteration (Time Dimension)
2. Areas (Features or Module Dimension)
3. Teams (People Dimension)

Just think of a large project that has many teams, for example Team1 and Team2. Team1 has 2 weeks sprints but Team2 has 4 weeks sprints, each team has different day-off, different sprint delivery and daily stand up meeting and many others, remember that they share the same product backlog. So by introduced team feature, we can manage this different very easy, Wow it’s really awesome! So each team can has separate and different

1. Team members
2. Team favorite
3. Backlog
4. Burndown chart
5. Sprints
6. Days-off
7. etc.

If we don’t segment our team project into teams, all team capabilities are available for the team project, which acts as the default team. To understand team feature more, assume that there is nothing called team project any more, it’s just a team now and if you don’t create any so you are working on the default team (Which will be the team project) so the team project has at least one team by default and this is what we will work on.

Team feature supports small teams that work on different product areas to manage their backlog and iteration, separate from other teams. We define and manage team membership through Team Web Access. We manage team members through the Administration mode in Team Web Access.

For detailed explanation see the following video

 

Links:

What’s New in the Visual Studio Team Foundation Server

Understand Teams

———————————————————————————————–

• Team Web Access for Agile Management

There are a lot of improvement introduced in TFS 11 in Team Web Access, and I believe it become the first class citizen, at least for me! There is big improvement in performance and usability, to minimize the number of round-trips to the server, to make richer UI experience. There are a lot of small features but the most important new features are Backlog and Board pages, I will also explain the Home Page.

1. Backlog

2. Board

3. Home Page

• Backlog

We have many internal features in the Backlog like:

1. Drag and Drop to prioritize the PBI (Product Backlog Item) and assign them to sprints
2. Sprints divided into Past, Current and Future based on start and end date of the iteration and the current date.
3. Quick add PBI or Bugs to the Backlog
4. Real time velocity chart
5. Real time Burndown chart
6. Forecast where to assign our PBIs based on the estimated velocity

The Backlog page will enable us to manage our backlog of the whole product or the team project (Default Team) or any team inside the team project. Remember only the selected iterations (Sprints if we use Scrum process template) what will appear in the backlog page divided into 3 sections Past, Current and Future, this divide based on the iteration start and end date and current date Remember also to use Backlog feature we have to select at least one iteration and one area.

Note: To customize the Backlog page or days-off of team capacity we will need to customize the process template.

• Board

It’s the Agile digital wall, it support drag and drop and view from different dimensions like PBI/Bugs and team members, it also support member filter. First we have to notice that it’s a task board for PBIor Bugs, so we must have PBIand Tasks for this sprint

The parent level of the task (PBI or Bugs in Scrum) will appear as vertical data and all child task appear horizontal data beside it PBI or Bug, it will appear in 3 state, To Do, In Progress and Done (Scrum template)

Note: To make auto self-assigned for task, you have to choose your name from the person at the top right corner in the Board page.

• Home Page

The home page mainly to represent a way of shortcut of most activities we perform, so let’s see them from a high level view:

1. Create work items shortcuts
2. Work load vs. capacity of current Sprint (real time)
3. Burndown of current Sprint (real time)
4. Team Favorites (queries, build definitions, source control and branches)
5. Activities (shortcuts for several activities)
6. Members (shortcut to view and mange members)
7. Administration (shortcut to manage Iterations and Areas)
8. Recent project and teams (move from team to team)
9. Search work items (Note: use double quotation around your criteria) vote for this bug with me
10. Profile (email, picture)
11. Settings (iterations, areas, security, alerts, members) by default for current team

See the following image for identify each feature with it’s number.

For detailed explanation see the following videos

Part 1

Part 2

Part 3 (updated on 6/6/2012)

Links:

What’s New in the Visual Studio Team Foundation Server

Working with Tam Web Access

Agile Planing and Iterations

What’s new in Planning and Tracking

What’s New in TFS 2012?- Introduction

In this series I will start introducing what’s new in Visual Studio 11 and Team Foundation Server 11 ( TFS 11) or as we expect to be Visual Studio 2012 and Team Foundation Server 2012 (TFS 2012)

 

1. Introduction
2. Project Management Tool
3. SSDT (SQL Server Developer Tool)
4. Team Explorer
5. My Work
6. Code Review
7. Suspend and Resume
8. Local Workspace
9. Pending Change
10. Diff and Merge tool
11. Unit Testing Improvement
12. Code Clones
13. Build Improvement
14. Storyboarding
15. Microsoft Feedback Client
16. Exploratory Testing Improvement
17. IntelliTrace in Production
18. Alerts
19. Administration

 

——————————————————————————————————————————————-

Introduction

I perform the Team Foundation Server (TFS) 11 Beta upgrade from the day one of the Beta release, I read many blog articles, MSDN, I also saw many videos, so I will not re-invent the wheel by rewriting what I have read or view through out all the previous period, but I will put the main point of the new features or improvement and I will put my feedback and realization about these features.

So the first question why we upgrade specially that the RTM not released yet?

This always one of my main question all the time for any new technologies or framework, unfortunately my answer was far from what I believe now, I used to trust of my experience and my existing solution, but what I found? I found that all my solutions are out dated and there are elegant solutions there, perfect, fast, easy and I just missed all of them all the time, eventually I realize the truth! the world keeping change and there are always improvement and your perfect solution today will be the worst tomorrow

The new technologies means new features and enhance for the old, some people said and new bugs too! especially in the beta, absolutely right, but ……

It’s always what you get more and more bigger than what you face of issues or bugs and you know that if you really master your tools, it’s a long story to tell so enough talk and let’s see what I decide.

So this what I believed now!

This why the upgrade is a must for me and I always waiting for it and guess what? it has more than I expected