Download and own part 1 to 21 of the SCCM Installation Guide in a single PDF file.
The PDF file is a 162 pages document that contains all informations to install and configure SCCM 2012 R2 or SCCM 1511 and later (Current Branch).
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.
These are Active Directory computer accounts that have gone stale (no longer linked to a physical computer).
Are there any common factors in the file computer objects that are missed ? I haven't checked the event logs (I will now) however I did check the and there is no error, it performs like the location isn't being interrogated (although if I add a new object in it gets discovered so the location must be).
Is it the same machines each time or a random subset? They have two NICs and both are on static addresses. I know this Thread is old but did you ever discover what was causing this anomaly Busby?
I've also tried modifying the rules to make these computers memebers and that refuses to work too. Essentially right now I cannot move any computer to any collection, but the All Systems/All Clients collection are picking up new computers no problems.
Anything different about firewall settings or A/V settings? Config Manager discovery runs through AD structure - not IP range.
The only pre-req is read only access to the AD structure. That's why I started with the object attributes in AD. OK, I may be applying some incorrect logic here, but to me, discovery means identifying a machine on the network that is new/different to other machines.
For this post, I’ll add the Description attribute from a computer account.
Once completed, initiate a Full Discovery on Active Directory System Discovery by right clicking it and choose Run Full Discovery Now Wait for the scan to finish, you can monitor the process by opening on your site server.