Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Mulongo oyo etiyamaki na archive. Tuna motuna mosusu soki osengeli na lisalisi

.msi installtion fails to install with SCCM

  • 2 biyano
  • 2 eza na bankokoso oyo
  • 21 views
  • Eyano yasuka ya atomic.delta

atomic.delta
atomic.delta
more options

I noticed that since version FF 70+ version the installation fails in a task sequence with error 0x80004005. What especially interesting is, after i deploy a new computer (new windows, settings etc.) i come to this multiple installation step, and only FF fails. After I cancel the task sequence, I go into windows and Firefox is happily waiting me on the desktop!

I think it is got to do with the detection method because the detection method is set to look for .msi product code and when i run a powershell command "Get-WmiObject Win32_Product | sort name | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize" on a freshly deployed PC I get all of the .msi codes but Firefoxe's. Can somebody from the dev team check this?

Thank you

I noticed that since version FF 70+ version the installation fails in a task sequence with error 0x80004005. What especially interesting is, after i deploy a new computer (new windows, settings etc.) i come to this multiple installation step, and only FF fails. After I cancel the task sequence, I go into windows and Firefox is happily waiting me on the desktop! I think it is got to do with the detection method because the detection method is set to look for .msi product code and when i run a powershell command "Get-WmiObject Win32_Product | sort name | Format-Table IdentifyingNumber, Name, LocalPackage -AutoSize" on a freshly deployed PC I get all of the .msi codes but Firefoxe's. Can somebody from the dev team check this? Thank you

All Replies (2)

neil mohler
neil mohler
more options

Haced

atomic.delta
atomic.delta Nkolo motuna
more options

Great answer man! Really implemented this "Haced" solution and it worked.

On more serious note, the sccm installation was halted because the detection method that comes with the .msi package is not correct. The detection method is set according to the .msi product code, and when I searched for the product code with powershell - it was not listed. I switched the detection method to .exe file and its file version - then it worked.

Cheers,