SCCM 1810 and Windows 10 Defender Definitions Updates

%3CLINGO-SUB%20id%3D%22lingo-sub-391272%22%20slang%3D%22en-US%22%3ESCCM%201810%20and%20Windows%2010%20Defender%20Definitions%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-391272%22%20slang%3D%22en-US%22%3E%3CP%3EUntil%20recently%20we%20had%20Auto%20deployment%20package%20that%20picks%20up%20the%20latest%20definition%20and%20deploys%20it%20our%20to%20our%20client%20based.%26nbsp%3B%20%26nbsp%3B%20Up%20until%20last%20friday%20this%20work%20perfectly%20-%20it%20seems%20like%20we%20did%20have%20a%20bad%20definition%20that%20was%20download%20from%20microsoft%20and%20pushed%20out%20to%20a%20certain%20number%20of%20clients%20-%20it%20created%20a%20blank%20folder%20under%20their%20ccmcache%20folder%20which%20cannot%20be%20deleted.%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BLooking%20at%20the%20WUAHandler%20logs%20on%20the%20client%20when%20doing%20software%20updates%20scans%20-%20it%20is%20hit%20or%20miss%20or%20very%20random%20when%20it%20picks%20up%20our%20onsite%20WSUS%20server.%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3BDoes%20anyone%20know%20if%20something%20changed%20in%20the%20March%2019%20updates%20for%20Windows%2010%20that%20the%20change%20update%20behavior%3F%26nbsp%3B%20%26nbsp%3B%20We%20did%20install%20the%20latest%20update%20for%20SCCM%201810.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advanced.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-391272%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EEndpoint%20Protection%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESoftware%20Update%20Management%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-549552%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%201810%20and%20Windows%2010%20Defender%20Definitions%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-549552%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F54954%22%20target%3D%22_blank%22%3E%40Eric%20Sabo%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-549556%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%201810%20and%20Windows%2010%20Defender%20Definitions%20Updates%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-549556%22%20slang%3D%22en-US%22%3E%3CP%3EYou%20need%20to%20recreate%20a%20new%20ADR.%26nbsp%3B%20Once%20it%20successfully%20runs%20yo%20can%20disable%20original%20ADR%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F263909%22%20target%3D%22_blank%22%3E%40DANBPA%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Until recently we had Auto deployment package that picks up the latest definition and deploys it our to our client based.    Up until last friday this work perfectly - it seems like we did have a bad definition that was download from microsoft and pushed out to a certain number of clients - it created a blank folder under their ccmcache folder which cannot be deleted.     Looking at the WUAHandler logs on the client when doing software updates scans - it is hit or miss or very random when it picks up our onsite WSUS server.     Does anyone know if something changed in the March 19 updates for Windows 10 that the change update behavior?    We did install the latest update for SCCM 1810.

 

Thanks in advanced.

2 Replies
Highlighted
Highlighted

You need to recreate a new ADR.  Once it successfully runs yo can disable original ADR

@DANBPA