> In order to create multiple machines in VPC I start with a basic OS
> installation and then copy the files and rename to create more machines. I
> rename the "machinename" in the OS and alter the SID with Ghost. However
> the MAC address of the Nic is the same and so the virtual machies won't
> connect to each other in the virtual network.
>
> Is there any way to force VPC to generate a new MAC address for the Nic with
> out installing a new OS from scratch to create the new virtual machine?
> This is used in a MSDN Lab environment where I have to create many machines
> and that is a real problem with OS's that need "activation" because you can
> only activate them 10 times from one CD key. Currently I save my "generic"
> installation after it has been activated and reuse it from there. My lab's
> "lifespan" is sometimes longer (at least with DCs) than the pre-activation
> period so I can't just not activate them.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

> In order to create multiple machines in VPC I start with a basic OS
> installation and then copy the files and rename to create more machines. I
> rename the "machinename" in the OS and alter the SID with Ghost. However
> the MAC address of the Nic is the same and so the virtual machies won't
> connect to each other in the virtual network.
>
> Is there any way to force VPC to generate a new MAC address for the Nic
> out installing a new OS from scratch to create the new virtual machine?
> This is used in a MSDN Lab environment where I have to create many
> and that is a real problem with OS's that need "activation" because you
> only activate them 10 times from one CD key. Currently I save my "generic"
> installation after it has been activated and reuse it from there. My
> "lifespan" is sometimes longer (at least with DCs) than the pre-activation
> period so I can't just not activate them.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>

> Is there any way to force VPC to generate a new MAC address for the Nic with
> out installing a new OS from scratch to create the new virtual machine?
>

> Either don't copy the .vmc file, create a new one instead, or edit the
> .vmc file and remove the MAC address. Search the file for
> ethernet_card_address.

> Yes, the mac address is held in the image configuration file *.vmc. Open
> this file with notepad. Locate this string
> <ethernet_card_address type="bytes">0003FF74859B</ethernet_card_address>
>
> And delete the string which is written quote"0003ff74859b" (This will be
> different for you.
>
> Do this for all but the origional image.
>
> Problem solved., oh, and you dont have to reactivate the image because
> already is, assuming that you dont sysprep them, that is a different
>
> Regards, Alan
> Systems Engineer
>
>
> "Phillip Windell" wrote:
>
> > In order to create multiple machines in VPC I start with a basic OS
> > installation and then copy the files and rename to create more machines.
> > rename the "machinename" in the OS and alter the SID with Ghost.
> > the MAC address of the Nic is the same and so the virtual machies won't
> > connect to each other in the virtual network.
> >
> > Is there any way to force VPC to generate a new MAC address for the Nic
> > out installing a new OS from scratch to create the new virtual machine?
> > This is used in a MSDN Lab environment where I have to create many
> > and that is a real problem with OS's that need "activation" because you
> > only activate them 10 times from one CD key. Currently I save my
> > installation after it has been activated and reuse it from there. My
> > "lifespan" is sometimes longer (at least with DCs) than the
> > period so I can't just not activate them.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> >