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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

What is the proper detection method and uninstall process for pushing firefox via Microsoft System Center?

  • 3 uphendule
  • 1 inale nkinga
  • 18 views
  • Igcine ukuphendulwa ngu Mike Kaply

mbrahm
mbrahm
more options

I am trying to use Microsoft System Center Configuration Manager to push a firefox install. Typically, you guys are rockstars and Firefox is one of the most simple programs to install - Kudos for writing your code well! Anyways, I am having an issue with my uninstall method and detection method. Basically, it seems like firefox can either install in Program Files (x86), or the standard 64-bit program files folder. This is giving me issues, because I can't tell how it chooses where to install it. So what I did was make this the detection method:

Either "C:\Program Files (x86)\mozilla firefox" exists OR "C:\Program Files\mozilla firefox" exists. Then to uninstall, I do a rmdir /s /q on both folders, to delete them, so that SCCM recognizes that the program is uninstalled. However, Program Files\Mozilla Firefox, after uninstallation, creates a folder called "to be deleted," which I can't delete. Therefore, I get errors trying to delete this folder, SCCM thinks that firefox is still installed because that folder exists, so you can see the problem.

I COULD add a restart and then delete the folder (as the "to be deleted" folder gets deleted on restart), but I am just wondering if there is a better way.

How does the installer chose whether to install 32- or 64-bit? I have been testing only on 64-bit Windows 10, and I have seen it install in both directories.

I am trying to use Microsoft System Center Configuration Manager to push a firefox install. Typically, you guys are rockstars and Firefox is one of the most simple programs to install - Kudos for writing your code well! Anyways, I am having an issue with my uninstall method and detection method. Basically, it seems like firefox can either install in Program Files (x86), or the standard 64-bit program files folder. This is giving me issues, because I can't tell how it chooses where to install it. So what I did was make this the detection method: Either "C:\Program Files (x86)\mozilla firefox" exists OR "C:\Program Files\mozilla firefox" exists. Then to uninstall, I do a rmdir /s /q on both folders, to delete them, so that SCCM recognizes that the program is uninstalled. However, Program Files\Mozilla Firefox, after uninstallation, creates a folder called "to be deleted," which I can't delete. Therefore, I get errors trying to delete this folder, SCCM thinks that firefox is still installed because that folder exists, so you can see the problem. I COULD add a restart and then delete the folder (as the "to be deleted" folder gets deleted on restart), but I am just wondering if there is a better way. How does the installer chose whether to install 32- or 64-bit? I have been testing only on 64-bit Windows 10, and I have seen it install in both directories.

All Replies (3)

Shadow110
Shadow110
more options

Hi, as Volunteer Support do not know much to help you and the Developers do not see this. stackoverflow is good to get answers from as is github.

As for installing if your 64 it will install 64 and will install to both folders. If 32 and on a 64bit system it will try and update it to 64.

If 32bit system will install 32 only

Deleting folders is a good idea as that is part of our support fix is have them uninstall and delete the folders in : C:\Program Files , C:\Program Files(x86) & C:\ProgramData and leave the Profile folder alone. Install with a full version installer, not the Stub installer :

Most times the uninstaller seems to be working well these days and people are reporting nothing in those folders to delete but it varies.

Hope that helped a little bit.

mbrahm
mbrahm Umnikazi wombuzo
more options

Alright, I'll give that a try. I should note that I was using the stub installer, I downloaded the .exe and extracted it as far as I could go, to see if there was an .MSI contained in it. I'll try doing it the way you suggested. Like I said, my only issue right now is that I can't delete one of the folders without a restart, because it keeps files in it that are pending to be delted. Worst-case, I can just throw in a restart, but I wasn't thinking I'd have to do that for firefox. I'll be back to mark the answer as resolved if this works for me.

Thanks a ton for volunteering and taking your personal time to help out with an open-source product.

Mike Kaply
Mike Kaply
  • Moderator
more options

The stub installer is smart enough to figure out the right installer. It usually goes 64.

My recommendation would be that you use the full installer for deployment and you can pick whether you want 64 or 32.