Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-9584: Command "adquery user" returns empty set in Auto-Zone

Authentication Service ,  

19 December,17 at 08:29 PM

Question:
In an auto-zone, when user groups are configured in both the auto.schema.allow.groups and nss.group.override files, why are they not listed in the output after running "adquery user" on the server?

Answer:
For any groups specified in auto.schema.allow.groups, the group override feature is not permitted. All groups subsequently identified in nss.group.override are skipped over and will not be listed by adquery results nor receive logon access to the server.

Related Articles

 articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-2090: "adquery group" command does not return primary group members articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-11863: adquery group {groupname} returns user lists that include non-zoned users