This behavior is usually seen at a central site, but could potentially occur anywhere.Work from any errors reported in the component log files on the site server: sinvproc.log, dataldr.log, sinvproc.log, dataldr.log, One potential cause for this type of error is an inventory resynchronization.Inactive clients in SCCMWhen a client is no longer communicating with SCCM, you have a couple of options.But first, let’s learn why our clients become inactive and how to find them.Communication can include: So a client can be marked as inactive if it fails to update SCCM due to issues such as loss of connection, restrictive firewall settings, and client corruption. When dealing with inactive clients, you might run across false positives.
Verify that proper permissions are set for SCCM to update the registry keys. The slow processing can lead to backlogs of data in their respective inboxes.
After you have created the reference computer and captured an operating system image from that computer, you can use a task sequence to configure how to deploy that image to a destination computer.
For information about how you can use task sequences, see Planning a Task Sequences Strategy in Configuration Manager.
The easiest way to explain this is to understand how a client remains active.
A client remains active if it is discoverable and if it communicates with your SCCM servers.