machine# rpm -Uvh vasclnt-4.0.1-22.i386.rpm vasgp-4.0.1-22.i386.rpm vasutil-4.0.1-22.i386.rpm
Preparing... ########################################### [100%]
Failed to detect QAS Application Configuration information in Active Directory.
The host appears to be joined to an Active Directory domain. However it appears that the domain has not been configured for QAS. Please verify that the host can authenticate with the domain and that the upgrade steps outlined in the QAS 4.0 Upgrade Guide have been followed. Continuing to install will prevent Active Directory users from logging into this host.
With QAS version 4.x , a QAS Application Configuration (QAC) must exist in Active Directory before the QAS hosts can be joined.
RESOLUTION 1:
Create the QAS Application Configuration (QAC) from the Windows side
Run the QAS.exe on the windows server
Please see page 21 of the QAS 4.0 Install Guide for more information on this, "Configuring Active Directory for QAS".
RESOLUTION 2: Create the QAC from a QAS client using 4.0.1.22 or above
# /opt/quest/bin/vastool configure -d <domain> ad [Container DN, default is 'CN=Program Data,DC=<domain>’]
The Quest Application Configuration (Q.A.C.) is an Active Directory object used to store QAS product information such as license and default settings. Now the *NIX client, the MMC snapin, and IMU can read behavior from a single location. It consists of multiple nested objects of the objectClass ‘Container’ inside a container with the name cn={786E0064-A470-46B9-83FB-C7539C9FA27C}.
There should only be one in an Active Directory Forest.
If multiple configurations are found, QAS uses the one created first as determined by reading the whenCreated attribute. If another group in your organization has already created an Active Directory configuration, use the existing configuration. You can use the provided PowerShell cmdlet Move-QasConfiguration to move the configuration data to another location in Active Directory. At any time you can completely remove the QAS Active Directory configuration using the Remove-QasConfiguration cmdlet.
Creating/configuring the QAC will have no effect on QAS 3.x clients.
With QAS version 4.0.0/4.0.1 , a QAS Application Configuration (QAC) must exist in Active Directory before the QAS hosts can be joined.
© 2024 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center