Avatar for Username

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊，或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

此討論串已被封存。 如果您有需要幫助，請新增一個新問題

.msi installtion fails to install with SCCM

  • 2 回覆
  • 2 有這個問題
  • 21 次檢視
  • 最近回覆由 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

所有回覆 (2)

neil mohler
neil mohler
more options

Haced

atomic.delta
atomic.delta 提出問題者
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,