cmbwml1
Enthusiast
Enthusiast

Disable Custom Names

We enabled custom naming templates in vRA 8.8 and didn't realize it would prevent us from specifying VM names without a number appended.  Is there a way to disable the custom naming templates feature or to override the default resource naming action of mcm###-####### getting appended?

0 Kudos
8 Replies
BrettK1
Enthusiast
Enthusiast

Edit: My reply was about Per-Project Custom Naming Templates, not the 'Custom Names' new system, so it's irrelevant.

0 Kudos
rwk1982
Enthusiast
Enthusiast

Hello!

Same issue here and we had a talk with our TAM. Once you enabled Custom Naming Templates you can not disable it. The Number Generator is unfortunately mandatory for the Templates but this will be changed in Future vRA Versions. Unfortunately I don't have a solution for you (we redeployed vRA because of this behavior).

Robert

Drink coffee.. Do stupid things faster with more energy...
0 Kudos
BrettK1
Enthusiast
Enthusiast

Ahh, I misunderstood, since vRA uses the term 'custom naming' in multiple places.  (using the same term to mean different things in different places is definitely a VMWare issue).  Yes, I avoided the new 'global custom naming' when it appeared, and looks like I can be glad I did with what you said!

0 Kudos
qc4vmware
Virtuoso
Virtuoso

Glad I found this thread... I did only test this in a non production environment and I took snapshots so I was able to revert... but I was pretty shocked to find out that a number incremented was a requirement.  Also, it seems like using ${resource.name} on it's own as the template is not valid???  In our environment we want it all to line up with what the user has input for the system name.  We do other verification outside of vRA to make sure the name is valid.  

I think I'll report all this as a "bug" and hopefully they will allow more flexibility in future releases.  Not useable for us now.

0 Kudos
BrettK1
Enthusiast
Enthusiast

Edit: Answering the wrong thing again... vRA terminology can be frustrating (Custom Naming Templates vs... Custom Name Templates?  Or even better, "Templates (i.e. Blueprints) vs Templates (i.e. 'Images')"?  Did marketing get their hands on this?

 

0 Kudos
ajayran
Contributor
Contributor

So I reinstalled 8.8 and I had this option, I didn't enroll

ajayran_0-1658938293465.png

And verified that I am not enrolled

ajayran_1-1658938337460.png

 

but it's still appending that MCM###

ajayran_2-1658938366933.png


any guidance or tips is appreciated

0 Kudos
qc4vmware
Virtuoso
Virtuoso

I think maybe that is the default behavior... in your screenshot I can't see what the template is set to.  It is completely empty it has to name it something.  Try setting it to this ${resource.name} .

qc4vmware_0-1658958711596.png

 

0 Kudos
qc4vmware
Virtuoso
Virtuoso

Also, I think I saw in the release notes as of some version you don't have the option to not have the new naming scheme active.  I was surprised to see you could install 8.8 and still had a choice.  I suspect you can still override this with a extensibility action on the machine provisioning event.

0 Kudos