Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

This thread was archived. Please ask a new question if you need help.

ProductCode (ProductID) after Firefox Setup 68.5.0esr.msi is installed - Not the same as .MSI installer

  • 1 reply
  • 1 has this problem
  • 1 view
  • Last reply by Mike Kaply

agcastle2000
agcastle2000
more options

The ProductCode (ProductID) after Firefox Setup 68.5.0esr.msi is installed does not match to the ProductCode (ProductID) of the Firefox Setup 68.5.0esr.msi. We use SCCM to create the application deployment for Firefox ESR x64 and to install all the endpoints. When creating the deployment, SCCM automatically extracts the ProductCode, and uses the same to detect the presence of the application - if it's not present, it installs. The main issue is that when SCCM checks again the presence after it's installed, the deployment fails because the ProductCode after it's installed is different than what came with the MSI installer. I noticed that this is the case as well for Firefox Setup 68.4.0x esr.msi whereas in the past this was not the case.

See the attached file to see the screenshots.

The ProductCode (ProductID) after Firefox Setup 68.5.0esr.msi is installed does not match to the ProductCode (ProductID) of the Firefox Setup 68.5.0esr.msi. We use SCCM to create the application deployment for Firefox ESR x64 and to install all the endpoints. When creating the deployment, SCCM automatically extracts the ProductCode, and uses the same to detect the presence of the application - if it's not present, it installs. The main issue is that when SCCM checks again the presence after it's installed, the deployment fails because the ProductCode after it's installed is different than what came with the MSI installer. I noticed that this is the case as well for Firefox Setup 68.4.0x esr.msi whereas in the past this was not the case. See the attached file to see the screenshots.
Attached screenshots

All Replies (1)

Mike Kaply
Mike Kaply
  • Moderator
more options

Can you check to see if this bug covers your situation?

https://bugzilla.mozilla.org/show_bug.cgi?id=1505436