Due to various factors (eg. QCS has been used prior to migration) target uses might have multiple x500 values, some of them will be conflicting with newly created legacyExchangeDN values. This can happen because by default the DSA doesn’t run a check and doesn’t verify the uniqueness of the newly created legacyExchangeDN attribute.
How can this be avoided?You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center