Share via

SCCM Client failed to install on some devices for many times

QdPooler-5995 561 Reputation points
2023-08-26T08:37:27.37+00:00

Hi experts,

I'm facing a strange issue. About 30 devices have failed install SCCM client, other devices don't have this issue. I have try many method, client push installation, manually installation, group policy installation, but none of them worked. In ccmsetup.log, I can see below error:

File C:\windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi installation failed. Error text: ExitCode: 1603

Failed to connect to policy namespace. Error 0x8004100e

This question has racked my brains. Any help would be highly appreciated!

Microsoft Security | Intune | Configuration Manager | Other
Accepted answer
  1. Simon Ren-MSFT 40,346 Reputation points Microsoft External Staff
    2023-08-28T02:00:57.5333333+00:00

    Hi,

    Thanks for your reply.

    This can occur if a previously failed installation of the Configuration Manager client left behind an IPI installer file (.ipi) in the %systemroot%\installer directory on the target computer.

    Search for *.ipi files in the %systemroot%\installer directory on the target computer and temporarily move them to a different folder. Next run the setup of the client installation again and it should complete successfully.

    Please refer to: MSI: Configuration Manager Client is not installed

    Thanks for your time. Have a nice day!

    Best regards,

    Simon

    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.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Sherry Kissinger 5,526 Reputation points
    2023-08-26T19:56:54.3333333+00:00

    It says right there... "MicrosoftPolicyPlatformSetup.msi". That is one of the dependencies. On one of those boxes, I would try logging in (or remotely, if you have winrm enabled and can remote powershell to it),

    as an admin, run msiexec /i MicrosoftPolicyPlatformSetup.msi /l*v c:\windows\temp\MPP.log /qn

    Where you run that from the folder where MicrosoftPolicyPlatformSetup.msi exists.

    Then watch the c:\windows\temp\mpp.log, and see WHY exactly that specific component is failing.

    1 person found this answer helpful.
    0 comments

Your answer

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