IMHO Visual Studio 2010 Lab Management is a l33t product. At this point in time, there is no word on the pricing but I going through the Visual Studio 2010 Licensing White Paper I don’t think that it will be cheap, furthermore I am also a bit  afraid that in a lot of companies it will be a bit hard to sell because of company politics as it is possible that your company is already using for example VMware vCenter Lab Manager and they might not be willing to just throw that away (yet).

David Baliles, the Enterprise Tools Strategist @ Microsoft posted on his MSDN blog a whole bunch of Visual Studio 2010 Lab Management videos which are worth checking out.

Click here for the videos.

Pieter Gheysens is giving a session on Application Lifecycle Management with Visual Studio 2010 on the 22nd December 2009 @ 18u30.

Read more here.

I uninstalled Visual Studio 2010 Ultimate to install the Visual Studio 2010 Premium SKU. I decided to only uninstall the main component and leave all the other components intact.

The uninstall went flawless but the installation of Visual Studio 2010 Premium showed that there was an error installing the Visual Studio Macro Tools:

[11/27/09,08:04:40] Microsoft Visual Studio Macro Tools: ***ERRORLOG EVENT*** : Setup detection logic indicates that this component is NOT installed, but MSI indicates that it IS already installed.  This is usually caused by an incompatible previous version being installed on the system.  Check in Add Remove Programs and uninstall any previous versions of Microsoft Visual Studio Macro Tools.

This is not something that you would expect because one would assume that the version of the components that make up the Visual Studio suite are similar between the different SKUs. So, just out of curiosity, I uninstalled the Visual Studio Macro Tools that was installed as part of the Visual Studio 2010 Ultimate installation:

Next, I ran the installer for the Visual Studio Macro Tools that comes with the Premium SKU. You can find the installer on the installation media (X:\WCU\VSA\VSA_ENV.MSI). The version of the Visual Studio Macro Tools that I have now is exactly the same, so it must be a glitch in the installer: