Microsoft a récemment sortit un nouveau pack de gestion SCOM/SCE pour surveiller votre Team Foundation Server 2010. Pour les néophytes en la matière SCOM est l’acronyme de System Center Operation Manager, la dernière version en date est la 2007 R2. C’est un outil qui permet de faire de la surveillance de serveurs/services. Il fait parti de la gamme “System Center” de Microsoft regroupe plusieurs produits permettant d’assister les administrateurs de systèmes infra/réseau. SCE pour System Center Essential est quant à lui une version “simplifiée” et unifiée des différents produits de la gamme System Center destinée aux PME pour gérer un parc réduit de serveurs. Si votre entreprise utilise l’un de ces deux produits et que vous avez un TFS 2010, vous aurez tout intérêt à installer le PACK de surveillance pour TFS 2010 afin de pouvoir surveiller avec précision la santé des différentes composantes de celui-ci. La page pour le télécharger ce trouve ici: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=97ca3b31-3653-4d60-bdad-3f2017febdc3 Que fait donc ce pack ? Voilà un rapide copié/coller des fonctionnalités du pack:
Initially Lab Management 2010 was supposed to be shipped with the 2010 Wave of the Microsof’s ALM offer. However, the product being at its first version (then very young), Microsoft decided to push the release date in order to make it as good as people wanted it to be (honestly it was a good call). The final version came out as an update of the TFS/Visual Studio bits release in April. You have to apply it on the client and server side. Check out the KB Article here and download the update there. It’s highly recommended to install this update even if you don’t use Lab Management capabilities because it includes all the QFEs and some minor fixes/improvements released up to this day.
Team Foundation Server 2010 has a great flexibility concerning its configuration. When the binaries are installed, a wizard shows up and propose you many types of installations: Basic, Standard, Custom, etc. If you configured your TFS with either Basic or Custom you will be without SharePoint. Now let’s say you changed your mind and you want to setup SharePoint after all, one might think it’s an easy task, but we’re talking about SharePoint, then nothing is ever easy! Here is the macro scenario to succeed in this task: 1) Install WSS 3.0 Manually. 2) Add the Team Foundation Server SharePoint Extension Console (the non obvious) part. 3) Let Team Foundation Server grant access to your SharePoint. 4) Create the association between those two. Before a little screencast, let’s explain the step 2 a little bit more. When I first tried to add my SharePoint, it never crossed my mind that I have to do this step, for me (and I think many people will think the same) installing the SharePoint Extensions were only if you have installed the SharePoint server on another server. But the truth is that you need to install it to get an extra configuration item in […]
The new release of Team Foundation Server 2010 went out few weeks ago. As I was lazy, I installed a quick VM to test it out, I put 512 Meg of RAM because I was cheap and planned to setup the basic version. Well, it didn’t go very well at first as the new Team Foundation Server Administration Console rejected my configuration: not enough RAM, 1024 is at least needed! Well, I was a bit stubborn on this and thought that 512MB could be fine for my own VPC evaluation (yes, cheap and stubborn, what a guy!), so I tried to find if there was a way to overcome this verification. My buddy Reflector helped me to find out what could be done and here’s the solution to my problem: If there’s an error that pops up, you can make the verification mechanism ignores it by setting an environment variable (that’s right, a Windows environment variable) corresponding to the criteria you want to bypass. In my case the criteria was called “VMEMORY”, the formulae is not that hard, create a variable TFS_IGNORE_VMEMORY (with a value of 1 for instance, but it doesn’t matter), and you’re good to go! Nice, of […]