Hi
We are currently evaluation View 4.6 and I'm having some issues with DNS/Computer naming when View creates a new machine in a pool
When I use Linked Clones, it works fine i.e. every new machine that gets provisioned has the next name in the sequence, both for DNS and as a virtual machine.
When I setup a pool for full virtual machines, View gives it a unique virtual machine name in vCentre, but the same DNS name as the template machine (and the first virtual machine in the pool) This means I have to rename the new machine, and then rejoin the first machine back to the domain, because DNS thinks it no longer exists.
I would love to just use Linked Clone machines, but one vital application we have (an Ingres database) refuses to work on the linked clones, but is quite happy on the full machines.
Hope this makes sense and someone can help
Thanks
Dave
With full clone provisioning you will be using one Custom Spec which is defines in vCenter Server.
Edit that custom spec and set the VM host name as "Use Virtual Machine name"
This will solve your problem
With full clone provisioning you will be using one Custom Spec which is defines in vCenter Server.
Edit that custom spec and set the VM host name as "Use Virtual Machine name"
This will solve your problem
Yes, that's fixed it
Thanks for your prompt reply and help
Dave