September 2006 Entries
Claiming my blog in Technorati

So according to Technorati in order to claim my blog I need to add a little html tag to this blog entry.  This may get me more visitor, lets give it a try. 

Technorati Profile
Legacy Visual Studio Support in Vista

So, I've been reading a lot of blogs in the last few days about this and would like to put in my .02c

First off, I'm not going to tell you the SP beta is available since I think everyone on the planet did a great job at that... oh wait I just did as well ;-). Anyway register and get it on Microsoft Connect.

As for Legacy support of .Net and Visual Studio in Vista, I think Microsoft are doing the right thing here.  We are moving in the future with a new OS.  We have a VS that works with the current .Net version and the next one (until we get full support for Vista and the .Net 3.0 with Orcas).  Building software is a hard business, supporting legacy application is a very hard business, supporting massive amount of hardware, software and multiple version of OSes is an almost impossible business.  I think sometimes the hardest thing to do is letting go... but not entirely.  I am fortunate enough to be working with current and next gen technologies but not everyone is, I understand the pain and very much share it.  Is there a way out, well absolutely, use virtual technologies, can't get any cheaper, it's free (VirtualPC, Virtual Server, VMware Server).  Microsoft also stated

Install up to four copies of the operating system in virtual machines on top of Windows Vista Enterprise with a single license

So what does that mean, well when you run vista and the free Virtual PC (or Server) that you can "legally" run up to four other copies of Windows virtually.  Well then, why not install Windows XP and Visual Studio.NET or 2003 to do legacy development, anyone who knows me will tell you that I push virtualization anytime I can (I'm even giving a talk at the Code Camp, I have a podcast on the subject also here --watch out it's in french --).  I think virtualization is super important in our business and is a great way to 'lock down' a customer configuration do develop against.  When I do have development to do (which as been sparse lately ;-)) I try as much as I can to do it in a VM multiple reason... I'll blog about this soon. 

I think with a new OS you need to take a stand and look into the future... It's not like we won't be able to do it anymore.

I respect the opinions of others on this, this is just my .02c.

Cheers,

ET

Speaker at the Montreal Code Camp on October 14th

Hey all,

I will be speaking at the Montreal Code Camp. I'm doing two sessions

Introduction à Visual Studio Team System et Team Foundation Server pour les développeurs (intro to TFS) and

Développer en Virtuel (Virtually Developing).

They are expecting 300 people and there are three rooms so about 100 per room per sessions ... That is a lot of people ... gulp ... it'll be great fun.

 

Cheers and looking forward to seeing you all,

ET

TFS Server Administrators (when you can't be a Windows server administrator)

This is post of is for all of you out there that due to security restriction can't be a Local Admin on your server but still need to be TFS Server Administrators.

This addresses the Domain installed TFS not the workgroup edition (WE).  I will comment on the WE were appropriate.

As we all remember there are three application that need our attention here, TFS (obviously), Windows Sharepoint Services (WSS) and SQL Server Reporting Services (SSRS).  For project level security I urge you to use the TFS Administration Tool available on codeplex here but in order to use TFSAT you need to be a TFS Administrator.  So how do we go about setting that up;

I have found that the simplest way to manage that particular group of users was to start by creating a Domain Windows Group and assigning you TFS admins to that group.  You will see why this is important when I talk about WSS.  You can assign individuals to the various Applications but I don't recommend it for manageability (it's easier with a group).

What is ironic about this post is the in order to initially setup TFS Admins you need to be a server admin... ;-)

Team Foundation Server

Step 1.  Create a Domain Windows group (for ex. TFS-Administrators)

Step 2.  Log in as Local Administrator and add the Domain\TFS-Administrators to the [SERVER]\Team Foundation Administrators.

a. From Team Explorer, right click on the server

b. Choose Team Foundation Server Settings

c. Choose Group Membership

d. Double-Click on [SERVER]\Team Foundation Administrators

e. Choose Windows User or Group and Click the Add button

f.  Enter Domain\TFS-Administrators and click ok, ok and close

So we are now setup ad TFS administrators.

Windows Sharepoint Services

Lets now focus on WSS.  Local Administrators are always able to manage WSS but since we don't want to or can't be Local administrators we need to give TFS-Administrators rights to administer WSS.  Rob blogged about this a week ago so let's do a step by step on what to do. Again we need to be a Local Administrator to do that.

Step 1. Go to the top level Sharepoint administration site usually http://tfsserver:17012, you can also start IIS Management Console and right-click on the Sharepoint Central Administration website and choosing browse.

Step 2. Choose Set SharePoint administration group from the security configuration section.

Step 3. In the Group Account name we need to enter Domain\TFS-Administrators and click ok, you'll go back to the top page of the Sharepoint admin site with no indication of success or failure.

Our TFS Admin Domain group will now be administrators of our TFS WSS site.  Remember that Local Administrators stay WSS administrators but our TFS Admins don't need to be.

 

SQL Server Reporting Services

Finally lets get our Domain Admin group admin access in SSRS.  Again we need to be a Local Admin on the SSRS server.

Step 1. We need to go the front page of the report server.  http://tfsserver/reports

Step 2. We need to give the Domain group Content Manager role on the Top Level Report site.  To do this click on the properties tab on top

Step 3. Click on "new role assignment" in the group or user name textbox type Domain\TFS-Administrators and select content manager and click ok.

Step 4. We also need to give our Domain user group System Administrator rights.  To do this we start by clicking Site Settings in the top right corner.

Step 5. Select Configure Site-Wide Security in the security section

Step 6. Click New Role Assignment, and in the group or user name textbox, type in Domain\TFS-Administrators then select system administrator role and click ok.

My experience has been that the group needs to be in both these locations for them to be able to create and manage reports.

After all this, you should be able to create project and administer a TFS server without being a Local administrator on that server.

Let me know if this works for you.

 

Cheers,

ET