Hi,
Back in the day, times were simpler. A person could download vMA, slap on an IP, and after a bit of configuration, it worked. Now, using vSphere 5, the newest version of vMA will not boot, complaining about a non-existent IP Pool... even when I specified that it uses Fixed IP Allocation. That being the case, what magic do I need to do to get this thing to boot?
Power On virtual machine
vSphere Management Assistant (vMA)
Cannot initialize property 'vami.DNS0.vSphere_Management_Assistant_(vMA)', since network 'XXXXXXXXXXXXX' has no associated IP pool configuration.
Thanks!
NYSteve