You don’t have to choose between the traditional command line interface (CLI) and PowerShell. You can easily run a PowerShell command or even a PowerShell script directly from a command prompt. This means you can integrate some PowerShell functionality into your older batch files. It also means that you can create a scheduled task to execute a PowerShell script!<\/p>\n
At a command prompt, run powershell \/? and you’ll see the proper syntax. Generally, you will want to use the format powershell -command “&{some powershell expression<\/span>}”<\/span>. I also prefer to use -nologo<\/span> to suppress the Windows PowerShell logo. This is especially useful if you want to capture the ouput to a text file. This also brings up an important point, because you are calling PowerShell from the CLI, any output returned is text <\/span>and not a PowerShell object. So when you run a CLI command like this:<\/p>\n powershell -nologo -command “& {get-process}”<\/span><\/p>\n It looks like normal PowerShell output. But if you capture it, it’s just text. Not that this is a bad thing. It may be just want you want.<\/p>\n I’ve put together a little batch file demo that you can run. It saves the output from several PowerShell expressions to a text file. It can even run a .ps1 file.<\/p>\n @echo off<\/span> If you want to try this out be sure to change the zlog variable path and any PowerShell script you might want to run. You should test this first interactively. Assuming everything works, then try it out as a scheduled task on your system. You should have an appropriate log file after the job completes.<\/p>\n If you try to schedule a batch file to run a PowerShell script, make sure the ps1 script doesn’t require any user input or interaction. Unless, of course, you create the job to be interactive.<\/p>\n Once you get the hang of it, you’ll realize you don’t always have to launch a full PowerShell instance to get something done. If you need the results of a simple PowerShell expression, you can stay in the CLI and get the best of both worlds.<\/p>\n","protected":false},"excerpt":{"rendered":" You don’t have to choose between the traditional command line interface (CLI) and PowerShell. You can easily run a PowerShell command or even a PowerShell script directly from a command prompt. This means you can integrate some PowerShell functionality into your older batch files. It also means that you can create a scheduled task to execute a PowerShell script!<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[18,2,25],"tags":[],"class_list":["post-352","post","type-post","status-publish","format-standard","hentry","category-batchcmd","category-general","category-windows-powershell"],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/352","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/comments?post=352"}],"version-history":[{"count":0,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/posts\/352\/revisions"}],"wp:attachment":[{"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/media?parent=352"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/categories?post=352"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.sapien.com\/blog\/wp-json\/wp\/v2\/tags?post=352"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
REM PoSHTest.bat<\/span>
set zlog=e:\\temp\\pslog.txt<\/span>
echo %date% %time% > %zlog%<\/span>
powershell -nologo -command “& {get-wmiobject win32_operatingsystem}” >>%zlog%<\/span>
REM you can use aliases<\/span>
powershell -nologo -command “& {gwmi win32_computersystem}” >>%zlog%<\/span>
REM You can use filtering blocks<\/span>
powershell -nologo -command “& {get-service | where {$_.status -eq ‘running’}}” >>%zlog%<\/span>
REM You can call other PowerShell scripts<\/span>
powershell -nologo -command “& {s:\\posh\\scheduleTest.ps1}”<\/span>
echo See %zlog% for results<\/span>
set zlog=<\/span><\/p>\n