Anyone ever done this? Having some trouble getting it working/debugging.
What I've done:
- install VRMGuestAgent using VMware docs. on my base AWS Windows instance. Put my cert.pem file in place. From all indications from the log it is talking to the IaaS manager fine. Also Windows pops up messages about a background process talking to the console which reveals a VRMGuestAgent process running looking for a workitems.xml file to show up.
- I then sysprep generalize the instance with an unattend.xml file in place and ready to go. When done and powered off convert to AMI.
- Deploy AMI; sysprep does the specialize and oobe steps in the unattend.xml correctly and I also have a setupcomplete.cmd file that runs.
- Once ready I log in; I don't see any workitems.xml or parameters.xml as I've seen referenced in docs that contain the script to run and custom properties parameters. The agent is running, not logging errors and has the background process window running.
I do the custom properties defined as documented - use guest agent; wait for customization, script0 ,etc.
My thought is vRA thinking the deployment is done as soon as AWS clones the AMI and powers on the instance; but doesn't realize I have a sysprep unattend that needs to run to configure networking, etc. During that window the VRM agent is not able to talk to vRA, vRA then never sends the parameters and script command. After vRA has given up is when the VRM agent gets connectivity but it is too late.
That is just an unproven theory - in any event if anyone has done this on AWS and has insights I would welcome the feedback.