Close Menu
    Facebook X (Twitter) Instagram
    Prajwal.orgPrajwal.org
    • Home
    • SCCM

      CVE-2025-47178 for Configuration Manager

      July 12, 2025

      SCCM 2503 Upgrade New Features and Hotfixes

      April 30, 2025

      Create a Device Collection for SCCM 2409 Clients

      February 27, 2025

      Device Collection for SCCM 2403 Clients

      January 22, 2025

      SCCM 2403 Hotfixes, Upgrade and New Features

      January 21, 2025
    • Intune

      New Features in Intune 2502 release (February 2025)

      February 27, 2025

      Intune Service Release 2406 New Features (June 2024)

      June 23, 2024

      Microsoft Intune 2405 New Features (May 2024)

      May 29, 2024

      How to Disable Android Enterprise system app in Intune

      May 22, 2024

      Intune ends support for Android device administrator

      January 22, 2025
    • Windows 11

      How to Install WSUS Console on Windows 11

      January 22, 2025

      How to enable memory integrity using Group Policy

      January 22, 2025

      Uninstall Mail and Calendar Apps using PowerShell

      January 22, 2025

      How to Create Batch File to Delete Temp Files

      January 22, 2025

      How to Change RDP Port using PowerShell

      January 22, 2025
    • Contact
    Prajwal.orgPrajwal.org
    Home » Target machine is a DC Not processing this CCR
    SCCM

    Target machine is a DC Not processing this CCR

    January 22, 202553 Views

    This post helps you fix the issue “Target machine is a DC Not processing this CCR”. This line is seen in ccm.log file when you perform either a client push or install SCCM client on domain controller.

    One of the most important task after you install Configuration Manager is install client agents in your hierarchy. There are several ways to install client agents on domain computers. The most easiest one being the client push method.

    Client Push installation happens when an the SCCM server makes a network connection to the client and then begins the client installation process.

    However sometimes we perform the client push without looking at all the options. This will lead to client installation failure and the log files are the only way to identify or troubleshoot the client install failures.

    Target machine is a DC Not processing this CCR

    Let’s say you perform a client push to all your domain controllers, you notice “Target machine is a DC Not processing this CCR” in ccm.log file. The ccm.log file that I am referring here is located on the site server.

    Your ccm.log file could contain similar lines as shown below.

    Target machine is a DC Not processing this CCR
    Target machine is a DC Not processing this CCR
    Trying the 'best-shot' account which worked for previous CCRs (index = 0x0) SMS_CLIENT_CONFIG_MANAGER
    Attempting to connect to administrative share '\\CORPAD.PRAJWAL.ORG\admin$' using account 'PRAJWAL\sccmadmin'
    Attempting to make IPC connection to share <\\CORPAD.PRAJWAL.ORG\IPC$> with Kerberos authentication 
    Unable to connect to WMI (root\ccm) on remote machine "CORPAD.PRAJWAL.ORG", error = 0x8004100e.
    Target machine CORPAD.PRAJWAL.ORG is a DC. Not processing this CCR
    Deleting SMS Client Install Lock File '\\CORPAD.PRAJWAL.ORG\admin$\SMSClientInstall.IND'
    Execute query exec [sp_CP_SetLastErrorCode] 2097152001, 120

    By default, client push explicitly excludes installing the client agent on domain controllers. Therefore for both manual and automatic push, you must select the appropriate option to allow pushing the client agent to DCs.

    While performing a client push on a domain controller, carefully look at client push options. Ensure you select “Allow the client software to be installed on domain controllers“. With this option checked, you can push the SCCM client agents on to domain controllers.

    Target machine is a DC Not processing this CCRIf you don’t wish to do this every time and want to configure this setting at site level, here is the solution.

    • In the SCCM Console, navigate to Administration > Overview > Site Configuration > Sites.
    • Select the site and on top ribbon click Client Push Installation Settings > Client Push Installation.
    • On the General tab, enable “Always install the Configuration Manager client on domain controllers“.
    Always install the Configuration Manager client on domain controllers
    Always install the Configuration Manager client on domain controllers
    Share. Facebook Twitter Pinterest LinkedIn Email
    Previous ArticleFind SQL Server Reporting Services Product Key
    Next Article How to Install RSAT Tools on Windows Server 2019

    Related Posts

    SCCM

    CVE-2025-47178 for Configuration Manager

    July 12, 2025
    SCCM

    SCCM 2503 Upgrade New Features and Hotfixes

    April 30, 2025
    SCCM

    Create a Device Collection for SCCM 2409 Clients

    February 27, 2025
    Latest Guides

    CVE-2025-47178 for Configuration Manager

    SCCM 2503 Upgrade New Features and Hotfixes

    New Features in Intune 2502 release (February 2025)

    Create a Device Collection for SCCM 2409 Clients

    Popular Guides

    Uninstall Snipping Tool using PowerShell

    Updated:January 22, 2025

    How to Manually Install SCCM Client Agent

    Updated:January 22, 2025

    How to Create Batch File to Delete Temp Files

    Updated:January 22, 2025

    Disable Driver Signature Enforcement using CMD Prompt

    Updated:January 22, 2025
    Trending Posts

    Create a Device Collection for SCCM 2409 Clients

    How To Disable Internet Explorer using DISM

    Updated:May 13, 2024

    Microsoft 365 Apps Business vs Enterprise

    Updated:February 14, 2024

    SCCM 2103 New Features and Improvements

    Updated:January 21, 2025
    © 2025 Prajwal.org | Privacy Policy

    Type above and press Enter to search. Press Esc to cancel.