I have a need to allow users to capture some information into AD such as their first and last name, mobile number, etc. That in itself is not an issue and is straighforward. What I am attempting to do is to allow the user to update their login name. The users were all assigned random numbers as logon names and now the business wish to change this by presenting a form for the user to fill out.
In the workflow I have tried adding the sAMAccountName to the 'Other' field in 'Update AD' action, however the workflow fails with:
Error updating Active Directory account. Failed to set property 'sAMAccountName'.
Is there a way for me to allow this to work so the login names can be updated?
Solved! Go to Solution.
I managed to update that attribute and the user is able to login with the newly updated login information, which works great. I am contunuing to test this however it does seem to function quite well.
Users are able to login with email@example.com as well as domain\new, however when logging in they are logged into the new profile. The sAMAccountName attribute is what is used to determine the account.
Any feedback from others who have tried this would be most welcome.
Can you post how you went about solving this so that others will have the answer if they have the same question?
Thanks and glad you figured it out.
Sure thing. So the issue at hand was relatively straight forward and my main stumbling block was a query that was giving me incorrect results when I went looking for changes in AD with my action. Once I cleared out my list and started from scratch, it was able to work.
The issue I had was the 'initiator' below in the workflow, and I was using a different account that I am used to and was looking at the wrong account for changes in AD.
How I got it to work:
In the 'AD fields to update' select the drop down >> Other >> Add
Enter in sAMAccountName (ensure spelling is exactly the same as the attribute name in AD)
What this changed was the sAMAccountName and the pre-Windows 2000 logon name. It does not change the 'Windows Login Name' - see below:
You will not be able to login with domain\oldname but if you did oldname@domain you can still login, however it will change to display the new updated information. When you login with the new account name the same profile exists with the same permissions and access and the user is able to work without interruption.
I'm left now trying to see how to update the 'User logon name' field.