Microsoft Firewall Client (2000)
Greetings,
First post! Hope I don't make an arse of myself out of the gate [;)]
Can anyone share some knowledge about scripting an unattended installation of the Microsoft Firewall Client (2000)?
Google seems to turn up no useful documentation...but I freely admit that my lack of success could be an external keyboard driver problem [8|]
This file exists on the client...
"C:\Program Files\Microsoft Firewall Client\setupbin\UNINST.EXE"
...but despite my best attempts at determining a silent uninstall switch, it continues to prompt for confirmation.
Any assistance will be very much appreciated.
Thanks,
Tim ==
First post! Hope I don't make an arse of myself out of the gate [;)]
Can anyone share some knowledge about scripting an unattended installation of the Microsoft Firewall Client (2000)?
Google seems to turn up no useful documentation...but I freely admit that my lack of success could be an external keyboard driver problem [8|]
This file exists on the client...
"C:\Program Files\Microsoft Firewall Client\setupbin\UNINST.EXE"
...but despite my best attempts at determining a silent uninstall switch, it continues to prompt for confirmation.
Any assistance will be very much appreciated.
Thanks,
Tim ==
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
TomB
18 years ago
UNINST.EXE is an older Installshield file. Chances are this applicaiton could have been installed with Installshield or you are calling a different UNINST.EXE.
Look at the following link for command lines: Here
UNINST.EXE -y -a might work.
You can also try to use AutoIT. http://www.autoitscript.com/AutoIt/downloads.php
Look at the following link for command lines: Here
UNINST.EXE -y -a might work.
You can also try to use AutoIT. http://www.autoitscript.com/AutoIt/downloads.php
Posted by:
xpanmanx
18 years ago
Thanks, Tom!
After some more investigative work, I came up with this method:
My lack of knowledge about package IDs makes me a little nervous. Under what circumstances might the package ID change?
After some more investigative work, I came up with this method:
MsiExec.exe /X {8C7A59A8-9ABE-459A-9A93-08C281A4A264} /qnMy lack of knowledge about package IDs makes me a little nervous. Under what circumstances might the package ID change?
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.