SCCM End point package size

%3CLINGO-SUB%20id%3D%22lingo-sub-110579%22%20slang%3D%22en-US%22%3ESCCM%20End%20point%20package%20size%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-110579%22%20slang%3D%22en-US%22%3E%3CP%3ESize%20of%20End%20Point%20package%20in%20SCCM%20is%20between%20800%20MB%20and%201.5%20GB%2C%20is%20this%20normal%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-110579%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EEndpoint%20Protection%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-114964%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20SCCM%20End%20point%20package%20size%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-114964%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%20I%20replied%20in%20the%20wrong%20place.%20We%20have%20created%20an%20ADR%20for%20Endpoint%20definition%20updates%20and%20Defender%20Definition%20Updates.%20The%20Endpoint%20package%20size%20at%20distribution%20is%20between%20800-900MB%2C%20and%20the%20Defender%20package%20is%201.4GB.%20We%20check%203%20times%20a%20day%20for%20definitions%20in%20the%20past%2012%20hours.%20A%20definition%20is%20usually%20145MB%20average%2C%20so%20why%20is%20the%20ADR%20package%20so%20large%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-113289%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20SCCM%20End%20point%20package%20size%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-113289%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20ADR%20uses%20an%20existing%20package.%20If%20we%20decided%20to%20create%20a%20different%20package%20each%20time%2C%20it%20creates%20a%20%E2%80%98software%20update%20group%E2%80%99%20per%20definition%3B%20that%20becomes%20a%20management%20nightmare%20when%20clearing%20superseded%20updates%2C%20as%20it%20takes%20a%20long%20time%20to%20load%20the%20list%20when%20removing%20memberships.%3C%2FP%3E%3CP%3EWe%20remove%20superseded%20packages%20every%20week%20from%20the%20deployment%20package.%20Shouldn%E2%80%99t%20it%20keep%20the%20latest%20definition%20only%3F%3C%2FP%3E%3CP%3EEnglish%20is%20selected%20only.%3C%2FP%3E%3CP%3EDo%20you%20have%20a%20different%20recommendation%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-112784%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20SCCM%20End%20point%20package%20size%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-112784%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20the%20ADR%20set%20to%20create%20new%20packages%20or%20use%20an%20existing%3F%3C%2FP%3E%3CP%3EHave%20you%20looked%20at%20the%20content%20to%20make%20sure%20it's%20pulling%20the%20correct%20patches%3F%3C%2FP%3E%3CP%3EAlso%20consider%20language%20packs%20in%20the%20size.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-112490%22%20slang%3D%22en-US%22%3ERE%3A%20SCCM%20End%20point%20package%20size%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-112490%22%20slang%3D%22en-US%22%3EClarification%3A%202%20separate%20ADRs%20for%20each%20product.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-112489%22%20slang%3D%22en-US%22%3ERE%3A%20SCCM%20End%20point%20package%20size%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-112489%22%20slang%3D%22en-US%22%3EHi%20Yvette.%20We%20have%20created%20an%20ADR%20for%20Endpoint%20definition%20updates%20and%20Defender%20Definition%20Updates.%20The%20Endpoint%20package%20size%20at%20distribution%20is%20between%20800-900MB%2C%20and%20the%20Defender%20package%20is%201.4GB.%20We%20check%203%20times%20a%20day%20for%20definitions%20in%20the%20past%2012%20hours.%20A%20definition%20is%20usually%20145MB%20average%2C%20so%20why%20is%20the%20ADR%20package%20so%20large%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-111803%22%20slang%3D%22en-US%22%3ERE%3A%20SCCM%20End%20point%20package%20size%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-111803%22%20slang%3D%22en-US%22%3EHi%20Salem%20Can%20you%20be%20more%20specific%3F%20What%20package%20are%20you%20referring%20to%3F%20thanks%20-Yvette%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Size of End Point package in SCCM is between 800 MB and 1.5 GB, is this normal?

6 Replies
Highlighted
Hi Salem Can you be more specific? What package are you referring to? thanks -Yvette
Highlighted
Hi Yvette. We have created an ADR for Endpoint definition updates and Defender Definition Updates. The Endpoint package size at distribution is between 800-900MB, and the Defender package is 1.4GB. We check 3 times a day for definitions in the past 12 hours. A definition is usually 145MB average, so why is the ADR package so large?
Highlighted
Clarification: 2 separate ADRs for each product.
Highlighted

Is the ADR set to create new packages or use an existing?

Have you looked at the content to make sure it's pulling the correct patches?

Also consider language packs in the size. 

Highlighted

The ADR uses an existing package. If we decided to create a different package each time, it creates a ‘software update group’ per definition; that becomes a management nightmare when clearing superseded updates, as it takes a long time to load the list when removing memberships.

We remove superseded packages every week from the deployment package. Shouldn’t it keep the latest definition only?

English is selected only.

Do you have a different recommendation?

Highlighted

Sorry I replied in the wrong place. We have created an ADR for Endpoint definition updates and Defender Definition Updates. The Endpoint package size at distribution is between 800-900MB, and the Defender package is 1.4GB. We check 3 times a day for definitions in the past 12 hours. A definition is usually 145MB average, so why is the ADR package so large?