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-5272: GC binding is required for pre-creating computer using adedit in Suite 2015

12 April,16 at 11:44 AM

Applies to Centrify DirectControl 5.2.2 on all platform

Problem:

When using precreate_computer with –all option, there will be an error encountered if binding to a domain without global catalog (GC):
>precreate_computer computer$@us.support.local - all                                
No binding for GC in forest US.SUPPORT.LOCAL
 
Cause:
  
Since Centrify Suite 2015 the global catalog search is required for pre-creating computer. When there is no GC binding present, it tries to bind to the parent domain (precisely forest name as the domain) and perform the search. The purpose of the search is to avoid duplicate service connection point (SCP) objects in the forest, which will cause conflict during adjoin.
 
Workaround:

Please add extra binding to the parent domain in adedit.

Bind with machine credential:

bind -machine <parent domain>
e.g
bind -machine support.local

OR

Bind with user credential:

bind <parent domain> <User>
e.g.
bind support.local admin_support

Resolution:

In Suite 2015.1 has introduced an option -nogc to bypass the GC search.

e.g.
precreate_computer testmachine$@us.support.local -nogc

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

Related Articles

 articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? 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-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-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) article[TIPS] A Centrify Server Suite Cheat Sheet articleCentrify's Privileged Identity Management Solution for Big Data