SCCM - Collection not updating

[CHiLL]

I am testing application deployment using two of our existing machines (test machines). I have a collection based on a query rule for these specific test machine names, which works as the machines appear in the collection. The applications were then installed onto these machines, which is grand. The query statement is:

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SYSTEM.Name like 'SPAREPC-25%' order by SMS_R_System.Name

Incremental updates is enabled for this collection.

 

However, I would like these applications to be deployed to machines that have only just been imaged. 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.

 

I then imaged two machines and matched the names EXACTLY to those that are in the query statement (copying and pasting). However, they are simply not appearing within the collection, many hours, even over 24 hours. Though, if I right click the collection and click 'Update Membership', they then appear in the collection!

 

I can't figure out why. My incremental updates are set at every 5 minutes within the site configuration and we only have 25 device collections and 15 user collections. (All of them use incremental updates). I've read that having a lot of collections can cause issues, but that's if I use over 200 collections!

 

Can anybody shed some light?

[Steve21]

Are these new machines/names to SCCM? or already in it just you're renaming a machine to match?

 

Incrementals only work on new machines and not ones that already exist. So if it already existed and has just been rebuilt it wouldn't add it until a full update (if you've got them to do it)

 

Steve

[CHiLL]

Are these new machines/names to SCCM? or already in it just you're renaming a machine to match?

 

Incrementals only work on new machines and not ones that already exist. So if it already existed and has just been rebuilt it wouldn't add it until a full update (if you've got them to do it)

 

Steve

Hi Steve, they are new machines to SCCM.

[Steve21]

And there's not an account already within SCCM that's called those names? (even if a new machine hardware wise).

 

Also are they within any sub-collections? Or are you querying it direct from the root? As the same applies, a sub-collection won't count as a new machine as it's already been added to a higher one etc

 

Steve

[CHiLL]

And there's not an account already within SCCM that's called those names? (even if a new machine hardware wise).

 

Also are they within any sub-collections? Or are you querying it direct from the root? As the same applies, a sub-collection won't count as a new machine as it's already been added to a higher one etc

 

Steve

No, there are no other machines within the SCCM database with the names that I'm using.

 

The machines get added automatically into the 'All Systems' collection, however my testing collection is limited to the 'All Systems' collection.

[ReadTheNetwork]

Is there anything obvious in Colleval.log?

Could you upload it to here or message me with the file. Plus the name of the collection to look out for.

 

Sorry - it's the collection's ID rather than the name .

You can see how often your collection would be changed/updated.

Edited August 4, 2016 by ReadTheNetwork

[CHiLL]

Is there anything obvious in Colleval.log?

Could you upload it to here or message me with the file. Plus the name of the collection to look out for.

 

Sorry - it's the collection's ID rather than the name .

You can see how often your collection would be changed/updated.

I've attached CollEval.log. SJW00068 is the collection in question.

[ATTACH]38232[/ATTACH]

[ReadTheNetwork]

From your log it seems like it's running every 5 minutes (as expected) and can see manual updates etc. Could you upload the SMSExec.log please.

[CHiLL]

From your log it seems like it's running every 5 minutes (as expected) and can see manual updates etc. Could you upload the SMSExec.log please.

There you go.

[ATTACH]38236[/ATTACH]

[ReadTheNetwork]

What version of SCCM are you using?

This might sound strange, could you add a direct rule to add a dummy machine into your collection? Then see if it updated after 5/10 minutes adding the query machines in.

[Steve21]

Aye your log file shows it's finding changes etc :s

 

As stupid as it sounds does your pc name actually equal "SPAREPC-25" or is it like "SPACE-PC252" just wondering whether it'll get upset about "SPAREPC-25%" if the first option as it's wanting something after the 5

 

Steve

[CHiLL]

What version of SCCM are you using?

This might sound strange, could you add a direct rule to add a dummy machine into your collection? Then see if it updated after 5/10 minutes adding the query machines in.

When adding the direct rule and entering the machine name, it asked me to select the machine resource list. I can confirm that doing it this way, the machines appeared instantly in the collection.

I was hoping that I can apply this to a limited collection, so when I deploy applications, I can just deploy them to a collection and not worry about having to manually add machines in, even newly imaged machines. As the collection should add the teacher machines, or the office machines, or the student machines and then the application deployments would work automatically.

 

Aye your log file shows it's finding changes etc :s

 

As stupid as it sounds does your pc name actually equal "SPAREPC-25" or is it like "SPACE-PC252" just wondering whether it'll get upset about "SPAREPC-25%" if the first option as it's wanting something after the 5

 

Steve

It's just 'SPAREPC-25'. However, the original two queries work, even with the % at the end of the machine name.

[ReadTheNetwork]

Sorry I meant add a dummy computer account, then see if the query runs correctly alongside the direct rule and adds new devices. I vaguely remember reading somewhere a behaviour similar to this with SCCM 2012 SP1. If you are using SP1, I'd recommend updating it. If you're not then it's not what I thought it would be.

 

It's an odd one - sounds like it's set up right (your query is fine, and it updates every 5 minutes). When you do a manual update, it does as you expected. If you can update SCCM try that, sounds like some odd configuration (behind the scenes). My depth of SCCM doesn't go that far sorry.

[CHiLL]

Sorry I meant add a dummy computer account, then see if the query runs correctly alongside the direct rule and adds new devices. I vaguely remember reading somewhere a behaviour similar to this with SCCM 2012 SP1. If you are using SP1, I'd recommend updating it. If you're not then it's not what I thought it would be.

 

It's an odd one - sounds like it's set up right (your query is fine, and it updates every 5 minutes). When you do a manual update, it does as you expected. If you can update SCCM try that, sounds like some odd configuration (behind the scenes). My depth of SCCM doesn't go that far sorry.

Sorry, I forgot to say, we're using SCCM 2012 SP2.

 

I'll be off next week, so I'll have to pick this up again the following week. Thanks for the help so far.

[ReadTheNetwork]

No worries, enjoy your break!

In that case try upgrading to a more recent version of SCCM. Bit of a long shot, but that might just fix something in the background

[CHiLL]

No worries, enjoy your break!

In that case try upgrading to a more recent version of SCCM. Bit of a long shot, but that might just fix something in the background

I think the next upgrade is 1151 and that's a bigger upgrade requiring a lot more tasks to perform! I think I'll leave that for now. This application deployment is purely in testing at the moment and not the highest on the agenda!