PENDING Configuration Manager client.msi installation failed. Error ExitCode: 1603

[Hyp]

Hi Prajwal,
I have a problem to install SCCM agent on a windows 2019 server that had scmm agent in the past
I already tried to fix the problem with cleaning WMI, or to make the steps from :

D

SOLVED Thread 'SCCM client install failed with exit code 1603'

Apr 24, 2017

Hi Prajwal,

First, Many Congrats for your awesome Website. It has helped me to implement the whole SCCM Environment with a PKI. And i got so many Information about SCCM and i could solved many Issues.

But one Issue makes me crazy. I cannot solve it. I have already investigated several Weeks of analysing the Issue. But with no Success. So i hope you can help me with this. You are my last Hope.

As you can read in the Thread Title, the SCCM Client can't be installed at a Client Machine with the Error 1603. I have found many solutions in the Net. I have tried to repair the WMI...

• Daniel Broz
• client install issues sccm
• Replies: 10
• Forum: SCCM

Unfortunatelly the problem is still there
I have also run with psexec directly the command or opening a new powershell and the problem is still there

 

[Prajwal Desai]

How are you installing the agent on this server? Use the client push method and try.

 

[Hyp]

Hello Prajwal,
We are using a configuration file tcf and we run the installation with with ps as admin with command: .\ccmsetup.exe /config:file.tcf
Works on all servers (hundreds) but on this one i receive this error

 

[Prajwal Desai]

That configuration file is not accepted on the server. From the screenshot, I see the exit code 1603 and the client not supporting the per-user installations. What's in that tcf file?

 

[Hyp]

yes, i see that, but how can i force it to installas system?

 

[Prajwal Desai]

You mentioned that the deployment works on most of the servers except one server. I think that the client installation on this troublesome server is being blocked by something, possibly a firewall, antivirus software, etc. What client installation properties have been specified in that config file?. If it's just one server, I would do a client push install and apply those configurations later manually.

 

[Hyp]

thank you very much, same error is even i select that file or not
no antivirus , no firewall on that machine

 

[Prajwal Desai]

So even with client push install or manually client install, the server ends up showing the same error?

 

[Hyp]

push doesn't work at all, no changes when i push in the ccmsetup.log even after 1 hour
the manual install without config file gives me the same error

 

[Prajwal Desai]

If you aren't seeing any changes in ccmsetup.log on the problematic server, it means the client installation is failing somewhere. What do you see in ccm.log on the ConfigMgr server when you do a client push?

 

[Garth]

Hi Prajwal,
I have a problem to install SCCM agent on a windows 2019 server that had scmm agent in the past
I already tried to fix the problem with cleaning WMI, or to make the steps from :

D

SOLVED Thread 'SCCM client install failed with exit code 1603'

Apr 24, 2017

Hi Prajwal,

First, Many Congrats for your awesome Website. It has helped me to implement the whole SCCM Environment with a PKI. And i got so many Information about SCCM and i could solved many Issues.

But one Issue makes me crazy. I cannot solve it. I have already investigated several Weeks of analysing the Issue. But with no Success. So i hope you can help me with this. You are my last Hope.

As you can read in the Thread Title, the SCCM Client can't be installed at a Client Machine with the Error 1603. I have found many solutions in the Net. I have tried to repair the WMI...

• Daniel Broz
• client install issues sccm
• Replies: 10
• Forum: SCCM

Unfortunatelly the problem is still there
I have also run with psexec directly the command or opening a new powershell and the problem is still there

Have you review the MSI log to see exactly what the problem is?

 

[Hyp]

Have you review the MSI log to see exactly what the problem is?

 

[Garth]

That is not the MSI log, that is the setup log, look for the log file with MSI in the name.

 

[Hyp]

yes i am seeing now that i attached the wrong file