BESRemove and PSEXEC command help

(imported topic written by SteveC91)

I currently use the PSEXEC command tool to run remote commands on systems I do not have remote desktop access to. In certain cases I want to use the PSEXEC command tool to launch BESRemove.exe to clean out the client install on those systems. When I do this using the BESRemove.exe paramaters of /quiet and /all the BESRemove.exe program ends quickly without removing the client. If I try to manually run the BESRemove executable it does clean up the install.

Any ideas on what may be wrong here?

(imported comment written by BenKus)

Are you saying that manually running “BESRemove /quiet /all” works, but it doesn’t work with psexec? (or that manually running the GUI works, but the command line options don’t work).

Ben

(imported comment written by SteveC91)

Ben, my mistake. When we run the BESRemove command manually (with the /quiet parameter) it pops up the regular BESRemove window asking us to click on “Remove Bigfix Enterprise Client” or “Remove All”. That shouldn’t happen when you give the command-line parameters.

(imported comment written by SteveC91)

I am using the latest BESRemove that we pulled down from the Bigfix download site yesterday.

(imported comment written by BenKus)

Hi Steve,

Try “/silent” instead of “/quiet”

See: http://support.bigfix.com/bes/install/downloadutility.html#besremove

Ben

(imported comment written by SteveC91)

Hi Ben. I tried that. Still no luck. Running that command string manually (besremove /silent /client or besremove /silent /all) on the person’s system does nothing.

(imported comment written by SteveC91)

Ben, I think I found my answer. On some of the systems I was trying this on the client was still running the BESClient service. I stopped the service first then found that the “automated” besremove.exe worked fine. So I’m adding a “net stop BESClient” before I run the besremove.