Definitely some mystery to the process and I've seen the issue as well. Prior to SP1, if you forced an update on all systems, you effectively updated all collections, which you could see in colleval. The logic has changed some with SP1 so that it shouldn't be as big of a load.
Also keep in mind in you can only have 200 incremental collections, bad things happen when you pass 200, I've had a few clients do that. To find out how many collections are incremental run the following query. 1 = no incremental no schedule 2 = no incremental scheduled 4 = incremental no schedule 6 = incremental scheduled select * from v_collection where refreshtype = 6 Chris Nackers Microsoft MVP - Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected] [mailto:[email protected]] On Behalf Of Craig Andrew (OIZ) Sent: Friday, October 04, 2013 5:16 AM To: [email protected] Subject: RE: [mssms] Direct membership add of a new device record taking long time in SCCM 2012. In 2012 the All Systems is set to incremental. When you add a new computer it should be added to All Systems automatically and the collection eval should spot this and run an update of membership, triggering updates across collections set with All Systems as limiting, and which are set to incremental. But I have noticed on occasion that the All Systems, or rather the colleval, doesn't notice the change and only when either a membership update is initiated manually, or another computer is added, that it is updated. But like I said this only happens occasionally. Because of the various, albeit occasional, disturbances to the colleval, I started using orchestrator to stage the adding of new machines. Create a database, a table, and a runbook which will save all add new machine requests and process en bullk every ten minutes. Then use the runbook to check the coll memberships and include retries if necessary, once everything is ready give a status back that the ts can continue. It sounds like a lot of work, but just to get rid of these anomalies and give peace of mind that every single machine will stage correctly is worth it. You can also do this with a script but I find orchestrator more elegant. Andrew From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Ryan Sent: Freitag, 4. Oktober 2013 06:56 To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] Direct membership add of a new device record taking long time in SCCM 2012. My guess is this order is happening: 1) Computer record is created 2) Task sequence creates direct membership rule for computer 3) Collection refreshes because of the new rule, but limiting collection is all systems and computer isn't there yet so it isn't added 4) Computer is added to the All Systems collection --Some time later-- 5) Collection hits it's refresh schedule and adds the computer. I'd suggest doing an update membership refresh on the All Systems collection, sleeping for a few seconds, and then creating the direct rule. You may have more luck. On Thu, Oct 3, 2013 at 11:21 PM, Richard Zuraff <[email protected]<mailto:[email protected]>> wrote: So if we add the machine to the all systems first than the other collection. Would you think this would speed up the process? On Oct 3, 2013, at 10:47 PM, "Ryan" <[email protected]<mailto:[email protected]>> wrote: That makes sense... Most collections are going to be limited to All Systems, so if the new record isn't in all collections yet it won't be added. On Thu, Oct 3, 2013 at 10:34 PM, Jeff Poling <[email protected]<mailto:[email protected]>> wrote: I've seen this before and updating the membership on All Systems fixes it. Though updating All Systems might have an impact depending on how many devices are in your environment. On Thu, Oct 3, 2013 at 8:30 PM, Richard Zuraff <[email protected]<mailto:[email protected]>> wrote: During our imaging process we add a new computer to a single collection as a direct member. From there we than move it to a imaging collection. We are noticing since moving to SCCM 2012 it taking a long time before the records will show up in that collection. In 2007 it would show up in a 1-2 minutes. I've done some reading and this may be due to the limiting collections in SCCM 2012. We have a single Primary and the collection is limited on all Systems. Is anyone else having this issue?
