This issue is most likely the result of an incorrectly configured ovf.xml file.
To resolve this issue, open the appliance-configuration-log.txt file to examine the exact error message. To do so on your Virtual appliance, follow the steps below:
Follow the steps below to troubleshoot the issue:
A. Verify that the parameters you put into the appliance during configuration of the ovf.xml file are correct. For example, if you are joining the domain 'yourdomain.com', configuration parameters for ERA Server Virtual appliance would be:
If you are sure that all parameters are correct, check whether the configuration generated by the automation script is correct.
B. Check the following configuration files:
/etc/hostsshould correctly map domain controller name and its IP address.
/etc/krb5.confshould be correctly generated. Check that '
/etc/crontabshould contain record for regular time updates against domain controller.
/etc/samba/smb.confshould be correctly generated.
If all configuration files are correct, then proceed with manual domain join.
C.Join the domain manually:
net ads join -U Administrator%' to join the domain. If successful, you should see created computer record in domain controller.
service winbind start'.
service nmb start'.
service smb start'.
wbinfo -u' lists domain users and '
wbinfo -g' lists domain groups.
ERA Server uses the commands '
kinit' and '
ldapsearch' to browse through active directory and '
wbinfo' and '
ntlm_auth' to perform domain authentication. If these commands work, then you have successfully joined your domain.