Share via

SCCM Client install during Autopilot

Zoltán 1 Reputation point
2021-04-01T08:20:27.767+00:00

Hi All,

I am facing an interesting issue, but not sure what or why it happens. The scenario is: I set up Autopilot to Enroll devices. We have 5-6 applications that we push during the deployment. All applications are installing fine, except the SCCM Agent. I packaged the SCCM Client as a Win32 app with the intuneapputil Tool. Command line: ccmsetup.exe CCMHOSTNAME=<internal management point> SMSSiteCode=<sitecode> /nocrlcheck /noservice I have tried already many different command line options to use but with no luck.

I have two different cases:

  1. Installation over Home internet The installation completes. The configuration manager is installed, but not fully functional, only after connecting to VPN, when the client makes connection to the management point. In this scenarion the installation happens from the Intune package!
  2. Installation over copmany network The installation failes with error codes:
      MSI: Module C:\WINDOWS\CCM\StatusAgentProxy.dll failed to register.  HRESULT -2147024770.  Contact your support personnel.
    
        ...
    
        File C:\WINDOWS\ccmsetup\{AF66DA1E-AF83-4031-B45F-1C65DD99C1E0}\client.msi installation failed. Error text: ExitCode: 1603
        Action: SelfRegModules.
        ErrorMessages:
        Module C:\WINDOWS\CCM\StatusAgentProxy.dll failed to register.  HRESULT -2147024770.  Contact your support personnel.
    
        ...
    
      CcmSetup failed with error code 0x80070643
    

Any help is appretiated.

Thx.

Microsoft Security | Intune | Application management
0 comments No comments

10 answers

Sort by: Most helpful
  1. Zoltán 1 Reputation point
    2021-04-12T09:54:15.843+00:00

    Thank you guys for the responses!

    Yes, CMG is configured.
    I am performing Hybrid AzureAD join during the setup.

    I also tried to install applications through the VPN, but that way it seems to be installing with no problems.

    Was this answer helpful?


  2. Jason Sandys 31,421 Reputation points Microsoft Employee Moderator
    2021-04-01T14:12:37.287+00:00

    Using ccmsetup.exe to install the client agent from Intune is not supported. You must use ccmsetup.msi.

    Do you have a CMG configured?

    Do you have Autopilot configured to perform a hybrid Azure AD domain join or an Azure AD domain join?

    Was this answer helpful?

    0 comments No comments

  3. Rahul Jindal 11,631 Reputation points
    2021-04-01T13:14:36.933+00:00

    I think you should first fix the issue involving installation of ConfigMgr agent over internet\VPN before getting it to work as part of Autopilot. What are you using for client authentication on remote devices? Cert or token? Either way, the pre-req for client authentication will need to be put in place first.

    Was this answer helpful?

    0 comments No comments

  4. Zoltán 1 Reputation point
    2021-04-01T09:45:59.293+00:00

    Thanks for your reply @Crystal-MSFT .

    I experienced this issue on a newly installed device (Windows 10 20H2).
    I tried to install the sccm agent during Autopilot setup, and later also by pushing it over the Intune.

    What I noticed, that the installation over the internet worked, but over VPN not.

    Also the error: Failed to connect to policy namespace. 0x8004100e - I see multiple times in the ccmsetup.log

    Was this answer helpful?


  5. Crystal-MSFT 54,306 Reputation points Microsoft External Staff
    2021-04-01T09:30:02.247+00:00

    @Zoltán , From your description, I know the Configuration client install failed on company network. Could you let us know if it affects all the devices on the company network or just a few devices?

    For the error message, based on my research, it can occur if there is an invalid or corrupt copy of C:\Windows\System32\msvcr120.dll on the target system.

    We can manually install the configuration manager client on the affected client to see if it is working, If the result is the same, we can rename the existing copy of msvcr120.dll and then copy over msvcr120.dll from a working client. Once the file has been copied over, reboot the problem client and attempt the installation again.

    Hope it can help.


    If the response is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.