If you are using PAM configurations on your system that have been modifed from your systems default installing QAS may change this configuration and result in undesired behaviour.
QAS is designed to work with most common PAM configurations however it is unable to handle every possible PAM configuration that is encountered.
If you have a non-standard PAM configuration after joining QAS to a domain you will need to update your PAM files manually. A wrapper script could be used to automate this for automated deployments.
After the system is joined and your customer PAM files are in place, if you need to rejoin your system to the domain for some reason then the "vastool unjoin" and "vastool join" commands both support a --skip-config option which can be used to prevent QAS from modifying the PAM configuration on the system.