Update User Details in Configuration Items>Users in SCSM

Darren_OLeary

Is there a method for updating an existing user's information in SCSM Configuration Items>Users after updating the details in Active Directory?

I have changed a user's logon username due to a change of their name.
When the AD connector syncs it will interpret the 'new' username as a completely new user and effectively create a duplicate user.

I want to be able to ensure that a user's history and identity is kept intact, such as their submitted SRs, IRs, CIs, etc.

Konstantin_Slavin-Bo

The CMDB uses the username as unique ID, which is why a change in username will result in a new user being created in SCSM. Read more about that here: https://blogs.technet.microsoft.com/manageabilityguys/2013/06/17/managing-username-changes-in-service-manager/

We have a large amount of changes of usernames, as our usernames depend on which department you're from. To handle this we have a runbook, which monitors new user CIs created in the CMDB, checks for an existing user with the same SID in the CMDB, moves all the relationships to the new user object (kinda like the script in the link), and then deletes the old user object. This ensures, that all the related WIs and CIs are moved to the new user object, and that the old user object does not interfere when searching for the users name.

Justin_Workman

@Konstantin_Slavin-Bo - Having the runbook match on SID and update relationships is a great idea!  Changing usernames tends to have a fairly large impact, but a runbook like this is a good defense against it!

Konstantin_Slavin-Bo

The CMDB uses the username as unique ID, which is why a change in username will result in a new user being created in SCSM. Read more about that here: https://blogs.technet.microsoft.com/manageabilityguys/2013/06/17/managing-username-changes-in-service-manager/

We have a large amount of changes of usernames, as our usernames depend on which department you're from. To handle this we have a runbook, which monitors new user CIs created in the CMDB, checks for an existing user with the same SID in the CMDB, moves all the relationships to the new user object (kinda like the script in the link), and then deletes the old user object. This ensures, that all the related WIs and CIs are moved to the new user object, and that the old user object does not interfere when searching for the users name.

Justin_Workman

@Konstantin_Slavin-Bo - Having the runbook match on SID and update relationships is a great idea!  Changing usernames tends to have a fairly large impact, but a runbook like this is a good defense against it!