(imported topic written by scott.craddolph91)
Hello,
Has anyone set up an action to remove multiple versions of Quicktime? I am especially interested in how the relevance clauses would be set up for such a task.
Thanks,
Scott Craddolph
(imported comment written by scott.craddolph91)
I got the relevance completed and it works to identify Quicktime versions but my run statement keeps bombing on my test system when the action runs - I have tried every variation possibe:
On a given workstation the uninstall string is this originally:
C:\WINDOWS\system32\msiexec.exe /uninstall {1838C5A2-AB32-4145-85C1-BB9B8DFA24CD} /qf
I want it to run unattended so I normally would replace the /qf with /quiet or /passive.
Now I’ve tried the following variations and it fails every time
run C:\WINDOWS\system32\msiexec.exe /uninstall {1838C5A2-AB32-4145-85C1-BB9B8DFA24CD} /quiet
run “C:\WINDOWS\system32\msiexec.exe /uninstall {1838C5A2-AB32-4145-85C1-BB9B8DFA24CD} /quiet”
run “C:\WINDOWS\system32\msiexec.exe /uninstall {1838C5A2-AB32-4145-85C1-BB9B8DFA24CD}” /quiet
wait “C:\WINDOWS\system32\msiexec.exe /uninstall {1838C5A2-AB32-4145-85C1-BB9B8DFA24CD}” /passive
All fail on the test box.
I’m open to suggestions at this point.
Scott Craddolph
(imported comment written by scott.craddolph91)
Forgot to add the following additional example:
run “C:\WINDOWS\system32\msiexec.exe {1838C5A2-AB32-4145-85C1-BB9B8DFA24CD}” /uninstall /quiet
Scott C.
(imported comment written by jessewk)
Hi Scott,
Braces are reserved characters in action script. You’ll need to escape the any left braces for your expression to work. Try:
wait C:\WINDOWS\system32\msiexec.exe /uninstall {{1838C5A2-AB32-4145-85C1-BB9B8DFA24CD} /qf
Notice the double {{. Braces are reserved to allow relevance substitution in action script. Anything between braces is evaluated just before the line is executed. For example, I would rewrite your expression like this to make it work on all Windows OSes:
{quote}wait {pathname of system folder}\msiexec.exe /uninstall {{1838C5A2-AB32-4145-85C1-BB9B8DFA24CD} /qf{quote}
Jesse
(imported comment written by SystemAdmin)
Hi Scott, maybe if you add UIMODE=“NO” to your script it could be work
fherrera.
(imported comment written by Mr.NiceGuy)
Was this ever resolved? If so what was the fix that solved the issue? I wrote a fixlet/task to remove Quicktime as well. It runs successfully, many systems state that QuickTime is indeed removed. However, when I go to check on those systems QuickTime is still installed (ie: the Program Files (x86) folder still exists). I wrote at least 2 other tasks to help in the cleanup of the uninstallation. The first removes the files in a sub folder (including the sub folder) and the 2nd removes the parent folder. However, when either of the tasks is run (in proper order) the systems are checked and still contain the folders. Every time these have been run BigFix indicates the tasks completed successfully. To me a successful run would be that the folders are removed/deleted. Does an extra check have to be added to the task in order for BigFix to mark it “failed” if the folder still exists?
Here is what I’m using (note: I replaced the key with QuickTime Reg Key, the actual script contains the real key):
Action:
wait MsiExec.exe /X {{QuickTime Reg key} /qn /norestart
Relevance:
exists folder “C:\Program Files (x86)\QuickTime”
Any suggestions? I also realize this thread is years old, if I need a new one I’m more than happy to create one.
(imported comment written by Mr.NiceGuy)
Was this ever resolved? If so what was the fix that solved the issue? I wrote a fixlet/task to remove Quicktime as well. It runs successfully, many systems state that QuickTime is indeed removed. However, when I go to check on those systems QuickTime is still installed (ie: the Program Files (x86) folder still exists). I wrote at least 2 other tasks to help in the cleanup of the uninstallation. The first removes the files in a sub folder (including the sub folder) and the 2nd removes the parent folder. However, when either of the tasks is run (in proper order) the systems are checked and still contain the folders. Every time these have been run BigFix indicates the tasks completed successfully. To me a successful run would be that the folders are removed/deleted. Does an extra check have to be added to the task in order for BigFix to mark it “failed” if the folder still exists?
Here is what I’m using (note: I replaced the key with QuickTime Reg Key, the actual script contains the real key):
Action:
wait MsiExec.exe /X {{QuickTime Reg key} /qn /norestart
Relevance:
exists folder “C:\Program Files (x86)\QuickTime”
Any suggestions? I also realize this thread is years old, if I need a new one I’m more than happy to create one.
(imported comment written by jgstew)
For BigFix to report “FAILED” when it does not succeed, you need to set the
success criteria
to be “
This action will be considered successful when the applicability relevance evaluates to false.
”