Discovery not populating "Assigned To" user in CMDB

Dead Blade
Kilo Guru

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.

1 ACCEPTED SOLUTION

Patrick DeCarl1
ServiceNow Employee
ServiceNow Employee

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

46 REPLIES 46

William not sure what your saying a issue is but if property is not listed under sys_properties table then the code you found is setting a default value


"   var nameField = gs.getProperty('glide.discovery.assigned_user_match_field', "user_name");"   user_name is the column it will use to match system user from your CI to sys_user table.


Hi Patrick, what I am saying is I don't believe my predecessors changes anything core like this and the assigned to is not working, never has to my knowledge.   When I look at the sys_properties table I do not see the things you are suggesting.   I will engage HI Support if this is a function that is suppose to be working.   Your replies have been very helpful thank you.


William,



Maybe this will help.



Go to sys_properties.list <-- type that in the nav text box


search on name = *glide.discovery.assigned_user_match_field


If property is in the system it will come up.


The value field will have user_name by default.



The code you posted above is the sensor script that is going to read the payload back from the mid server. In the script you see gs.getProperty('glide.discovery.assigned_user_match_field', "user_name");



I would look at the payload and see what "Win32_ComputerSystem.UserName;" is bring back. If the user doesnt exist in SN, then no assigned to is set.


That is helpful.   The glide is not bringing back anyone, never has.



find_real_file.png


How do I find the payload?


Look at the ecc record for input for the "Windows - OS Information" probe under discovery status. You will see in the xml payload the parameter or results for "Win32_ComputerSystem.UserName"   If nothing is there, then you might have a access issue. If there is data there, then you need to see if that value is inline with user_name field on the sys_user table.