*Edit - Ok, now they actually work... I forgot to include the folder Logs, so the tools would run but would not display any results. That is fixed now.
I'm starting to make some Powershell right click tools and wanted to see if some people could test them out. I've tested them out in my environment and they seem to work well, but I wanted to make sure they work for others before I invest more time coding others.
If you download, extract and run the right click tools install command file, it will install the tools. You'll have a new menu whenever you right click on a collection called "Powershell Right Click Tools". There are currently 4 tools:
Ping Collection - Uses Start-Job to speed things up. You'll only see a speed increase if a large number of computers are off or if you have high latency in your network. I added in buttons to shutdown, reboot or wake up those computers.
Wake On Lan - Same as the previous one, just recoded into PS to make it look like the others.
Reboot Collection - Restarts all computers in the collection
Shutdown Collection - Turns off all computers in the collection
The last option is Remove PS Tools, which will delete all the files I added and remove that menu when you next restart ConfigMgr.
In my testing it didn't matter what the Execution-Policy setting was on the computer. I open the Powershell scripts through a vbs file that sets the execution-policy to unrestricted, but it doesn't change it for the computer. I have no clue why this is, but ConfigMgr seems to have a different execution policy than the rest of the computer in Powershell.
If these work, I'm going to start coding tools to add more features. The first idea I had was to let you right click on a deployment and give a detailed view of the compliance (so the status of computers running the deployment) and give you some options to quickly fix common problems (change cache size / clear cache, wol, reboot, policy updates, re-run deployment).
Thanks for testing!
<message edited by Ryan2065 on Wednesday, August 15, 2012 1:43 PM>