Schema modification: relaxing constraint from single-valued to multi-valued.

Discussion in 'Active Directory' started by Chuck Chopp, Jan 19, 2010.

  1. Chuck Chopp

    Chuck Chopp Guest

    I'm not seeing anything in the AD documentation on MSDN that indicates
    whether or not it is permissible to modify an existing attribute
    [previously created by an extension to the schema, not a base attribute]
    where the only change being made is to change the value of
    "isSingleValued" changes from TRUE to FALSE. At the time the change
    would be made, objects would already exist in the forest that have the
    attribute present with just a single value.

    In eDirectory, it is possible to do this, as well as making other
    modifications where a constraint is being relaxed, but you can't go in
    the opposite direction where a constraint is made more restrictive.

    Is there any sort of more advanced reference material regarding
    modification of existing schema entries? If not, I'll do some test
    coding and determine it empirically, but would prefer a to know up front
    if it's specifically not permitted.
    Chuck Chopp, Jan 19, 2010
    1. Advertisements

  2. Chuck Chopp

    Lee Flight Guest


    as isSingleValued is a system-only attribute I think you would be
    from making this change as you would not be able to modify it subsequently,
    have you found otherwise?

    Lee Flight
    Lee Flight, Jan 20, 2010
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.