I'm Rob Marshall, a consultant who specialises in the Microsoft System Center Configuration Manager product. I like to share, i do so by blogging and helping out when I can in the MS SMS newsgroups and participating in the ConfigMgr MVP program.
I was awarded and joined the program in 2009. It'd be an understatement to say it has to be one of the best experiences an IT engineer can have, if they really enjoy specialising in a product.
My biggest weapon for troubleshooting is, my formidable knowledge, no, only joking, you, the community. I find if I cannot answer a question, then I can usually find the answer from using Bing\Google, pouring over the documentation, and if that doesn't work, tinkering in mine or someone elses virtual lab.
The blogs pretty much about ConfigMgr, but it is also a platform for me to express my random urges to display something I've stumbled across, and that I imagine would entertain you or what not as equally as it did me.
Handy to know:
Start an application wmic process call create "calc.exe" Terminate an application wmic process where name="calc.exe" call terminate
Start an application
wmic process call create "calc.exe"
Terminate an application
wmic process where name="calc.exe" call terminate
You can also do this remotely
WMIC /NODE:Machine Name /User:UserName /Password:Password process call create "calc.exe"
Drop /Password off the command line to be prompted.
You'll get the following appear if it's successful:
Executing (Win32_Process)->Create()
Method execution successful.
Out Parameters:
instance of __PARAMETERS
{
ProcessId = 22080;
ReturnValue = 0;
};
Something I noticed is that it creates the process but it's not interactive. The process is running on the target but not in the current users session. So even though CALC is now running on the remote machine, you cannot interact with it. This is ok for stuff that runs silent, but how do you get processes to run and become visible to the logged on user when using WMIC Process Call Create?