Everything I have read, videos that I watched mention using network profiles or create a customization spec to assign static IPs to the provisioned VMs. In a typical lab environment IP addresses are a none issue as DNS is used to handle the server IP lookups. But when duplicating a whole production environment, down to each individual server IP address, into multiple development lab environments by provisioning VMs using vCAC single or multi server blueprints completely wipes out the source VMs IP configuration (from what I noticed replaces the sources network adapter with one vCAC provisions) and replaces it with a random static IP address from a network profile or customization spec. Again in a typical lab environment vCAC IP assignment would be a none issue but since the a production environment may have unknown hard coded IP address for some of the applications (i.e. application to database connection strings) I have to duplicated everything as if it was the original production environment....makes sense?
If anyone else has come across a similar dilemma or perhaps has come up with a method to do this I would love to hear from you.
thanks,
bkitt2000