narrow default width wide
colour style colour style colour style colour style

SCCM Speedup FAQ


What is SCCM Speedup?

SCCM Speedup is an application that runs as a Windows service that will dramatically decrease the amount of time that SMS/SCCM takes to process changes that are required for software to deploy to your clients.

How does it work?

SCCM Speedup monitors both Active Directory and SMS/SCCM for any changes that are relevant to Software Distribution.

  • New SMS/SCCM clients
  • Computers that change Active Directory OUs
  • Computers that change AD group memberships for an AD group that is associated with a Collection

What is required to run SCCM Speedup?

The application can be installed on any Windows system with .Net 4 installed. You can install it on your Primary but that isn't required. We also require that any Active Directory domains that are being monitored are at least in 2003 Native Mode (2008 mixed-mode is fine)

Why do you require 2003 Native Mode?

Microsoft introduced some new attributes to the schema that help SCCM Speedup to operate so efficiently. By taking advantage of these new attributes, we can do things like dig into AD group changes to determine exactly what changed. Other similar products cannot do this so they could potentially create thousands of DDRs just because of a single group membership change.

Will we need to re-do all of our Collection Queries?

Absolutely not. SCCM Speedup isn't replacing what AD System Group Discovery does. It is just improving it.

Why does it take so long for software to deploy without SCCM Speedup?


If you are using AD groups and/or AD OUs in your Collection Rule Queries, SMS/SCCM has two distinct processes that have to run before any new members will make it into your Collections:

  • AD System Group Discovery has to run. This is what pulls the AD Group and OU information from AD into SMS/SCCM for your clients. When it runs, it processes ALL¬†enabled AD computer objects. So, if you have 20000 computer objects in AD and only 10 have changed, you still have to wait for the Primary to process all of those DDRs.
  • The Collection(s) have to refresh after the DDRs have been processed. Once again, SMS/SCCM isn't very intelligent about this. You have to decide on a static schedule for all of your individual Collections. If you set the update schedules too fast, the Primary won't be able to keep up and they will all just end up waiting on each other. If you set it too slow, it can take forever for them to update (and therefore for software to deploy)

end faq