![]() ![]() Reduce the frequency of collection updatesĪ general rule of thumb is not to update your collections more than is required.Įnsure that you sync the collection update schedule with other updates, such as the different discovery methods. If not explicitly required, use Equals to. Here are some examples of what you should not have in your collection queries: Reduce the complexity of collection queriesĪnother common issue I have seen is when the collection queries get overly complicated. In SCCM 2007, they had configured delta updates, which is the old term for incremental updates.ĭelta updates did not work well in SCCM 2007, but once you had migrated them to SCCM 2012, they started working, leaving major performance issues in its backwaters. ![]() One case that I have seen was when a customer had upgraded from SCCM 2007 to 2012. From what I’ve heard, keeping collections configured with incremental updates under 500 is a good idea. However, if you have hundreds of collections configured with incremental updates, you will most likely start seeing performance issues. Incremental updates are great because they can update every 5 minutes putting no significant strain on the SCCM server. Only use Incremental Updates for collections when required In most cases, regular queries can accomplish this. Sometimes, you might need this, but I would argue in most cases not.Ī common reason for many collections is using them for displaying devices or users using query-based collections. I have seen many customers with thousands of collections. Keep the number of collections to a minimum Reduce the complexity of the collection queries.When collection updates are not properly configured, you may see one or more of the following issues:īest practices for collections in SCCM include: ![]() There are two different other types of collection updates in Microsoft Endpoint Configuration Manager (SCCM): To keep collections up to date, they need to update on a set schedule. I provide a Powershell script for configuring the collection update in Microsoft Endpoint Configuration Manager (SCCM) in this blog post. This is something that I have seen firsthand with thousands of collections configured for incremental updates.Īccomplishing this for a few collections works fine using the GUI, but if you want to change collection update settings for hundreds or thousands of collections, this is not a viable option. The organization migrated from SCCM 2007, where Delta updates did not work.The IT administrator does not know how collections updates work. #Sccm run script schedule how toHow to configure collection updates using Powershell.Ī common reason for a Microsoft Endpoint Configuration Manager (SCCM) environment to become slow is misconfigured collection updates.How to find how collections are configured and performing.Reduce the frequency of collection updates.Reduce the complexity of collection queries.Only use Incremental Updates for collections when required.Keep the number of collections to a minimum. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |