You need to be on the matching release level of AVP and the SDM client. You will find if you connect via vSphere to the AVP host and pull up a console the US is most likely deployed/running but does not have the correct configuration.
What you might want to try is to deploy Utility Services with the VMware Embedded Host Client (EHC) just to see if the problem is with your AVP install or your hardware (bad disk?) or the version of SDM you are using. The Embedded Host Client is VMware's replacement for the vSphere Client. Beginning in AVP 7.1 the old vSphere client will not be able to connect because AVP restricts the TLS connection to TLS1.2 for security reasons. The old vSphere client cannot connect at TLS1.2. You can access the EHC by browsing to
If you do get Utility Services to deploy you will need to delete it because it won't have been set up correctly. But at least you will be able to narrow down your problem.
Workaround is to login to AVP with vSphere client and run the Utility server config wizard setup as if you are deploying US on VMware. The issue you are getting when deploying on AVP using SDM client is because the network interface config is not able to setup successfully. Once you run ythe config wizard you will see the status of US in AVP SDM client started.
thanks everyone, I resolve my problem, it is due to AVP was entering in Maintenance mode, so to exit the maintenance mode, you need to login using Vsphere web client
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.