GrayAndYellowGearsThere is no option to manage the VM MAC address using the MED-V Client Interface or workspace policy. During the first time setup phase MED-V automatically deletes the old VM MAC address and then creates new random MAC address. This cannot be overwritten or controlled using the *.VMC file. If you set a static address in the *.VMC file, it will be overridden. If you would like for a MED-V workspace to maintain a permanent MAC address you will need to use the GlobalImageData.XML file to set this.

GlobalImageData.xml is a file which resides under the image directory and contains information which is shared by all versions of an image. The location is in the <MED-V Images Root>\<Imagename> directory and affects all versions of the image. Two important values are the <DesiredMachineName> and the MacAddress> elements.

The <DesiredMachineName> is the auto-generated name of the MED-V workspace computer name. In order to make sure all versions of the same image have the same name, the random name chosen for the image is stored in the <DesiredMachineName> field of this file.

The <MacAddress> field is where you can set a static MAC address for the VM that will remain constant. This can be created after the image has been deployed and after first-time setup or, you could incorporate the creation into the first-time setup by using scripts or an external tool to set the VM's MAC address by setting the <MacAddress> field.

It is important to format the MAC address properly with the correct vendor code for Virtual PC. The MAC address is a hexadecimal value of 6 bytes which starts with 0003FF, the vendor code for Virtual PC, for example 0003FF0A0B0C. Also note that configuring two machines with the same MAC won't work, and the second machine with MAC will not be able to get network connectivity. The following is an example of a custom GlobalImageData.XML file:

<?xml version="1.0"?>
<ImageGlobalData xmlns:xsi="" xmlns:xsd="">

Steve Thomas | Senior Support Escalation Engineer

The App-V Team blog:
The WSUS Support Team blog:
The SCMDM Support Team blog:
The ConfigMgr Support Team blog:
The SCOM 2007 Support Team blog:
The SCVMM Team blog:
The MED-V Team blog:
The DPM Team blog:
The OOB Support Team blog:
The Opalis Team blog:
The Service Manager Team blog: http:
The AVIcode Team blog: http:

clip_image001 clip_image002