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-09-2017

Thanks Patrick, you have been extremely helpful.

Patrick DeCarl1 · ‎08-09-2017

No problem. Let me know what support comes up with.

Dead Blade · ‎08-16-2017

Hi Patrick, HI support let me know that, after the line userName = userName.substring(x + 1); , It will omit everything before the back slash and returning just first.last.

So basically I just modified the new sys_user field to be first.last and not DOMAIN\first.last.

bharath10 · ‎07-23-2019

Hi,

Any idea how we can achieve it without changeing/modiy ootb property or script/code.

R's,

Bharat

sk59 · ‎07-23-2019

I facing the same issue and followed through this post but couldn't find the payload with Win32_ComputerSystem.UserName.

Please help. I want to see what username we have received into servicenow as 'Assigned to' is not populated in cmdb