I’m running into an issue with the Microsoft SCCM Devices app that we have integrated with IIQ. I have enabled the mapping options to create, update, and delete assets in IIQ based on SCCM data. For import options, I have selected:
Update asset owner
Unassign owner if primary user is blank
Remove owner if the primary user can’t be matched
Problem
It seems like IIQ is not correctly correlating asset ownership with the Primary User(s) field in SCCM.
For example, when I search for devices assigned to myself in IIQ, it returns over 50 assets. However, after checking SCCM:
I am correctly listed as the primary user for only my desktop and laptop.
Many of the other assets already have a correct primary user assigned, but this information is being ignored.
Some assets don’t have a primary user listed, but I appear as a user who has logged into them within the last 90 days (which makes sense since I’m a Windows technician and log into many devices).
Additional Configuration Details
I have weekly verification enabled.
Verification is set to review the last 30 days and allow shared devices (since many desktops are used by multiple users).
Has anyone else experienced this issue? Is there a known workaround or configuration setting I might be missing?
Any insights would be greatly appreciated!
Thanks in advance.
Page 1 / 1
Hi @BHainline 78787a0 wwps ! Thank you for submitting your question. I am happy to take a look at this for you.
In order to troubleshoot, would you be able to provide a few asset tags, that way I can investigate the issue.
Thanks so much!
Of course! Here are three assets:
BE-DCLEARMANLT - This asset shows the correct primary user in SCCM, but shows that I am the owner in IIQ.
GA-AWOOTERSLT - This asset shows no primary user in SCCM, but shows that I am the owner in IIQ.
GA-157TEACHLT - This asset shows multiple primary users (of which I am not one) in SCCM, but shows that I am the primary user in IIQ.
Hi @BHainline 78787a0 wwps sorry for the delay. I have had to do some investigation. I started with (GA-AWOOTERSLT) . There are a couple issues at play here:
There are two assets with that asset tag. One is in a missing status and the other is active. If you go to apps → SCCM→ Asset History → enter that asset tag. You will see those two asset records and notice it is skipping changes for the one in the missing status. If you look at the other asset, the active one, you are listed as the primary user AND owner email; which is the field SCCM looks at to update owner.
So based on the data we are receiving from SCCM, this looks to be updating correctly.
We may have to tackle these 1 by 1 but I wanted to get this information to you first.
Please let me know if you have any questions!
Hi Melissa,
That’s strange. If I use the Asset Explorer and select the Asset Type as Devices, and then filter for the status of Missing, I only get four results. None of which are Windows devices. The results I get are three Chromebooks and one printer.
If I search for that asset, I only get one result.
Additionally, when I try to search for asset history in the SCCM app, I get no results no matter the asset name that I enter.
Thank you,
Brett Hainline
Hi @BHainline 78787a0 wwps ! Good Morning.
If you go to SCCM → Sync History → enter that asset tag, it will show you records of each sync. Go to February 13th and enter (GA-AWOOTERSLT). It looks as if the ‘missing’ device was deleted on that date and from there, it was re-created on 2/14 and the owner was set to you.
There is an iiQ Admin setting I can turn on that may help weed some of these issues out. See below.
However, aside from the ‘missing’ asset, the active one with that asset tag still has your name listed as the primary user, which is why it is being updated as such.
I hope this makes sense!
I think there must be some kind of confusion here. The active asset in IIQ should match what comes from SCCM.
That asset (GA-AWootersLT), did not have a primary user set in SCCM. Therefore, it should not assign any user when it imports into IIQ, correct?
Hi @BHainline 78787a0 wwps Under SCCM → Asset History is where I am seeing this information.
Your name is listed under the primary users custom field section. See screenshot below.
I understand that my name is listed in IIQ as the primary user of the device, but that is not what SCCM says at all. It seems that IIQ isn’t being populated with the correct information from SCCM. Here is a screenshot of that device in SCCM with the primary user field blank:
@BHainline 78787a0 wwps I think I found the culprit.
SCCM identifies the owner email as the primary user. Please see below.
Your name is listed under that field for this asset.
What I am not understanding is how SCCM is saying that my email address is associated with those devices.
Is the IIQ import not associating with the Primary User(s) field in SCCM? Most of the 50 some devices that it says that I am the primary user in IIQ only show that I was just one of the people to log into the device and not the primary user at all. Why is it not pulling the email from one of the other users that have logged into the device in the past 90 days?
@BHainline 78787a0 wwps I may have to get you to submit a ticket to support for this. From my understanding, I don’t think SCCM pulls the last logged in user. It looks at the primary assigned user, from my knowledge.
Would you be able to submit a ticket to support?
Please let me know if you need assistance!
Thank you
@BHainline 78787a0 wwps Hey there, I just wanted to follow up on this thread. For SCCM, we only bring over the primary user versus the last logged in user so that is not something we support at this time. You can submit this as an enhancement request here: https://community.incidentiq.com/ideas
Kathryn,
The problem that I am having is the opposite. SCCM seems to be taking one of the last logged in users (me for example) and completely ignoring the Primary User(s) field. I have almost 60 devices that say I am the asset owner in IIQ, but SCCM only has me in the Primary User(s) field for my desktop and laptop.
Thank you,
Brett Hainline
@BHainline 78787a0 wwps That sounds backwards so lets get a ticket submitted for that! Support will be able to best guide you from here.