Licensing needs for Team Build Server

I decided to write a short post about licensing of Team Build Server environments because I was asked several times in the past. There’s a good chapter in the Team System Licensing Guide which explains it in detail.

If you want to run Static Code Analysis or automated Tests you need to install Visual Studio Team System on the build server. For this Team System installation you don’t need any additional licenses as far as your developers have an appropriate license to do the specific task (extract from Licensing Guide):

Team Member Actions Licensing Implications
Developer checks-in source code. Team Foundation Sever CAL required.
Developer defines a team build type to include any of:
- Unit Testing
- Code Coverage
- Code Analysis
Team Edition for Developers or Team Suite is required.
Tester defines a team build type to include any of:
- Generic Testing
- Web Testing
- Load Testing
- Manual Testing
Team Edition for Testers or Team Suite is required.
Team member initiates a build. Team Foundation Sever CAL required.

Conclusion:
If you (=developer) only have a Developer Edition installed and queue a new Team Build, you don’t need any additional licenses. Only if you want to modify or create such a build definition.

The build server do not need any licenses (included in Team Foundation License), only the developers who working on it!

Team Foundation Server 2008 installation – Errors Part 1

This is the first post about errors which can occur when installation TFS 2008.

Event log entry information:

Source: DCOM
Event ID: 10016
User: domain\tfsservice
Description: The application-specific permission settings do not grant Local Activation permission for the COM Server application with
CLSID {61738644-F196-11D0-9953-00C04FD919C1}
to the user domain\tfsservice SID (…). This security permission can be modified using the Component Services administrative tool.

Reason:
This happens after installing SharePoint Services 3.0. The CLSID is used by the service “IIS WAMREG admin Service” and the tfsservice Account needs to have the local activation right on this service.

Solution:

  1. Open “Administrative Tools” > “Component Services”
  2. Expand nodes “Computers” > “My Computer” > “DCOM Config”
  3. Locate entry “IIS WAMREG admin Service”
  4. Right click > Properties
  5. Tab “Security” > “Launch and Activation Permissions” > “Edit…” Button
  6. Add tfsservice Account if not already present and grant permissions “Local Launch” and “Local Activation”

MSF Agile Process – Checking in with Task Work Items closes them by default

If you’re checking in source files that are associated with task work items the default action is set to “Resolve”. This means that the work item is closed after the check in. But often you don’t have such granular work items that they can be resolved by one check-in, in bug work items this is rather the appropriate action.

To get lesser problems, this behavior should be changed. Unfortunately it’s not possible to change the default to “Associate” so you need to remove the “Resolve” action. This can be done by editing the work item template. A description to do that was posted by Martin Woodward in TFS Top Tip #3.

Installing SQL Server 2005 after Visual Studio 2008

Recently, I was installing Visual Studio 2008 on a fresh Windows Vista installation with standard options (including SQL Express Edition).
SQL Server 2005 wasn’t installed before but that’s what I did as next. Because I want to administrate my DB’s with the management studio I checked the “client tools” option in the setup.

So after installing everything, the setup shut a message that the client tools couldn’t be installed, because there’s an older version already installed.

Name: Microsoft SQL Server 2005 Tools Express Edition
Reason: Your upgrade is blocked. For more information about upgrade support, see the “Version and Edition Upgrades” and “Hardware and Software Requirements” topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.

Build version check:
Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.

The client tools which were installed by the Visual Studio blocking the setup tool to install the management studio etc. After some research in Google, I found the solution for this problem on the MSDN forums.

You need to start the setup from the command line with the parameter “SKUUPGRADE=1″ to force installing the newer versions of the client tools:

cmd>setup.exe SKUUPGRADE=1

SQL Server 2005 Developer Edition has no AdventureWorks DB by default

If you’re installing the developer edition of SQL Server 2005, you don’t get the sample database AdventureWorks even if you check the samples option in the setup.

So if you like to use the database in case of a sample application like EAP from Trivadis, you need to install it separately.

Ged Mead run into the same problem and posted the answer: “How To Install the AdventureWorks Database in SQL Server 2005 Developer Edition“.

Hello world!

Welcome to my new blog!
Because I wanted to try out some ASP.NET stuff and do some personal stuff, I now have my own domain. Most of the content about .NET will be mirrored to my company blog at:
http://blog.trivadis.com/blogs/nicolasmueggler

I’ll try to get my old posts from the company blog to also add here.

So have fun!