{"id":5198,"date":"2020-06-24T18:28:33","date_gmt":"2020-06-24T22:28:33","guid":{"rendered":"https:\/\/batchpatch.com\/?p=5198"},"modified":"2020-06-24T18:30:46","modified_gmt":"2020-06-24T22:30:46","slug":"batchpatch-remote-command-execution-options","status":"publish","type":"post","link":"https:\/\/batchpatch.com\/batchpatch-remote-command-execution-options","title":{"rendered":"BatchPatch Remote Command Execution Options"},"content":{"rendered":"

BatchPatch has a number of commands and actions that are built-in and come with the software… Windows update commands, reboot and shutdown commands, wake on LAN, commands to get information from target computers about disk space usage, uptime, logged-on users, file version information, registry values, commands to review\/modify services and processes, and a lot more. But what if you want to execute a command that isn’t already built-in? Obviously not all commands are going to be useful for all users, and we can’t include every command that ever existed in the history of all commands \ud83d\ude42 Inevitably you might find yourself wanting to hard-code some of your own commands into BatchPatch to execute on remote systems.<\/p>\n

BatchPatch provides a few different places and ways to store and execute your own commands. <\/p>\n

1. Under ‘Actions > Get information > Create\/modify user-defined commands<\/em>‘ BatchPatch provides and interface for you to add your own commands. Once a command is added in this interface, the command will appear in the BatchPatch menu under ‘Actions > Get information > Execute user-defined commands<\/em>‘<\/p>\n

\"\"<\/a><\/p>\n

\"\"<\/a><\/p>\n

2. Under ‘Actions > Execute remote process\/command<\/em>‘ there are several options. Remote command 1, 2, 3, 4 can be created and will be stored in the current grid and visible in the row under which they are created. Commands 1 and 2 do not attempt to capture output and will only report exit codes upon execution. Commands 3 and 4 attempt to capture output, so that you can display the output in the grid upon execution. Under the hood the logged-output commands (3\/4) have to be executed differently from the standard commands (1\/2), and in some cases this difference can cause failure, which is why we separate these completely. If a command fails to execute under 3\/4 it might be successful under 1\/2.<\/p>\n

\"\"<\/a><\/p>\n

Additionally under ‘Actions > Execute remote process\/command<\/em>‘ we have ‘Create\/modify remote commands<\/em>‘ and ‘Create modify remote commands (logged output)<\/em>‘ where you can create commands that won’t be tied to a particular grid and will instead be saved globally for all BatchPatch instances that you launch. Commands created under these interfaces appear hard-coded in the BatchPatch menu under ‘Actions > Execute remote process\/command<\/em>‘ as ‘Execute saved remote commands<\/em>‘ and ‘Execute saved remote commands (logged output)<\/em>‘, respectively.<\/p>\n

\"\"<\/a><\/p>\n

More details on hard-coding custom commands into BatchPatch can be found here: How to Hard-Code Your Own Custom Commands in the BatchPatch Actions Menu<\/a><\/p>\n

<\/p>\n

\n

<\/p>\n

Once a command has been hard-coded into BatchPatch, not only is it available for direct execution on target computers, but now it can also be included in job queues or be executed by the Task Scheduler. You can see in the screenshot below that the Job Queue window shows all of my previously created hard-coded commands, deployments, copy jobs etc. I can add any of them to a job queue for automation.<\/p>\n

\"\"<\/a><\/p>\n

Additionally, all job queues will appear along with all hard-coded commands, deployments, copy jobs etc in the Task Scheduler so that you can schedule any job queue or command that you have previously created.<\/p>\n

\"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

BatchPatch has a number of commands and actions that are built-in and come with the software… Windows update commands, reboot and shutdown commands, wake on LAN, commands to get information from target computers about disk space usage, uptime, logged-on users, file version information, registry values, commands to review\/modify services and processes, and a lot more. […]<\/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],"tags":[217,227,420],"class_list":["post-5198","post","type-post","status-publish","format-standard","hentry","category-blog","category-general","tag-remote-commands","tag-remote-execution","tag-remote-scripts"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts\/5198","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=5198"}],"version-history":[{"count":1,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts\/5198\/revisions"}],"predecessor-version":[{"id":5205,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/posts\/5198\/revisions\/5205"}],"wp:attachment":[{"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/media?parent=5198"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/categories?post=5198"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/batchpatch.com\/wp-json\/wp\/v2\/tags?post=5198"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}