SCCM Client Actions Tool v0.8

Rating:        Based on 1 rating
Reviewed:  0 reviews
Downloads: 2152
Change Set: 11626
Released: Nov 15, 2011
Updated: Jan 12, 2012 by pr3m
Dev status: Stable Help Icon

Recommended Download

Application ClientActionsTool_v0.8.zip
application, 86K, uploaded Nov 15, 2011 - 2152 downloads

Release Notes

SCCM Client Actions Tool v0.8 is currently the latest version.
It comes with following changes since last version:
  • Added "Wake On LAN" action.
  • WOL.EXE is now included.
  • Added new action "Get all active advertisements" to list all machine based advertisements on remote computers.
  • Added new action "Get all active user advertisements" to list all user based advertisements for logged on users on remote computers.
  • Added config.ini setting "enablePingTest" to control whether ping test is run before each action or not.
  • Added GUI interface for configuring client installation properties.
  • CCMSETUP parameter string in config.ini can be used and modified directly in GUI.
  • Modified "Get Logged-On User" action so that if no user is logged on remote computer, the last logged on user is shown.
  • Improved "Query advertisement status" action to support keyword based filtering to get status of all matching advertisements.
  • Added small "Close" button in top right corner of DIV dialogs.
  • Fixed issues with querying user based advertisements.
  • Current username is now determined and shown from wscript.network to support running the tool in a RDC session.
  • Delete log file if it is empty on exit.
  • Bug fixes.

The tool is downloadable as a ZIP file that contains three files:
ClientActionsTool.hta – The tool itself.
Cmdkey.exe – command line tool for managing cached credentials. This is needed for alternate credentials feature when running the HTA on Windows XP. Cmdkey.exe is natively available starting from Windows Vista.
Wol.exe - command line tool from Gammadyne Corporation to send wake up packets to remote computers.
Config.ini – A configuration file for default settings. This file is not required to run the tool, but if it doesn’t exist, the tool may prompt for the data every time it’s run.

Only the HTA file is necessary to use this tool. After all, the concept of the tool is simplicity – “one click to rule them all” sort of thing. However, having cmdkey.exe in same folder is a requirement for using alternate credentials when running the HTA on Windows XP. The config.ini file improves usability by keeping default settings for every run.

Make sure you know what one or another action does before initiating it on workstations in production environment! Some of the actions have been explained in documentation.

Donate to SCCM Client Actions Tool project using PayPal

Reviews for this release