Prin utilizarea acestui site, sunteți de acord cu Politica de confidențialitate.
Accepta
EnterineEnterineEnterine
  • ACASĂ
  • Pro
  • Tehnologie
  • Microsoft
    • Azur
    • ConfigMgr/SCCM
    • Dpm
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Birou 365
    • Office Insider
    • Putere bi
    • Skype
    • Server SQL
    • Echipe
  • Ferestre
    • Centrul de administrare Windows
    • Client Windows
    • Windows Server
  • Lista de colecție de interogări SCCM
Lectură: Automatic deployment rule failed with error code 0X87D20417
Redimensionare fontAa
EnterineEnterine
Redimensionare fontAa
  • ACASĂ
  • Pro
  • Tehnologie
  • Microsoft
  • Ferestre
  • Lista de colecție de interogări SCCM
Căutare
  • ACASĂ
  • Pro
  • Tehnologie
  • Microsoft
    • Azur
    • ConfigMgr/SCCM
    • Dpm
    • Orchestrator
    • Hyper-V
    • Microsoft Edge Insider
    • MSI
    • Birou 365
    • Office Insider
    • Putere bi
    • Skype
    • Server SQL
    • Echipe
  • Ferestre
    • Centrul de administrare Windows
    • Client Windows
    • Windows Server
  • Lista de colecție de interogări SCCM
Lista de colecție de interogări din Configuration Manager
Configmgr

Automatic deployment rule failed with error code 0X87D20417

Publicat: February 11, 2024
1 Min Citește
Cota

The automatic deployment rule failed with error code 0X87D20417. In my SCCM environment (1610 CB with last updates) I get an automatic deployment rule failed with error code 0X87D20417.

When I check the ruleengine.log, it reports these lines:

Downloading content with ID 16803330 in the package SMS_RULE_ENGINE
Failed to download the update from internet. Error = 12002 SMS_RULE_ENGINE
Failed to download ContentID 16803330 for UpdateID 16812681. Error code = 12002 

To fix the Configuration Manager error code 0X87D20417, try the below-mentioned steps. If none of these worked post it in the comments.

  • Try recreating the automatic deployment rule again. Deleting the existing ADR and creating a new one works most of the time.
  • Automatic Deployment Rules don’t work when you use specific proxy authentication on a site server. There is a hotfix available for this issue. Note that the hotfix is applicable only if you have installed the Microsoft System Center 2012 R2 Configuration Manager.
  • Error code=3 means the system cannot find the path specified. So ensure you have provided the correct path to download the updates.
  • Wait some time, there may be problems not on your side.
  • Restart your Configuration Manager server.

Etichetat:Centru de sistemManager de configurare System CenterPrevizualizare tehnicăWSUS
Articolul precedent Supercharge Your Development with Docker on AlmaLinux 9
Articolul următor Configuration Manager Discovery Methods Configuration Guide
4 Comments 4 Comments
  • John C Storbeck says:
    February 23, 2021 at 6:59 am

    I am having this as well started a week ago on ADRs that did not change.

    Downloading content with ID 18060039 in the package, srctype = 1 SMS_RULE_ENGINE 2/23/2021 10:54:46 PM 5528 (0x1598)
    Failed to download the update content with ID 18060039 from internet. Error = 80 SMS_RULE_ENGINE 2/23/2021 10:54:53 PM 5528 (0x1598)
    Failed to download ContentID 18060039 for UpdateID 18078372. Error code = 80 SMS_RULE_ENGINE 2/23/2021 10:54:53 PM 5528 (0x1598)
    Downloading content with ID 18060040 in the package, srctype = 1 SMS_RULE_ENGINE 2/23/2021 10:54:53 PM 5528 (0x1598)
    Failed to download the update content with ID 18060040 from internet. Error = 80 SMS_RULE_ENGINE 2/23/2021 10:55:00 PM 5528 (0x1598)
    Failed to download ContentID 18060040 for UpdateID 18078372. Error code = 80 SMS_RULE_ENGINE 2/23/2021 10:55:00 PM 5528 (0x1598)
    Downloading content with ID 18060041 in the package, srctype = 1 SMS_RULE_ENGINE 2/23/2021 10:55:00 PM 5528 (0x1598)

    I get error code = 80 Any idea what that code is for?

    Reply
    • Andrej Prijmak says:
      February 25, 2021 at 5:42 am

      Hi. Did you try to clear out c:\windows\temp? Do you install all available hotfixes and updates for ConfigMgr? Do your disks have free space?

      Reply
      • John C Storbeck says:
        April 3, 2021 at 1:29 pm

        Sorry for the delay, yes it seems clearing out the c:\windows\temp fixes the issue. Having to do this every couple of week now for some reason. Looks like Defender is leaving the 0kb .TMP files behind now.

        Reply
        • Andrej Prijmak says:
          April 4, 2021 at 7:11 am

          Hi. You can create simple PowerShell to clear files older than X days in the temp folder and schedule it to run once a week (as an example)

          Reply

Lasă un răspuns Anulează răspunsul

Adresa ta de e-mail nu va fi publicată. Câmpurile obligatorii sunt marcate *

Acest site folosește Akismet pentru a reduce spamul. Aflați cum sunt procesate datele comentariilor dvs.

Traducere

English中文(简体)DanskNederlandsFrançaisDeutschItaliano한국어PolskiPortuguêsRomânăEspañolУкраїнська
de Transposh - translation plugin for wordpress

Postări populare

Cerințe de sistem pentru Windows Server 2016
Windows Server
Lista de colecție de interogări din Configuration Manager
Lista de colecție de interogări din Configuration Manager
Configmgr
Navigarea structurată/gestionată este activată în paginile moderne din site-urile clasice ale echipelor
Teh
SCCM nu s-a obținut locațiile DP ca versiune așteptată de la MP
Configmgr

Postări recente

Instalarea și configurarea Fail2ban pentru protecție SSH pe Ubuntu 24.04
Linux
Activarea și configurarea FirewallD pe AlmaLinux
Linux
Crearea utilizatorilor și configurarea cheii SSH în AlmaLinux
Linux
Cum să resetați parola pe AlmaLinux
Linux

© 2023 Enterine

Accesați versiunea mobilă
Bine ai revenit!

Conectați-vă la contul dvs

Nume de utilizator sau adresă de e-mail
Parolă

Ți-ai pierdut parola?