Discovery not populating "Assigned To" user in CMDB

Dead Blade · ‎07-28-2017

I know the name of the probe that is suppose to populate the CMDB: Windows - OS Information / Win32_ComputerSystem.UserName

But this has never worked. I check the other post and I have computers with the "In Use" state, so that's not it.

I am wondering how to I enable this function to work. It is currently set to Active and discovery is running on the workstations.

Patrick DeCarl1 · ‎07-29-2017

Hi William,

OOTB property "glide.discovery.assigned_user_match_field" is set to use "user_name" field on the "sys_user" table to match the value discovery pulls back. If that value doesnt match what your system has, then you might need to change what field to use from sys_user to sync up.

All this can be found in the sensor of the probe.

View solution in original post

Dead Blade · ‎08-02-2017

But when I look at the CI record, his name is not in the assigned to.

Patrick DeCarl1 · ‎08-02-2017

Does CORP\bradley.****** match his user_name value on the sys_user table?

Dead Blade · ‎08-02-2017

Ah, the name is fully qualified as the USER ID (first.last@company.com) . Hmmm....

Dead Blade · ‎08-02-2017

So we probably have to edit the script to strip out the "CORP\" and add the @company.com after the user_name. Agree?

Patrick DeCarl1 · ‎08-02-2017

I would avoid updating OOTB code b/c you will miss the next update if SNC makes changes to code.

Look to store that value in sys_user via a LDAP pull or however your getting user data into sn. Then update property to put to new field.