Well, maybe not FTW; there are a couple things that it does fairly poorly. But it will let you (if you connect as an account that's a local admin on the remote box, e.g. a domain admin account) execute any program with an arbitrary command line. I'm fairly sure the program will start on the service's desktop, also, so it won't matter if it's quiet or not. (Although if it isn't quiet, you won't be able to interact with it.)
I use it fairly frequently to have a machine re-run its WSUS scan (by running "wuauclt /detectnow" via WMI). Works fairly well, although the WMI method call that you have to make is different on 2K versus XP, so you have to use the method-call interface that takes a separate parameter that's a collection of the method's parameters (if that makes any sense). Because you can't specify the method's parameters directly; there are two different versions of it that take different parameters in different positions.
E.g. instead of doing a 'callMethod("runprogram", "exe", "command line")', you have to build a separate collection of "exe" and "command line", then do a 'callMethod2("runprogram", thatcollection)' instead. But at least it works. |
