Sccm update collection membership not updating
Client from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM. So I updated the collection with two more query rules, one for each of the two other spare machines I'm using (amending the name within the query statement), so there are now four query rules for this one collection in total.
However, I would like these applications to be deployed to machines that have only just been imaged.
The alert should be resolved after completion of the next scheduled processing cycle once this is done.
Hi everyone Roberto Rodriguez here with a Configuration Manager support tip for you.You shouldn't use incremental on anything other than the primary built in collections (as a rule of thumb) as they hammer the SQL instance every 15 minutes. Have you reviewed the local client logs for inventory to validate that it is working though? Sorry, I'm still a little new to administering SCCM, so some of my questions may a little dumb.We also have other collections that separate the computers by Model number, but those collections have stopped working as well. For some reason all collections have stopped updating except the "Windows 10 Machines" collection.I've since added an exception to Trend File scanning for the PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\inboxes folder and I've noticed a considerable improvement - I'll post back after a week or so to let you know how it's going.It seems the actual problem here was down to the sheer volume of collections running updates.