I've just finished a developer guideline doc in the free doc library showing how to setup multiple MOSS 2007 Virtual Machines with Virtual PC 2007 along with information on how to properly distribute and avoid networking and configuration issues when creating a developers library of VM images.

You may have spent many hours building out your Virtual Server or Virtual PC image and now want to distribute a copy of your virtual image to others on your team inside a corporate network.  It's easy to just to grab an external USB drive and give someone a copy. Well, in order to avoid network conflicts where the same Virtual Machine in a domain workgroup could have IP DHCP conflicts with duplicate server names and SQL instances, you'll need to understand how to resolve and rename your server instances. 

This document assumes that as a Developer / IT Pro, you have already considered the pros and cons of virtualized IDE's and the products that are widely available today and that you have a base image somewhere, created using similar instructions like the steps listed here on MSDN.

I've read through some pretty decent blogs in the few years focusing on SharePoint development and how to utilize Virtual Server, Virtual PC2007 and VMware for MOSS, WSS and ASP.NET development. Some books contain details around development in VPC or Virtual Server but most never explain the pros and cons well enough to know more than what the author simply preferred. Virtual PC, other than being free-as-in-beer, lends itself to ease-of-use, customization, and distribution among developers. (See my favorite list of blog articles on VM based development)

For a complete development system, each build could take up to 8 hours or more. The purpose of this document is to reduce those efforts to a fraction of the time require to build each VPC and with far fewer steps than it would take to copy all of the required media and repetitively to create a new server VPC for each developer on your team.   

In short, this document shows you how to copy, rename and reuse a base image over and over to distribute to others without conflict. I hope it's helpful!