I am sure that title sounds weird but in short I notice if I have a collection that is based on a Query the collection does not update if I modify the query in the monitoring section of SCCM 2012. 

I find that I need to remove the query from the collection, hit apply and then add the query back to the collection.  Then it updates.

Is there something I am missing when I am creating the collection in the first place that causes this?

thanks,

Rich

Once you've imported a Query in the collection query, there's no connection between the two anymore. So, changing the Query in the Monitoring node will not reflect to the collect

Collections based on queries are by definition non-static, that's the whole point of the query. The queries are evaluated dynamically though -- that would crush any non-trivial implementation regardless of the amount of money spent on hardware. Instead, the queries are evaluated on a schedule. By default, this is every 7 days but you can certainly adjust this if needed. There is also the ability to enable incremental collection evaluation which enables only new or updated resources that meet the query results to affect the collection's membership. You can also manually initiate the query evaluation on the collection as Benoit pointed out.

What Peter said is also true, there is no link between the queries in the monitoring section of the console and queries you've imported into a collection. Think of importing a query into a collection as a membership rules as a copy (because that's truly what it is).

Here's some more info on Collection Evaluation:

Collections based on queries are by definition non-static, that's the whole point of the query. The queries are evaluated dynamically though -- that would crush any non-trivial implementation regardless of the amount of money spent on hardware. Instead, the queries are evaluated on a schedule. By default, this is every 7 days but you can certainly adjust this if needed. There is also the ability to enable incremental collection evaluation which enables only new or updated resources that meet the query results to affect the collection's membership. You can also manually initiate the query evaluation on the collection as Benoit pointed out.

What Peter said is also true, there is no link between the queries in the monitoring section of the console and queries you've imported into a collection. Think of importing a query into a collection as a membership rules as a copy (because that's truly what it is).

Here's some more info on Collection Evaluation:

http://blogs.technet.com/b/senthilkumar/archive/2014/06/08/configmgr-2012-r2-collection-evaluation-overview.aspx

If you need to change the query, then you need to directly modify the one in the Membership tab of the collection. Be careful though, this can be very dangerous if you have things already targeted at the collection, like a task sequence deployed as required. It's *always* a good idea to test your query in the monitoring workspace first to verify the results of the query and avoid deployments being targeted at expected systems. This is most likely why the queries are copies as it would be way to easy to unknowingly change a query used in a collection and target something at the wrong systems.l

Also, if you are using incremental collection evaluation, why are you lowering the full collection evaluation time? Ultimately, there's nothing technically wrong with it, you just need to be very cognizant of the performance impact evaluating queries and updating collection membership has on the system and the possible ripple effects this may/will cause.