Adding WMIC right-click actions to the ConfigMgr 2007 admin console (1)

September 15, 2009 at 8:51 am in AdminUi, ConfigMgr, ConfigMgr 2007, configmgr2007, sccm, SCCM 2007, sccm2007 by Kenny Buntinx [MVP]

Hi All,

I previously blogged about customizing the sccm admin console using the right-click actions and blogged about how you can customize the console yourself using the correct guid and a fairly easy to construct xml.

Most of these extensions use some form of vbscript to trigger these actions, but if you are not a great scripter, don’t despair you can achieve quite a lot of these tasks using a single command line. The following 2 links give you a decent overview of what is achievable using wmic:

Specifically for ConfigMgr the following command lines are interesting from my point of view:

  • Trigger hardware inventory: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000001}”
  • Trigger software inventory: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000002}”
  • Trigger data discovery: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000003}”
  • Trigger machine policy assignment request: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000021}”
  • Trigger machine policy evaluation: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000022}”
  • Trigger Refresh default management point: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000023}”
  • Trigger Refresh location (Ad site, or subnet): WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000024}”
  • Trigger Software metering usage reporting: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000031}”
  • Trigger sourcelist update cycle: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000032}”
  • Refresh proxy manamgement point: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000037}”
  • Trigger cleanup policy: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000040}”
  • Trigger validate assignments: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000042}”
  • Trigger certificate maintenance: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000051}”
  • Trigger branch dp scheduled maintenance: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000061}”
  • Trigger branchdp provisioning status reporting: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000062}”
  • Trigger software update deployment: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000108}”
  • Trigger state message upload: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000111}”
  • Trigger state message cache cleanup: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000112}”
  • Trigger sofware update scan: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000113}”
  • Trigger software update deployment re-eval: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000114}”
  • Trigger OOBS discovery: WMIC /node:Computername /namespace:\\root\ccm path sms_client CALL TriggerSchedule “{00000000-0000-0000-0000-000000000120}”

And some more general ones:

  • reboot computer: wmic /node:computername os Where (name like ‘%windows%’) call reboot
  • shutdown computer: wmic /node:computername os Where (name like ‘%windows%’) call shutdown

 

Enjoy.

“Everyone is an expert at something”

Kim Oppalfens – Sms Expert for lack of any other expertise
Windows Server System MVP – SMS
http://www.scug.be/blogs/sccm/default.aspx

http://www.linkedin.com/in/kimoppalfens

Tweet about this on TwitterShare on FacebookShare on Google+Share on LinkedInPin on Pinterest