Originally Posted by Old Pedant
I simply don't have a system where I can try that stuff any more.
I'm doing contract work from home and while I have VPN to a system where this could be done I don't have high enough privileges there to do it.
I do think it *could* be done via VBS, but what FouLu says re threading makes sense.
Definitely doable in vbs; I have apps that were written for cluster management in (of all things) vbs and WMI. The "threading" concept is actually a relay of a spawned sub process that detects its completion state before attempting to poll for current information. Ingenious, I have to admit, but far cry from the threading model. Unfortunately, the way its built (and due to the limitation of vbs), if I execute my own WMI management at the same time it will result in the script crashing since it'll never detect that the WMI has completed. Oh well.
If I were you alykins, I'd write it as an actual manager. Given a list of machines, you can do something like select a drop down for the service then have it populate in a table below the current status and start up type for the service. Choose the service (add some select/desselect all type options), and submit those for the WMI to update. Neat.
This way you could also handle if you get something new as well and want to add it to the management. Just use some files to construct the dynamic data you need.
Now I get to make an awesome mspaint picture
Lol that's awesome.