Name and cn attribute not populating with Create AD Object

[taarik_rahaman]

Hi everyone,

We're trying to get the Create User AD object working, but are a little stumped.   We're able to create the account and set all of the attributes needed successfully (e.g. sAMAccountName, displayName, givenName, sn, title, etc.) using the one activity.   However, when it comes to cn and name, these seem to be copied from sAMAccountName when the AD record is created.

What are we doing wrong please?   Is there maybe a group policy forcing CN and Name to be copies of sAMAccountName?   Or is it possible the problem is in my activity's object data field?

Thank you!

Taarik.

[Sandeep Kumar6]

Hi Taarik,

I think i got your problem , Its not your activity problem, In AD some attributes are there which have same value like you told CN and Name gets copied from SamAccountName in similar   ways we have "mobile" and "mobilephone"   which have same value , if you update "Mobile" it will update same value for "mobilephone"

and same goes for "officephone" and "telephonenumber" attributes so i think there is no problem from your side.

Thanks

Please hit like if you found your answer.

[taarik_rahaman]

iiglasia,

Thanks for your feedback.   I don't think this particular issue I'm running into is universal.   I think this customer has specifically configured AD to copy Name and CN from sAMAccountName.   I'll do some more digging and I'll aim to update this thread with the final result.

Thanks again!

Taarik.

[Sandeep Kumar6]

Yeah Taarik what you said may be correct. but i have observed in AD the information i have given in my last comment.

Please update if you find fither information about it.

Thanks

SAndeep

[taarik_rahaman · Accepted solution]

iiglasia,

The gentleman who assisted me from Support actually figured this out!   The Workflow config was the issue, at least in this case...though it may be due to how AD is configured...I have no idea.

Anyway, I re-read the documentation and it is definitely confusing at least to me:   "Whatever is passed as the Object name becomes both the samAccountName and the name of the new user in Active Directory."

How could the sAMAccountName be the same as the name?   Maybe that is how it's set by default?   In any case, because we were setting sAMAccountName in the Object data parameter of the same Create AD Object activity, the sAMAccountName was set correctly on the new accounts...so maybe overriding the behavior in the standard config.

I hope this helps someone else!

Regards,

Taarik.