When installing a VMA under vSphere it will not power on with an error regards IP Pools. This can then start a very infuriating circular process of the range never being allowed. I spent a good hour or so looking at this issue and with the help of thesaffageek we thought of a way to NOT use the IP Pool (this is something that is being used for Cloud and the future)
To get around the need for the IP Pool the vAPP options need to be disabled to allow the virtual machine to power on and be configured. The following steps should be followed:
Once the machine has been configured and powered on the settings changed will have reverted back to Enabled but will not need the pool. I’m not 100% sure why this happens and I have not yet had to restart the VMA. I will update this post if I get any issues.
By Paul Wood