Hello,
Just wanted to start off by stating that I know there is another discussion about this called "Silent or unattended install options?" but I am unable to reply to that thread as I keep encountering an error when I try.
From this thread though, I found you can do a silent install with /S switch.
I also found from Simeon's post that you can install to a specific directory with /D=C:\Program Files\Fiddler.
My issue is that when using these switches together, I am not getting the correct result. I am deploying Fiddler (v5.0.20181.14850) via an APPLICATION. I also tried to deploy as a package but was also having issues.
FiddlerSetup.exe /S /D=C:\Program Files\Fiddler - looks like the silent install is working but then the install will fail with error 0x87D00324(-2016410844). There is a Fiddler folder within program files but the .exe was not installed.
FiddlerSetup.exe /D=C:\Program Files\Fiddler /S -Incur pop up window to walk through the instillation. The default directory on the install is correct, but it is not silent.
When trying to install via package, I am trying the following :
FiddlerSetup.exe /S /D=C:\Program Files\Fiddler
Issue is that it looks like it installs successfully, I can find it within C:\Program Files\Fiddler but the doesn't actually install Fiddler, seems like it just places the install within that directory.
10 Answers, 1 is accepted
Sorry for the late reply. According to this post, the 0x87D00324 error code of the SCCM means that the detection method did not succeed.
Based on the screenshot, it seems that the detection rule needs to be changed. In the 'Specify the file or folder to detect this application.' section, the 'File or folder name:' field needs to be 'Fiddler.exe' or maybe '%PROGRAMFILES%\Fiddler\Fiddler.exe'.
Regards,
Simeon
Progress Telerik
Rank 1
Hello Simeon,
So I have received this error on other installations and knew it wasn't the actual detection method that was the issue. It was more of an issue with how the install was completing. I know there wouldn't be a problem if I just used one of the switches alone, but that isn't the end goal I was wanting.
I have also tested this locally without issue besides what I described above. I am just not sure how to use the silent switch along with the directory switch to specify which directory to install within.
For the detection method I am using file systems, path is '%programfiles%\Fiddler' and File is 'FiddlerSetup.exe' so I don't see any reason this would be incorrect.
Current instillation program: FiddlerSetup.exe /S /D=C:\Program Files\Fiddler
Install starts in: \\SHARED DRIVE\Source\Applications\Software\Telerik Fiddler
Would you possibly have any other suggestions or suggest looking at any specific logs?
I am just not sure how to use the silent switch along with the directory switch to specify which directory to install within.
I confirm that FiddlerSetup.exe /S /D=C:\Program Files\Fiddler is the correct command to run the installer silently and to set the install directory. Fiddler is using the NSIS installer and the /S and /D options are common for NSIS installers. FYR, here is a link from the NSIS documentation.
As for the detection method, I admit that SCCM is out of my scope and unfortunately, I can not help much. It just seems to me that the detection method is trying to find the installer FiddlerSetup.exe into the install directory after the install and it should look for the Fiddler.exe program instead. Correct me if i am wrong.
Would you possibly have any other suggestions or suggest looking at any specific logs?
Unfortunately, I am not aware for any logs which the Fiddler installer makes.
Regards,
Simeon
Progress Telerik
Rank 1
Hello Simeon,
So I modified the detection method to just Fiddler.exe and yes you are correct, this would be correct over FiddlerSetup.exe. My mistake here and thank you for pointing that out.
So this result is similar to how the package would install (from my original post on this thread), the silent install is working and it installs to the correct directory but it doesn't look like it actually installs Fiddler. There is no 'Fiddler' or 'Progress Telerik Fiddler' within add/remove programs or when searching within the start menu. When looking within program files though, the Fiddler folder is there with all the needed source files but again, it looks like it didn't actually install anything.
I assume that the SCCM runs the FiddlerSetup.exe with a different Windows user account from the one you intend to use Fiddler.exe with. The current installation of Fiddler is for a single user. This means that it creates shortcuts into C:\Users\The_User_Who_Runs_The_Installer\AppData\Roaming\Microsoft\Windows\Start Menu\Programs. However, these shortcuts are visible only for this user in its Start menu.
The same assumption is valid for the fact that Fiddler does not appear within Add/Remove programs of other users. The installer creates the Uninstall registry key of Fiddler into HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall\Fiddler2. If you open Add/Remove programs with the same user which ran the Fiddler installer you should now see Progress Telerik Fiddler in the list.
The main reason to make Fiddler per user and not for all users is that installing something for all users requires administrator privileges and many users who wish to use Fiddler does not have them. This is how it became possible these people to use Fiddler as well.
So to solve the problem, make sure that the Fiddler installer is run with the Windows user account you intend to use Fiddler with.
Regards,
Simeon
Progress Telerik
Rank 1
Hello Simeon,
"I assume that the SCCM runs the FiddlerSetup.exe with a different Windows user account from the one you intend to use Fiddler.exe with."
- This would be the system user.
"The main reason to make Fiddler per user and not for all users is that installing something for all users requires administrator privileges and many users who wish to use Fiddler does not have them."
- That is why we are deploying the applications via SCCM. We do not want to allow users to have admin privileges to install their own software but at the same time, wanted the install to work if anyone else signed into the same computer. This is an unlikely scenario but haven't had issues installing other applications at system level with SCCM.
I suppose for now I will just not include the directory for install as I cannot get around this. I appreciate the responses and effort you put into replying!
Thanks Simeon!
Rank 1
Forgot to add in the previous post:
"So to solve the problem, make sure that the Fiddler installer is run with the Windows user account you intend to use Fiddler with."
-Not really sure how to go about this when you have potentially 50+ people that the software would need to deploy to. The install should be within the same Program Files location for all users.
Rank 1
Forgot to include this within the previous response:
"So to solve the problem, make sure that the Fiddler installer is run with the Windows user account you intend to use Fiddler with."
-Not sure how to accomplish this when deploying the application to 50+ users via SCCM. They should all be within the same Program Files directory.
I will mark this thread as answered but technically it was not as I had to remove the "/D=C:\Program Files\Fiddler" from the instillation command line.
Thanks
If you need to install Fiddler for all users, please add it at https://fiddler.ideas.aha.io/ideas so that we could prioritize it.
Regards,
Simeon
Progress Telerik
Rank 1