Fix the network settings for the VSTS Beta 2 VPC image – level 100

At Tech Ed, Microsoft handed out DVDs with a VPC image ready to go with:

  • Windows Server 2003 Standard
  • VS Team Suite (included all of Team System and Whidbey).
  • Sql Server 2005 April CTP
  • Microsoft Office 2003
  • Visual Studio Tools for Office.
  • All of it expires in Sept 2006.

This is the one of the best ideas that Microsoft has had!  Many
were feeling the pain of beta installs, especially with Team System, so
now they release VPC images  that are ready to be evaluated. 
I’m loving it.  I’m using this image for all my .Net 2.0 Beta 2
goodness, and I didn’t have to spend hours setting it up.  Hop
over to Microsoft or talk to your local Developer Evangelist (or User
Group) to get your copy of the DVD.

I was frustrated, however, that my image couldn’t get on the
Internet.  After some investigating, I discovered that the network
connection had an explicit IP and a gateway of  I’ve
made that typo before (198 instead of 192), but I just cleared it out,
use DHCP, and now my image can get to the Internet.  A small
oversite on the image-creators, but an easy fix.  I love VPC for
beta software!  I’m diving into all the ASP.NET security

A _great_ idea with 2.0 is a machine-wide web.config file located at:
%WinDir%Microsoft.NETFrameworkv1.1.4322CONFIG.  If you have a
team of developers that are in charge of an app, you can set the
machine to High trust instead of Full, turn override off, and they
won’t be able to set their app to Full trust (this assumes that you
don’t want them running arbitrary Win32 API calls from their web pages,
or COM interop).