I was creating a collection directly on the CAS like I do normaly within SCCM 2007 on a central site. The goal was to deploy a script on specific machines. I was having issue with the collection membership when I found that the CAS was having no colleval.log. I decide to look into site server components on the console and got a surprise.
In SCCM 2012, collection membership is part of site data so it’s the responsibility of SQL database replication. Data is replicated from primary to CAS. This is why collection evaluator component are on the primary only and the refresh lasted a few minutes longer.
Founder of System Center Dudes. Nick has been awarded in 2016 as a Microsoft MVP in Enterprise Mobility category.
Working as a senior SCCM and Intune advisor as well as a specialist Microsoft Cloud solutions specialist.