Results 1 to 3 of 3

Thread: Custom fullname attribute settings ignored by ADMA

  1. #1
    Join Date
    Feb 2009
    Posts
    56

    Custom fullname attribute settings ignored by ADMA

    hie friends,

    When I tried to configure the ADMA to create a customized Full Name attribute, the objects unexpectedly use the relative distinguished name of the metaverse object i.e. a relative distinguished name is the metaverse object's common name.
    When this problem occured, error messages are not logged in any of the log files to warn that the custom configuration is ignored.

    What is the cause of this problem ? Can anyone help me solving this........

    thanks

  2. #2
    Join Date
    Nov 2005
    Posts
    3,026

    Re: Custom fullname attribute settings ignored by ADMA

    This problem may occur if -
    - a multiple-component relative distinguished name exists in the metaverse distinguished name ($mv.dn).
    - the Active Directory relative distinguished name and the connector space relative distinguished name must match;
    (however, Active Directory does not support multiple-component relative distinguished names)

    The New Connectors template contains a code that automatically modifies the common name if a plus sign (+) is present in the distinguished name of the object. This functionality ensures that the relative distinguished name that MMS builds for the Active Directory object is compliant with the Active Directory requirements. The relative distinguished names must match to guarantee that the new Active Directory object is successfully discovered by MMS during subsequent discoveries.

  3. #3
    Join Date
    May 2008
    Posts
    2,680

    Re: Custom fullname attribute settings ignored by ADMA

    To resolve this problem:

    1. Use Compass to log on to MMS as an administrator.
    2. Click Management Agents on the Bookmarks menu in the left pane.
    3. Click the appropriate ADMA in the right pane.
    4. Click Design MA on the Actions menu in the left pane.
    5. Click the Control Connected Directory tab.
    6. Click the Output Construction Templates tab.
    7. Click the New Connectors tab.
    8. Locate the following section:

      Code:
      # We need to escape the  comma in the RDN
      $v_fullName = $replace($v_fullName, ",", "\,")
      
         if $EXISTS($v_fullName) = TRUE
            then
                if $EMBEDDED(" + ", $mv.dn) = TRUE
                then
                   $v_cdDn = CN= $GET_SUBSTRING($DN_COMPONENT($mv.dn, 1), "", " + ") , $parent("$v_cdDn")
                   else
                   $v_cdDn = CN= $v_fullName , $parent("$v_cdDn")
                endif
            endif
    9. Replace the code that you located in the previous step with the following code:

      Code:
      if $EXISTS($v_fullName) = TRUE
            then
               if $EMBEDDED(" + ", $v_fullname) = TRUE
                then
                 $v_cdDn = CN= $GET_SUBSTRING($DN_COMPONENT($v_fullname, 1), "", " + ") , $parent("$v_cdDn")
                 else
               $v_cdDn = CN= $v_fullName , $parent("$v_cdDn")
              endif
        endif
    10. Click OK.

Similar Threads

  1. Replies: 8
    Last Post: 06-05-2012, 12:21 PM
  2. No custom graphics settings in Crysis 2
    By Reuben 1 in forum Video Games
    Replies: 6
    Last Post: 27-03-2011, 05:35 AM
  3. LDIF syntax for adding an already created custom attribute to OU
    By Deffen-Baugh in forum Active Directory
    Replies: 4
    Last Post: 30-07-2009, 07:00 PM
  4. Custom AD attribute - [WP]
    By OmJaa in forum Active Directory
    Replies: 3
    Last Post: 11-03-2008, 07:17 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,511,329.89872 seconds with 16 queries