Hi OzTFS'ers,

Brian Randell blogged this recently for those that are interested: 
http://www.pluralsight.com/community/blogs/brian/archive/2008/12/24/happy-holidays-and-look-what-santa-s-brought.aspx

Also note that the VS2010 CTP will expire Jan 1 2009. See my blog post for how 
to workaround it: 
http://blogs.msdn.com/granth/archive/2008/12/10/visual-studio-2010-ctp-vpc-will-expire-jan-1-2009.aspx



Grant

---

I'm happy to report that the VSTS virtual machines are all updated with fresh 
bits and expiration dates. You now can test and evaluate (since these images 
are NOT licensed for production use) Team System 2008 with SP1.

The new expiration date is December 31, 2009.

That's right, we've produced the same pair as before. A VSTS "all-up" image 
with Team Foundation Server, Team Build, Team Explorer, and Team Suite. And a 
TFS "only" image with just Team Foundation Server, Team Build, and Team 
Explorer.

What's different is that we've produced both Virtual PC 2007/Virtual Server 
2005 R2 compatible images AND Hyper-V compatible images. Download the ones that 
make you happy!

As part of the refresh and extending the expiration date, I've updated the 
images to include the following (naturally some items only appear in the 
"all-up" images):

 *   the latest virtual machine additions or integration services components
 *   all of the latest Windows Updates as of December 1, 2008
 *   Team Foundation Server 2008 SP1
 *   Visual Studio 2008 Team Suite SP1
 *   Team System Web Access 2008 SP1
 *   Team Foundation Power Tools, October 2008 update
 *   the latest MSSCCI provider
 *   Team Explorer 2005 (this allows you to work with TFS from Visual Studio 
2005 which is installed so that you can edit and customize TFS reports)
 *   the GDR for the product formally known as Visual Studio 2008 Database 
Edition (aka Data Dude)
 *   current Process Explorer, Process Monitor, and Background Info

Naturally at this point, you're wondering, where are the goods? Here they are:

 *   VSTS "all-up" Virtual PC/Virtual Server 
image<http://www.microsoft.com/downloads/details.aspx?FamilyID=c7a809d8-8c9f-439f-8147-948bc6957812&displaylang=en>
 (6 GB download, expands to 15 GB)
 *   TFS "only" Virtual PC/Virtual Server 
image<http://www.microsoft.com/downloads/details.aspx?FamilyID=72262ead-e49d-43d4-aa45-1da2a27d9a65>
 (3 GB download, expands to 8 GB)
 *   VSTS "all-up" Hyper-V 
image<http://www.microsoft.com/downloads/details.aspx?FamilyID=9eb65c97-29c9-4d05-ae45-73d22ad4b86e>
 (6 GB download, expands to 15 GB)
 *   TFS "only" Hyper-V 
image<http://www.microsoft.com/downloads/details.aspx?FamilyID=39644cdd-db4d-445e-b087-dd3e3cdf03fb>
 (3 GB download, expands to 8 GB)

The Virtual PC 2007/Virtual Server 2005 R2 compatible images provide VMC files 
for Virtual PC 2007 SP1 and Virtual Server 2005 R2 SP1 Update. The VMC file 
that ends in -V7 is for Virtual PC and the one that ends in -R2 is for, well, 
Virtual Server.

The Hyper-V downloads only contain the VHD. You'll need to configure them 
yourself. I wanted to make it as easy as possible.

And as a reminder, these images do not contain antivirus so follow your 
corporate policy before you bring them up on a network. That said, they are all 
built from the same base so duplicate IDs on a network is possible. Use Shared 
NAT or one of the many other options to get network access without causing 
problems.

--------------------------------------------------------------------------------
List address: [email protected]
Subscribe: [email protected]
Unsubscribe: [email protected]
List FAQ: http://www.codify.com/lists/oztfs
Other lists you might want to join: http://www.codify.com/lists

Reply via email to