I understand what you are saying but if you already have the only DHCP server in production and you want your proof of concept View VMs to get an ip range that is different from the production, then I will setup another scope on the DHCP server (superscope?) and here is the missing step:....something needs to be setup within the DHCP server to make it distinguish between the two subnets: Production and Test. So is there a way of binding the second scope (View) to a port group (NIC) so when a View VM boots up it will reach the DHCP server as you said using the portgroup assigned to the parent image and get an IP address different from the production. Maybe I am just paranoid, I should just increase the existing scope and let everything on the same IP range:).

Thank you.

Regards

Djak44