Closed
Bug 874082
Opened 12 years ago
Closed 12 years ago
Provide a way for the uninstaller to silently remove the profile directory
Categories
(Firefox :: Installer, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: mkaply, Unassigned)
Details
This might already be possible, but I can't find any information on it.
Currently the silent uninstall option (-ms) leaves behind the profile directory
It would be nice if there was someway to specify that you wanted the user profile directory removed.
![]() |
||
Comment 1•12 years ago
|
||
The option to remove the profile directory for the user running the uninstall will likely be removed due to users that use this shooting themselves in the foot. I won't add another foot gun here so wontfix.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
(In reply to Robert Strong [:rstrong] (do not email) from comment #1)
> The option to remove the profile directory for the user running the
> uninstall will likely be removed due to users that use this shooting
> themselves in the foot. I won't add another foot gun here so wontfix.
The request is not for average home users. This is for an enterprise (school district) deployment that I don't want the profile to remain or anything to remain if I decide to pull firefox. Is it possible to have a silent hidden full uninstall switch that most users will never need or use?
We are talking about 15000 people with over 5000 client machines.
The resolution of "wontfix" is so apple like when it comes to enterprise flexibility.
![]() |
||
Comment 3•12 years ago
|
||
When working on enterprise deployments in the manner you described you have to perform the custom uninstall and at the same time whatever you are doing to automate the launch can easily perform the rmdir of the profile directory as well as any other custom actions. Hopefully you aren't just manually running the uninstaller silently!
Not to mention, the uninstaller will only know about the profiles for the user account that is running the uninstaller.
We use KACE to deploy software which I then use a batch file to execute the install. KACE uses the "system account".
I made this:
@ECHO OFF
taskkill /IM firefox.exe
:MENU
if exist "%programfiles%\mozilla firefox\uninstall\helper.exe" (
"%programfiles%\mozilla firefox\uninstall\helper.exe" /S
GOTO setup
) else (
GOTO x64
)
:x64
if exist "Programfiles(x86)%\mozilla firefox\uninstall\helper.exe" (
"%programfiles(x86)%\mozilla firefox\uninstall\helper.exe" /S
GOTO setup
) else (
GOTO setup
)
:setup
"%~dp0setup.exe" -ms /ini="%~dp0core\nodesktop.ini" /slient
![]() |
||
Comment 5•12 years ago
|
||
Adding the current capability to silent mode of the uninstaller wouldn't help when running as any other account than the account that you want to remove the profile for.
There are a bunch of enterprise features that I very much agree would be nice but I am adamantly against adding them to the installer / uninstaller used by the vast majority of users. MS gets this right by providing utilities for enterprises but we aren't going to bolt these things to the side of the installer / uninstaller.
Think of it this way.
I work for a school district. Each software or product we use can have a profound effect on that companies product via exposure.
Kids use product A in school --> Kids tell parents about product A --> parents try product A --> parents tell other adults.
Kids grow up to be an adults and are familiar with product A and continue this by exposing product A to their kids.
Thank you for your time :)
![]() |
||
Comment 7•12 years ago
|
||
(In reply to Paul from comment #6)
> Think of it this way.
>
> I work for a school district. Each software or product we use can have a
> profound effect on that companies product via exposure.
>
> Kids use product A in school --> Kids tell parents about product A -->
> parents try product A --> parents tell other adults.
>
> Kids grow up to be an adults and are familiar with product A and continue
> this by exposing product A to their kids.
>
> Thank you for your time :)
This is already understood. The problem is this bug is asking for the uninstaller to be able to do what uninstallers don't do in that you want it to be able to touch multiple user profiles from a single account. I also understand that you want this functionality and with this in mind see adding it to the uninstaller as the simplest way to get what you want while I see this as a request to add significant one-off use case specific code when it would be much more appropriate to provide enterprise utilities for your use case.
You need to log in
before you can comment on or make changes to this bug.
Description
•