There are many Virtual Appliances such as vSphere Replication, HCX as well as other 3rd party solutions which integrate with vCenter Server's vService Extension Service. For these OVF/OVAs to be properly deployed and powered on, you need to bind to the specific vCenter Server's vService endpoint (see screenshot). Today, Import-VApp does not support this feature and after deployment, power on will fail and requires user to re-deploy using either the UI which isn't ideal. vService binding is supported w/OVFTool today https://www.virtuallyghetto.com/2014/10/how-to-configure-the-vcenter-extension-vservice-using-ovftool.html and it would be great to see this natively get added into Import-VApp since this can not be configured post-deployment even with OVFTool and must be done as part of the initial deployment.