Managing "Assigned To" for Asset and Discovery

[pgd]

Good morning Community,

We currently utilize Discovery, CMDB and Asset Management within SNOW.   We also supplement our discovered data with a feed from our Microsoft SCCM installation.   Recently, we've been having discussions about the quality of "Assigned To" data.   Currently, this field is populated with the user to last log into a machine.   We also notice is some cases there is no value populated (either from discovery or SCCM).   It seems unlikely that a user has never logged into the machine, so there must be something else occurring.   A further issue is that Technicians or Service Desk colleagues will be assigned to multiple devices at any given time, since they log into workstations other than their own.

Our goal is to have this Assigned To field populated for all workstations, with the accurate user that is assigned the device.   However, we also want to cross check that user against the most recently logged-in user.   My solution is to create a new field, Last Log-in User, and alter the discovery code to populate this field instead of Assigned To.   Then, we create a process to manually populate Assigned To at time of device deployment.

Before we develop this change, I wanted to see if anyone else in the community has experienced similar issues, and what their solution was to the problem.   Thank you in advance for any feedback!

Respectfully,

Patrick Dietzel

[Community Alums]

I agree with Robo. Your approach is sound, and better gets to the use of Assigned to, which is a particularly important field when it comes to Software Asset Management.

Another approach I've seen used is to create some scripts to determine what user has logged in the most in the past month to use as the Assigned to. I actually prefer your approach as it better ensures this value is not changed automatically on you.

[jkoenig_mgm]

I know this is an old thread, but I have another way of looking at this, and I currently perform this fucntion manually, (we are JUST now building out our CMDB).

Using a User Affinity, instead of last login is how you want to assign users, and you want to only assign users via SCCM discoveries, that have a single User affinity record. 

To do this, you'll first need to set your user affinity requirements up in SCCM to be something like "x hours over a period of time = primary user" (I'm not an SCCM expert, as you can tell). Then from there you will want to calculate how many users flagged per host, and then only assign users with machines with single users. 

Hope this makes sense. If not, I'm open to sharing some of my calculation snipits and sccm queries. As I stated, i'm doing all this manually (using power bi to build the reports, and importing the assignee changes manually into our database)

[Lakshmi Prabha1]

Hi,

We have the same requirement. Are you able to find a solution for this issue? Have u created a new field and populated the last logon through Discovery? Please advice.