Skip to main content

In the Microsoft app you can check a box, under General settings>mapping> that says, 

 

The question is what happens to the device if you do not check that box? In iiQ is the device’s status changed? If so, to what? Or, is the device just ignored by iiQ? Will the sync history indicate the device wasn’t found in Microsoft? Are there any rules we can setup to set status or send an alert to the technicians if the device is not found in Microsoft SCCM? 

Hi Vince,

 

If the deleted option is enabled and a device is removed from SCCM, it will be deleted from IIQ.  The timeline/history goes along with that.  This includes the sync history.

If you want to keep the asset in IIQ, you could always change the status to “Out of Service” or “Surplus”.  This will keep all the data/history but not interfere with your “in service” devices.

 

Please let me know if you have any other questions,


Scott


Thanks svanassche!

But how does iiQ know to change the status? Are you using a rule? If so, how is the rule configured? 


You will have to change the status yourself, which is a pain.


I am running into the same issue with the Jamf integration… we don’t want to delete the assets out of iiQ, for records purposes, but we do want to set them to a different status after they’ve been deleted/removed from Jamf (or in your case, Intune).

I made this idea for this exact reason.

Being able to use this filter for when the last time it was seen in one of these syncs, and take action via a rule, would be fantastic… and eliminate any manual data manipulation (manually change statuses, etc)


@jclark Thanks. Do you use a timeframe to filter on “last sync?” 


There’s not currently a filter for the last time a device was synced via the integrations. That is the problem we are trying to resolve.


@jclark  you beat me to responding, but you answered exactly what I was going to say  😁.  Thank you


@jclark @svanassche_iiQ2 Love the team work! 😄


@jclark  

There’s not currently a filter for the last time a device was synced via the integrations. That is the problem we are trying to resolve.

@jclark  you beat me to responding, but you answered exactly what I was going to say  😁.  Thank you

 


Reply