vRA deploys new VMs with existing name

[cdhunter]

Having a small problem with vRA in that when we deploy a new VM from Blueprint they are created with a server name that already exists!

When deploying a new VM in VRA they are deployed into a specific build folder.  Apart from deploying into specific folders (so the VM can't be duplicated within vCenter) is there any other way to fix this?

Thanks

[greco827]

vRA is only aware of the VM's which it manages.  If you are using the same naming convention that already exists you will need to import the existing VM's into vRA so that they can be managed via vRA.  This is a pretty time consuming process.  Depending on the complexity of your naming convention, it may be wise to simply start the sequencing number high (don't start with 001, but rather 200, for example) or simply add an additional character to the naming convention to reflect the server was provisioned via vRA, which will obviously prevent name duplication with existing servers.

http://pubs.vmware.com/vra-62/topic/com.vmware.ICbase/PDF/vrealize-automation-62-system-administrati...

Page 34

[RanjnaAggarwal]

There are two options available for this:-

1. Configure machine prefix in such a manner so that it should duplicate the same name

2. another option is with custom properties you can provide machine name option to user where they type machine name while requesting the VM.