Deploying most of Avaya's ova's to your own virtual environment (AADS included) without using the SDM restricts access to root to Avaya in a challenge/response scheme where only Avaya holds the key. You can get root access afterwards by signing agreements with Avaya and paying them to open it up.
Most of the 8.X and 10.X OVAs have the option to enable root when using the SDM. My AADS are deployed using the SDM but the root option is not included.
The real reason to need root is to edit the /etc/hosts file. I've gone around this by building a DNS server and placing the required entries in the DNS.
On a side note, if you don't have a high stratum NTP source, AADS will not deploy successfully. Windows 2019 NTP was not enough though it works fine for the other applications...
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.