Authenticating to an Active Directory (AD) stops after upgraded to QAS 4.x on window side. Or post QAS upgrade to 4.x on windows side, the necessary UNIX attribute are not correctly populated into users accounts in UNIX Account tab in Active Directory Users and Computers.
The schema configuration can be customized in the QAS 4.x Control Center. QAS 4 clients know to look in the Quest Authentication Configuration (QAC) for this kind of custom information, however QAS 3 clients do not have this capability.
Custom attributes which were set previously through QAS or VAS configuration tool are no longer set
1 - To tell QAS 3 clients about custom LDAP attributes, add a line in the [vasd] section of /etc/opt/quest/vas/vas.conf, mapping the field to the custom LDAP attribute. For example, if the gecos field is mapped to the displayName attribute rather than the default gecos attribute, you can put in a line as below:
gecos-attr-name = displayName
The following attributes can be set this way:
These setting can also be made on QAS 4 clients to override the settings that the client gets from the Quest Authentication Configuration.
To set the attributes globally for the 4.x clients, do the following;