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

So in conclusion, the User record has the first.last@company.com in the User ID (user_name) field. The glide is producing the user_name as "CORP\first.last". So we will need to add a new field to capture the "CORP\first.last" from AD and match user_name in the sys_user table to the new field in the sys_user table. Correct?

Patrick DeCarl1 · ‎08-02-2017

Where ever you put the new " "CORP\first.last" value, you will change the property value with new field from sys_user. So you wont use user_name in property.

Dead Blade · ‎08-02-2017

Yup, exactly what I was thinking. And that won't effect any future SN version updates correct? Or will I need to check on that change to sys_properties?

Patrick DeCarl1 · ‎08-02-2017

The property will have a skip upgrade record but that is normal.

Dead Blade · ‎08-08-2017

Hi Patrick, I added a new sys_user field, I modified the sys_properties with the new field name and I updated "var nameField = gs.getProperty('glide.discovery.assigned_user_match_field', "new_field");".

The ECC log shows the data coming in as expected but SN is not updated the Assigned to. Should I get Hi Support involved?