CA Service Management

 View Only
  • 1.  Filter contacts from AD with pdm_ldap_import

    Posted Sep 05, 2013 05:41 AM
    Hello All,
    Here a few tips for pdm_ldap_import which would help speed it up and as well avoid a lot error messages in the ldap_logging.n and stdlog.n files which complain about last name missing - something like below:

    cnt:A8E83F210C41304FAA27A77D06734EDD (AHD03075:Required attribute Last Name is missing from object Contact)

    The idea here is to NOT let the pdm_ldap_import process look at or process contacts who have last name as NULL. We set a 'ldap filter prefix/suffix' manually in the NX.env file to achieve the above objective.
    Here are the steps:

    * set the ldap_user_object_class options manager value to blank (remove person)
    * add the following variables to the NX.env file:
    @NX_LDAP_FILTER_PREFIX=(&(objectClass=user)(mail=*)(givenName=*)(sAMAccountName=*)(sn=*)
    @NX_LDAP_FILTER_SUFFIX=)
    * make sure you see @NX_LDAP_USER_OBJECT_CLASS= [BLANK] in the NX.env file
    * restart services for the changes to take effect

    The above example
    objectClass=user - takes care of importing only 'users' type accounts excluding computers, mailboxes etc which are also 'person' type of accounts
    mail=* - filters out contacts where email_adress is NULL
    givenName=* - filters out contacts where first_name is NULL
    sAMAccountName=* - filters out contacts where userid is NULL
    sn=* filters out contacts where last_name is NULL

    You can include all or remove/add any more AD attributes as per your specific needs, the above can be used for reference for your specific filter prefix.

    Thanks,
    Vamsi
    Sr Support Engineer
    CA Technologies


  • 2.  RE: filter contacts from AD with pdm_ldap_import

    Posted Sep 05, 2013 09:59 AM
    Thanks for the tip Vamsi!


  • 3.  RE: filter contacts from AD with pdm_ldap_import

     
    Posted Sep 06, 2013 03:23 PM
    Thanks for sharing these tips with the community Vamsi!


    vamsitaduri wrote:

    Hello All,
    Here a few tips for pdm_ldap_import which would help speed it up and as well avoid a lot error messages in the ldap_logging.n and stdlog.n files which complain about last name missing - something like below:

    cnt:A8E83F210C41304FAA27A77D06734EDD (AHD03075:Required attribute Last Name is missing from object Contact)

    The idea here is to NOT let the pdm_ldap_import process look at or process contacts who have last name as NULL. We set a 'ldap filter prefix/suffix' manually in the NX.env file to achieve the above objective.
    Here are the steps:

    * set the ldap_user_object_class options manager value to blank (remove person)
    * add the following variables to the NX.env file:
    @NX_LDAP_FILTER_PREFIX=(&(objectClass=user)(mail=*)(givenName=*)(sAMAccountName=*)(sn=*)
    @NX_LDAP_FILTER_SUFFIX=)
    * make sure you see @NX_LDAP_USER_OBJECT_CLASS= [BLANK] in the NX.env file
    * restart services for the changes to take effect

    The above example
    objectClass=user - takes care of importing only 'users' type accounts excluding computers, mailboxes etc which are also 'person' type of accounts
    mail=* - filters out contacts where email_adress is NULL
    givenName=* - filters out contacts where first_name is NULL
    sAMAccountName=* - filters out contacts where userid is NULL
    sn=* filters out contacts where last_name is NULL

    You can include all or remove/add any more AD attributes as per your specific needs, the above can be used for reference for your specific filter prefix.

    Thanks,
    Vamsi
    Sr Support Engineer
    CA Technologies