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-5771: Centrify daemon does not start upon first boot after the update from 10.8.x / 10.9.x to 10.11 and prevent AD users access

Centrify Identity Service, Mac Edition ,  

12 April,16 at 11:46 AM

Applies to: Centrify DirectControl for Mac version 5.2.4 on Mac OS X 10.11


Problem:

Centrify daemon (adclient) does not start upon first boot after the OS update from 10.8.x/10.9.x to 10.11. Running "adinfo" in terminal shows:

CentrifyDC mode: <unavailable>

This prevents AD users from logging into the Mac.


Cause:

If you are upgrading to OS X 10.11 El Capitan from a 10.8.x or a 10.9.x version, there is a known apple bug (22735194) that prevents the Centrify daemon (adclient) from running upon first boot after the update.


Workaround:

1. Login as a local administrator and execute the following command in terminal to restart Centrify daemon (adclient):

sudo /usr/local/share/centrifydc/bin/centrifydc restart

Then run the command "adinfo" to confirm Centrify daemon is running:

CentrifyDC mode: Connected

Or

2. Alternatively, upgrade from 10.8.x / 10.9.x to 10.10 first, then proceed with the update to 10.11 El Capitan.

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

Related Articles

 articleKB-6279: Network users unable to login after OS X direct upgrade from 10.8 or 10.9 to 10.11 articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? 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-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-3925: How to add Centrify parameter to a group policy articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out?