vastool status reports " "FAILURE: 302 VAS cannot find its host/ object in AD"". Checking in AD the QAS client computer object has been deleted from Active Directory (AD).
CAUSE 1 : Object does not exist in AD or on the domain controller that is being talked to.
CAUSE 2: AD permission problem
CAUSE 3: AD replication of the computer object has not occurred.
QAS has no rights to remove anything from Active Directory.
Typically, there is something extraneous in such cases. For example, check if you have any scripts running on your Windows Server which check Active Directory for any particular criteria, like machine not up for x number of days, and deletes the host objects based on the actions defined in those criteria.
Rejoin the machine to AD
/opt/quest/bin/vastool -u <admin user> join -f <yourdomain.com> or recreated the Computer account
1 - Recreate the Computer account
# /opt/quest/bin/vastool -u <admin user> create host/
2 - Then check the health of QAS client by running the status command below and checking for failures or critical errors:
1 - Check other domain controllers for the object to see if it exist.
To list the domain controllers run the following command:
/opt/quest/bin/vastool info servers
For each domain controller server, run the following command:
/opt/quest/bin/vastool -u host/ search -U DC://$server "(samaccountname=<computer object's samaccountname>)"
2 - If the computer object is missing from any of the domain controllers, this can cause QAS to be in a bad state.
If object is missing, please contact your AD team to remedy. To force AD replication. please refer to Microsoft Technet