MachineProvisioned Event Payload different when creating IaaS VM vs Importing VM

[pizzle85]

When we import VMs into vRA we perform some operations on it through vRO. I am attempting to move from workflow stubs to events to perform these processes. Historically when using the workflow stubs, regardless of whether a VM was being created through the IaaS processes or imported i got the exact same vCACVmProperties set. With the event broker when creating a VM i get a properties array in the event payload, when Importing i do not get this. Also running the 'getPropertiesFromVirtualMachine' action returns only about 5 properties instead of the 50 or so i need.

Any suggestions on getting a full vCAC property set from vRA for my imported VMs?

[SeanKohler]

I would guess they don't exist. You can write any property (even new ones) at any time using the property update methods.  I would do a post-machine-import write of your properties key:value pairs based on the values you have in your provisioned machines.

Thanks for sharing this issue though.  We are going to import 1000+ machines in the next few months.  I hadn't yet considered that we wouldn't have machine properties that we need.  (though some of our maintenance workflows would write some of them due to BG membership and other states)