none
modify-naming-attribute error using classical provisioning RRS feed

  • Question

  • I am replicating an AD structure to ADAM, using classical provisioning.

    But when I rename an object in AD, then while doing an Export to ADAM, I get the error modify-naming-attribute (The attribute cannot be modified because it is owned by the system) .

    Is there anything I can do to resolve this issue through the MA configuration? Should I add some code in the ADAM MAExtension?

    Thank you,

    Andreas

    Friday, November 23, 2012 1:04 PM

Answers

  • Hi Andreas,

    The user CN cannot be directly modified (export flow) from the Configure Attribute Flow - remove the export flow to cn from your AD MA.

    DN renaming (include CN) have to be renamed from the Provision function. ex.:

    dn = ADMA.EscapeDNComponent("CN=" + mventry["firstName"].Value + " " + mventry["LastName"].Value).Concat("OU=MyOu,DC=mydomain,DC=com");
    if (ADMA.Connectors.Count == 0)
    {
         csentry = ADMA.Connectors.StartNewConnector("user");
         csentry.DN = dn;
         ...
         ...
         csentry.CommitNewConnector();
    }
    else if (ADMA.Connectors.Count == 1)
    {
         csentry = ADMA.Connectors.ByIndex[0];
         csentry.DN = dn;
    }

    Remark: You have the possibility to change only the CN without the need to apply the all DN. ex.:

    csentry.RDN = mventry["firstName"].Value + " " + mventry["LastName"].Value


    Patrick Layani

    Saturday, November 24, 2012 9:11 PM
  • Try this.

    Cheers,
    Markus


    Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

    Monday, November 26, 2012 10:47 PM
  • Hi,

    Can you check this post.


    Patrick Layani

    Thursday, November 29, 2012 12:32 PM

All replies

  • Hi Andreas,

    The user CN cannot be directly modified (export flow) from the Configure Attribute Flow - remove the export flow to cn from your AD MA.

    DN renaming (include CN) have to be renamed from the Provision function. ex.:

    dn = ADMA.EscapeDNComponent("CN=" + mventry["firstName"].Value + " " + mventry["LastName"].Value).Concat("OU=MyOu,DC=mydomain,DC=com");
    if (ADMA.Connectors.Count == 0)
    {
         csentry = ADMA.Connectors.StartNewConnector("user");
         csentry.DN = dn;
         ...
         ...
         csentry.CommitNewConnector();
    }
    else if (ADMA.Connectors.Count == 1)
    {
         csentry = ADMA.Connectors.ByIndex[0];
         csentry.DN = dn;
    }

    Remark: You have the possibility to change only the CN without the need to apply the all DN. ex.:

    csentry.RDN = mventry["firstName"].Value + " " + mventry["LastName"].Value


    Patrick Layani

    Saturday, November 24, 2012 9:11 PM
  • Thank you Patrick,

    but now we are getting this error in the MVExtension when Full Syncing: "System.InvalidOperationException: Unable to rename non-leaf object."

    Any further help would be appreciated!

    Andreas

    Monday, November 26, 2012 9:48 AM
  • Try this.

    Cheers,
    Markus


    Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

    Monday, November 26, 2012 10:47 PM
  • Hi,

    Can you check this post.


    Patrick Layani

    Thursday, November 29, 2012 12:32 PM