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,