nicolaj
Enthusiast
Enthusiast

Properties not being applied to vcac 6.2 provisioned vm's

Jump to solution

I am trying to set up vcac 6.2 for the first time. Without going into all the detail of how I got here,I am finally at the point where I can try and test out my setup. I request a machine through the catalog, and the machine is named according to my machine prefixes, it is assigned an IP out of my network profile - everything looks like it should from within vcac and even in vCenter. But when the vm is deployed and built in vCenter, I open the console and log onto it, the hostname is that of my template, not the machine name assigned to it. The network information is also that of my template, and not the IP assigned to it by vcac. If I look at it in vcac under item details, it's listed the way I want; the properties are just not actually getting assigned to the vm. I've set up all of the pertinent custom properties in the blueprint; Does that make any sense? What is the huge piece of this that I am missing? Any nudge in the right direction would be greatly appreciated.

Thank you!

0 Kudos
1 Solution

Accepted Solutions
GrantOrchardVMw
Commander
Commander

Do you have a Customisation Script from vCenter associated with the Blueprint?

Grant

Grant http://grantorchard.com

View solution in original post

0 Kudos
2 Replies
GrantOrchardVMw
Commander
Commander

Do you have a Customisation Script from vCenter associated with the Blueprint?

Grant

Grant http://grantorchard.com

View solution in original post

0 Kudos
sbeaver
Leadership
Leadership

Grant is right!  Customization Spec is the issue

Steve Beaver
VMware Communities User Moderator
VMware vExpert 2009 - 2020
VMware NSX vExpert - 2019 - 2020
====
Co-Author of "VMware ESX Essentials in the Virtual Data Center"
(ISBN:1420070274) from Auerbach
Come check out my blog: [www.virtualizationpractice.com/blog|http://www.virtualizationpractice.com/blog/]
Come follow me on twitter http://www.twitter.com/sbeaver

**The Cloud is a journey, not a project.**