{"id":3041,"date":"2016-06-01T16:31:55","date_gmt":"2016-06-01T20:31:55","guid":{"rendered":"http:\/\/batchpatch.com\/?p=3041"},"modified":"2016-06-01T16:32:23","modified_gmt":"2016-06-01T20:32:23","slug":"triggering-configmgr-sccm-client-actions-remotely","status":"publish","type":"post","link":"https:\/\/batchpatch.com\/triggering-configmgr-sccm-client-actions-remotely","title":{"rendered":"Triggering ConfigMgr (SCCM) Client Actions Remotely"},"content":{"rendered":"<p>As a convenience for those of you are using SCCM in your environment, last year we added the ability to trigger SCCM client actions remotely, directly from BatchPatch.  We&#8217;ve received a few questions about this topic recently, so I figured I would take a few minutes to provide some context here.<\/p>\n<p>SCCM administrators sometimes need or want to initiate a certain activity on client computers at non-scheduled times.  For example, maybe you need your clients to perform a &#8216;Software Inventory,&#8217; and you would like to execute that action on-demand.  You could certainly establish a remote connection to all of the computers in question, and then you could execute a command line task to trigger the desired process.  Or you could fire up PsExec from your workstation, and then use it to remotely trigger the process on a set of target computers.  However, if you are a BatchPatch user, you can initiate the process directly from BatchPatch in a single click.  BatchPatch isn&#8217;t doing any special magic here.  We&#8217;re simply making it quicker\/easier for you to remotely trigger SCCM client actions without having to mess with any command line copy\/paste.<\/p>\n<p>The list of SCCM triggers available in BatchPatch are:<\/p>\n\n<div class=\"wp_syntax\"><table><tr><td class=\"code\"><pre class=\"text\" style=\"font-family:monospace;\">{00000000-0000-0000-0000-000000000001} Hardware Inventory\n{00000000-0000-0000-0000-000000000002} Software Inventory\n{00000000-0000-0000-0000-000000000003} Discovery Inventory\n{00000000-0000-0000-0000-000000000010} File Collection\n{00000000-0000-0000-0000-000000000011} IDMIF Collection\n{00000000-0000-0000-0000-000000000012} Client Machine Authentication\n{00000000-0000-0000-0000-000000000021} Request Machine Assignments\n{00000000-0000-0000-0000-000000000022} Evaluate Machine Policies\n{00000000-0000-0000-0000-000000000023} Refresh Default MP Task\n{00000000-0000-0000-0000-000000000024} LS (Location Service) Refresh Locations Task\n{00000000-0000-0000-0000-000000000025} LS (Location Service) Timeout Refresh Task\n{00000000-0000-0000-0000-000000000026} Policy Agent Request Assignment (User)\n{00000000-0000-0000-0000-000000000027} Policy Agent Evaluate Assignment (User)\n{00000000-0000-0000-0000-000000000031} Software Metering Generating Usage Report\n{00000000-0000-0000-0000-000000000032} Source Update Message\n{00000000-0000-0000-0000-000000000037} Clearing proxy settings cache\n{00000000-0000-0000-0000-000000000040} Machine Policy Agent Cleanup\n{00000000-0000-0000-0000-000000000041} User Policy Agent Cleanup\n{00000000-0000-0000-0000-000000000042} Policy Agent Validate Machine Policy \/ Assignment\n{00000000-0000-0000-0000-000000000043} Policy Agent Validate User Policy \/ Assignment\n{00000000-0000-0000-0000-000000000051} Retrying\/Refreshing certificates in AD on MP\n{00000000-0000-0000-0000-000000000061} Peer DP Status reporting\n{00000000-0000-0000-0000-000000000062} Peer DP Pending package check schedule\n{00000000-0000-0000-0000-000000000063} SUM Updates install schedule\n{00000000-0000-0000-0000-000000000071} NAP action\n{00000000-0000-0000-0000-000000000101} Hardware Inventory Collection Cycle\n{00000000-0000-0000-0000-000000000102} Software Inventory Collection Cycle\n{00000000-0000-0000-0000-000000000103} Discovery Data Collection Cycle\n{00000000-0000-0000-0000-000000000104} File Collection Cycle\n{00000000-0000-0000-0000-000000000105} IDMIF Collection Cycle\n{00000000-0000-0000-0000-000000000106} Software Metering Usage Report Cycle\n{00000000-0000-0000-0000-000000000107} Windows Installer Source List Update Cycle\n{00000000-0000-0000-0000-000000000108} Software Updates Assignments Evaluation Cycle\n{00000000-0000-0000-0000-000000000109} Branch Distribution Point Maintenance Task\n{00000000-0000-0000-0000-000000000110} DCM policy\n{00000000-0000-0000-0000-000000000111} Send Unsent State Message\n{00000000-0000-0000-0000-000000000112} State System policy cache cleanout\n{00000000-0000-0000-0000-000000000113} Scan by Update Source\n{00000000-0000-0000-0000-000000000114} Update Store Policy\n{00000000-0000-0000-0000-000000000115} State system policy bulk send high\n{00000000-0000-0000-0000-000000000116} State system policy bulk send low\n{00000000-0000-0000-0000-000000000120} AMT Status Check Policy\n{00000000-0000-0000-0000-000000000121} Application manager policy action\n{00000000-0000-0000-0000-000000000122} Application manager user policy action\n{00000000-0000-0000-0000-000000000123} Application manager global evaluation action\n{00000000-0000-0000-0000-000000000131} Power management start summarizer\n{00000000-0000-0000-0000-000000000221} Endpoint deployment reevaluate\n{00000000-0000-0000-0000-000000000222} Endpoint AM policy reevaluate\n{00000000-0000-0000-0000-000000000223} External event detection<\/pre><\/td><\/tr><\/table><\/div>\n\n<p>In BatchPatch you can see all of the triggers listed alphabetically under <em><strong>&#8216;Tools > SCCM client triggers.&#8217;<\/strong> <\/em> <\/p>\n<p>To execute a particular task, simply highlight the desired target computers in the grid, then select &#8216;Tools > SCCM client triggers&#8217; and choose the desired task.  In the screenshot below you can see that when I hover over a particular task, it shows the actual command that will be executed on the target host.<\/p>\n<p><a href=\"\/wp-content\/uploads\/2016\/06\/SCCM-client-triggers-BatchPatch.png\"><img loading=\"lazy\" decoding=\"async\" src=\"\/wp-content\/uploads\/2016\/06\/SCCM-client-triggers-BatchPatch-1024x570.png\" alt=\"SCCM-client-triggers-BatchPatch\" width=\"540\" height=\"301\" class=\"aligncenter size-large wp-image-3042\" srcset=\"https:\/\/batchpatch.com\/wp-content\/uploads\/2016\/06\/SCCM-client-triggers-BatchPatch-1024x570.png 1024w, https:\/\/batchpatch.com\/wp-content\/uploads\/2016\/06\/SCCM-client-triggers-BatchPatch-300x167.png 300w, https:\/\/batchpatch.com\/wp-content\/uploads\/2016\/06\/SCCM-client-triggers-BatchPatch-768x428.png 768w, https:\/\/batchpatch.com\/wp-content\/uploads\/2016\/06\/SCCM-client-triggers-BatchPatch.png 1482w\" sizes=\"auto, (max-width: 540px) 100vw, 540px\" \/><\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>As a convenience for those of you are using SCCM in your environment, last year we added the ability to trigger SCCM client actions remotely, directly from BatchPatch. We&#8217;ve received a few questions about this topic recently, so I figured I would take a few minutes to provide some context here. SCCM administrators sometimes need [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1,17,3],"tags":[202],"class_list":["post-3041","post","type-post","status-publish","format-standard","hentry","category-blog","category-general","category-tutorials","tag-sccm-client-triggers"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts\/3041","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/comments?post=3041"}],"version-history":[{"count":3,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts\/3041\/revisions"}],"predecessor-version":[{"id":3045,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts\/3041\/revisions\/3045"}],"wp:attachment":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/media?parent=3041"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/categories?post=3041"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/tags?post=3041"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}