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-1875: Huge amount of Event ID 566 generated when adnisd is enabled

Auditing and Monitoring Service ,   Authentication Service ,   Mac & PC Management Service ,  

12 April,16 at 11:45 AM

Applies to:

Centrify DirectControl version 4.4.x on Windows Server 2008 R2


Problem:

Huge amounts of 566 failure events are being recorded into AD events logs due to adclient trying to access the unixUserPassword attribute. Example event log entry: 
Event Type:     Failure Audit
Event Source:   Security
Event Category: Directory Service Access 
Event ID:       566
Date:           23-Sep-2010
Time:           9:53:58 AM
User:           CENTRIFY\CENT210$
Computer:       CENTSVR01
Description:
.....


Cause:

Starting Windows 2003 SP1 Microsoft introduced the feature to mark the unixUserPassword attribute as confidential. By default only members of the built-in Administrators group can read a confidential attribute. adclient ignores the setting in DirectControl Console for supporting agentless client and always tries to read all the unixUserPassword attribute of AD user object. Hence, the failure access of such attribute gets reported with Event ID 566.


Workaround:

Grant "read" permission of unixUserPassword attribute to computer objects.

Here is how to check permission of attribute unixUserPassword in AD user object:

1. click 'Start' -> 'Run' type  adsiedit.msc

2. Open CN=User, right click select 'Properties'

3. Choose "Security" tab

4. select "Advanced", in permission column, click 'Add', under 'Enter the object name to select' type 'Authenticated Users', click on 'Check Names' then select, click OK

 then  under 'Enter the object name to select' type 'Authenticated Users', click OK.

5. Then select 'Authenticated Users' and click on 'Edit', select tab 'Properties'.
Under 'Apply to:'  select 'Descendant User objects' and look for 'Read unixUserPassword', check the box under 'Allow', click OK

Note: Look at the attachments file.


Resolution: 
This will be fixed in a future release of DirectControl.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-3925: How to add Centrify parameter to a group policy articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6041: How to show current license type in use by adclient articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-1550: Windows Event ID: 26 gets reported in Domain Controller event log from Unix/Linux machines running Centrify DirectControl articleKB-6056: How to report the group policy settings that are in effect for the local computer? article[How To] Enable Symantec VIP MFA for Centrify Server Suite on Linux Part I