<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Threshold on Anything About IT</title><link>https://www.verboon.info/tags/threshold/</link><description>Recent content in Threshold on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Aug 2013 20:07:46 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/threshold/index.xml" rel="self" type="application/rss+xml"/><item><title>ConfigMgr 2012 Script for Incremental Collection threshold</title><link>https://www.verboon.info/2013/08/configmgr-2012-script-for-incremental-collection-threshold/</link><pubDate>Mon, 05 Aug 2013 20:07:46 +0000</pubDate><guid>https://www.verboon.info/2013/08/configmgr-2012-script-for-incremental-collection-threshold/</guid><description>&lt;p&gt;As described within the &lt;a href="http://social.technet.microsoft.com/wiki/contents/articles/11215.system-center-2012-configuration-manager-best-practices.aspx#Best_Practices_for_Collections"&gt;ConfigMgr 2012 Best Practices Wiki&lt;/a&gt; on TechNet it’s recommended to keep the number of collections with incremental updates enabled to around 200, this to prevent evaluation delays. So I thought it might be a good idea to keep an eye on collections with incremental updates enabled within our infrastructure using a PowerShell script.&lt;/p&gt;
&lt;p&gt;The property &lt;strong&gt;RefreshType&lt;/strong&gt; within the &lt;strong&gt;SMS_Collection&lt;/strong&gt; WMI class defines how Configuration Manager refreshes the collection. According to the documentation on MSDN the property can have the following 3 values.&lt;/p&gt;</description></item></channel></rss>