I believe in Hyper-V!

Team Foundation ServerCategory Archives

About TFS Administration

Automatic Deployment of TeamCompanion through System Center 2012 R2 Configuration Manager

Last week I received a request from one of our customers about the options for automatic deployment of TeamCompanion to end users. In this blog post I would like to explain and show you how this can be achieved using System Center 2012 R2 Configuration Manager. As always, I’ll lead you through the procedure using lots of pictures :) .

Which prerequisite do we need to start our procedure? An Active Directory, the System Center 2012 R2 Configuration Manager, a couple of domain members, and goodwill.

Additionally, your developers need to prepare appropriate packages as follows:

1. SQLSysClrTypes.msi (download from here)
2. ReportViewer.msi (download from here)
3. Ekobit.TeamCompanion.Installer.exe
4. TeamCompanionSetup.exe

The order of the packages is important, so please create exactly in the order stated above.

If you don’t know how to create Applications and Packages here is a guide.

Do the same for the ReportViewer.msi, Distribute Content and Deploy applications.
Now we need to create three TeamCompanion packages with this order:
– TeamCompanionSetup /S /C
(where /S mean silent and /C is for a user)
– TeamCompanion /S

Do the same for the rest of packages, Distribute Content and Deploy applications.

After you have prepared all this, you are ready to implement your automatic deployment of TeamCompanion

Step 1.

Open the System Center 2012 R2 Configuration Manager console and go to Software Library|Applications and create two applications (Microsoft System CLR Types for SQL Server 2012 & Report Viewer) like in the picture.

After you have created Applications, you need to Distribute Content and you need to Deploy applications to the selected clients in the environment.

Step 2.

Create three packages (TeamCompanionInstaller.exe, TeamCompanionSetup /S /C and TeamCompanion /S).


You are finished on the System Center 2012 R2 Configuration Manager side. Let’s look the client side now!
On the client side, Outlook 2013 and Team Explorer 2013 must be installed to be able to push complete package installation of TeamCompanion.


Finally, open Outlook to access TeamCompanion features, connect to your Team Foundation Server and enjoy ;)


For more information about TeamCompanion please visit our web page www.teamcompanion.com

Enjoy the day ;)



Microsoft Conferences in April 2012 – MS Network 2.0 and WinDays 2012

This month was very exciting. I participated in two Microsoft conferences as a speaker with three lectures.

The first conference was MS Network 2.0 in Mostar (Bosnia and Herzegovina) 4. – 5. April. On the MS Network 2.0 I talked about what is new in System Center 2012 Virtual Machine Manager. The session was well attended, and grades at the end have been satisfying. Thank you all who attended my session.
Also, I would like to thank MS Network 2.0 team and very kind hosts for their hospitality Smile. It was great experience!

Few pictures from the MS Network 2.0 conference.


The second conference was WinDays 12 I Rovinj (Croatia) 23. – 27. April.

I had two sessions. My colleague Ivan Kardum and I had common lecture about Team Foundation Server and System Center 2012 Operations Manager. We talked about how to unite developers and administrators Smile… Trust me, it’s possible Winking smile.

On the second session, entitled “Administrators, remove the mask” I talked about bad admins and how an administrator can destroy the entire company. It was a great lecture, I started  with a mask on the face Smile.

I would like to thank WinDays 12 team and especially I’m grateful everyone who came to my sessions and supported me.

Few pictures from the WinDays 12 conference.


Hope to see you next year at the same conferences Winking smile.

Migrate TFS 2010 Project Collection to another TFS 2010 server

If you want to migrate one or more TFS Project Collections from one TFS server to another follow this procedure. Procedure is very important and if you skip any step your will have the problem. For that reason read and follow this article from beginning.

NOTE: You can’t to migrate Team Project only, you need to migrate whole Collection. With this process you migrate Work Items and Source Control only. In my second blog post I’ll write about how to migrate Reports and SharePoint sites. That is more complicated procedure.

Step 1.

Stop Team Project Collection which you want to migrate.


Step 2.

Detach Collection.


Step 3.

Open your SQL Server Management Studio and backup database which you want to migrate. Before backup I advice to shrink your database (log and data).


Step 4.

Copy database on to your new TFS server and restore to SQL server.


Step 5.

Open Team Foundation Server Administration Console go to Application Tier >>> Team Project Collections, click to Attach Collection and follow the Wizard.


Your restored database will appear.


Team Project Collection is attached but with warnings about Reporting, SharePoint Products and Lab Management. As I mentioned before, you can’t to migrate Reports and SharePoint site easy.

Migrated Team Project Collection is up and running.


Step 6.

Check your migrated Project/s.



That’s It!