blocks|key|202366|text|以下是对我有效的命令。我不喜欢在脚本中重定向输出的想法，因为这会使手动运行变得困难。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|202367|powershell+-windowstyle+minimized+-c+"powershell+-c+.\myscript.ps1+-verbose+>>+\\server\myscript.log+2>&1"|code-block|syntax|javascript|202368|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Here is the command that worked for me. I didn't like the idea of redirecting the output in the script, since it would make it difficult to run manually.

<pre><code>powershell -windowstyle minimized -c "powershell -c .\myscript.ps1 -verbose &gt;&gt; \\server\myscript.log 2&gt;&amp;1"
</code></pre>

blocks|key|420695|text|我使用文字记录功能来帮助解决这个问题。只需将其包含在代码中，它就会将所有(可能是)屏幕内容输出到日志文件中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|420696|Start-Transcript+-path+$LogFile+-append

<Body+of+the+script>

Stop-Transcript|code-block|syntax|javascript|420697|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I use the transcript feature to help with this. Just include it in your code and it outputs all (would be) screen content to a log file.
<pre><code>Start-Transcript -path $LogFile -append

&lt;Body of the script&gt;

Stop-Transcript
</code></pre>

blocks|key|202435|text|以下内容适用于我在Windows+7上的工作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|202436|+powershell+-command+c:\temp\pscript.ps1+2>&1+>+c:/temp/apickles.log|code-block|syntax|javascript|202437|在Windows+7任务调度器GUI中：|202438|+program+=+"Powershell"
+arguments+=+"-command+c:\temp\pscript.ps1+2>&1+>+c:/temp/apickles.log"|202439|请注意，"-file“不起作用，因为文件名之后的所有参数都被解释为文件的参数。请注意，"2>&1“也会将错误输出重定向到日志文件。PowerShell的后续版本会以略有不同的方式来实现这一点。|202440|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The following works for me on Windows&nbsp;7:

<pre><code> powershell -command c:\temp\pscript.ps1 2&gt;&amp;1 &gt; c:/temp/apickles.log
</code></pre>

In the Windows&nbsp;7 Task Scheduler GUI:

<pre><code> program = "Powershell"
 arguments = "-command c:\temp\pscript.ps1 2&gt;&amp;1 &gt; c:/temp/apickles.log"
</code></pre>

Note that "-file" does not work because all parameters after the file name are interpreted as parameters to the file.
Note that "2>&amp;1" redirects the error output to the log file as well. Later versions of PowerShell do this in a slightly different way.

blocks|key|420849|text|之前所有答案的组合真的对我很有帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|420850|我的问题是，我需要在WinRM上执行一个PowerShell脚本，作为打包提供程序的一部分，但由于权限问题，它总是失败。解决方法是作为计划任务执行，但我需要将参数传递给脚本并获得输出，以确认通过的所有内容。|offset|length|420851|这段代码对我来说工作得很好：|420852|#+Generate+a+unique+ID+for+this+execution
$guid+=+[guid]::NewGuid()
$logFile+=+"C:\Windows\Temp\$guid.log"

$argument+=+"-NoProfile+-ExecutionPolicy+unrestricted+-Command+""&+{""$ScriptPath""+$ScriptArgs}+2>&1+>+$logFile"""

$a+=+New-ScheduledTaskAction+-Execute+"powershell.exe"+-Argument+$argument
Register-ScheduledTask+-TaskName+$TaskName++-RunLevel+Highest+-User+$username+-Password+$password+-Action+$a+%7C+Start-ScheduledTask
do+{
++++Start-Sleep+-Seconds+30
++++$task+=+Get-ScheduledTask+-TaskName+$TaskName
}+while+($task.State+-eq+4)|code-block|syntax|javascript|420853|完整的脚本可以在这里找到：|420854|https://gist.github.com/dev-rowbot/fa8b8dadf1b3731067a93065db3e1bba|420855|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Windows_Remote_Management|1^0|0|A|5|0|0|0|0|0|0|1V|1|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@$D|11|E|12|1|13]]|A|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|15|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|16|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|Q|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|P]]]]

A combination of all the previous answers really helped me out...

My problem was that I needed to execute a PowerShell script over <a href="https://en.wikipedia.org/wiki/Windows_Remote_Management" rel="nofollow noreferrer">WinRM</a> as part of a Packer provisioner, and it kept failing due to rights issues. The way around this is to execute as a scheduled task, but I needed to pass arguments to the script and get the output as well to confirm everything passed.

This snippet worked well for me:

<pre><code># Generate a unique ID for this execution
$guid = [guid]::NewGuid()
$logFile = "C:\Windows\Temp\$guid.log"

$argument = "-NoProfile -ExecutionPolicy unrestricted -Command ""&amp; {""$ScriptPath"" $ScriptArgs} 2&gt;&amp;1 &gt; $logFile"""

$a = New-ScheduledTaskAction -Execute "powershell.exe" -Argument $argument
Register-ScheduledTask -TaskName $TaskName -RunLevel Highest -User $username -Password $password -Action $a | Start-ScheduledTask
do {
 Start-Sleep -Seconds 30
 $task = Get-ScheduledTask -TaskName $TaskName
} while ($task.State -eq 4)
</code></pre>

The full script can be found here:

<a href="https://gist.github.com/dev-rowbot/fa8b8dadf1b3731067a93065db3e1bba" rel="nofollow noreferrer">https://gist.github.com/dev-rowbot/fa8b8dadf1b3731067a93065db3e1bba</a>

blocks|key|420629|text|我会这样做：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|420630|创建一个函数来调用您的脚本并重定向此函数的输出，如下所示：|420631|.ps1：|420632|function+test{
++++#+Your+simple+script+commands
++++ls+c:\temp+-Filter+*.JPG
++++ls+z:\+#+Non-existent+directory
}

test+*>+c:\temp\log.txt|code-block|syntax|javascript|420633|以下是日志文件：|420634|++++Répertoire+:+C:\temp


Mode++++++++++++++++LastWriteTime+++++Length+Name
----++++++++++++++++-------------+++++------+----
-a---++++++++07/06/2008+++++11:06+++++176275+HPIM1427.JPG
-a---++++++++07/06/2008+++++11:06++++++69091+HPIM1428.JPG
-a---++++++++07/06/2008+++++11:06+++++174661+HPIM1429.JPG


ls+:+Lecteur+introuvable.+Il+n'existe+aucun+lecteur+nommé+«+z+».
Au+caractère+C:\temp\test.ps1:14+:+1
%2B+ls+z:\+#non+existent+dir
%2B+~~~~~~
++++%2B+CategoryInfo++++++++++:+ObjectNotFound:+(z:String)+[Get-ChildItem],+Driv
+++eNotFoundException
++++%2B+FullyQualifiedErrorId+:+DriveNotFound,Microsoft.PowerShell.Commands.GetC
+++hildItemCommand|420635|您可以使用新的V3重定向操作符控制要输出的内容：|420636|Do-Something+3>+warning.txt++#+Writes+warning+output+to+warning.txt
Do-Something+4>>+verbose.txt+#+Appends+verbose.txt+with+the+verbose+output
Do-Something+5>&1++++++++++++#+Writes+debug+output+to+the+output+stream
Do-Something+*>+out.txt++++++#+Redirects+all+streams+(output,+error,+warning,+verbose,+and+debug)+to+out.txt|420637|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|Y|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|10|8|@]|9|@]|A|$]]|$1|Q|3|R|5|H|7|11|8|@]|9|@]|A|$I|J]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I would do: 
Create a function to call your script and redirect the output of this function like this:
<h3>.ps1:</h3>
<pre><code>function test{
 # Your simple script commands
 ls c:\temp -Filter *.JPG
 ls z:\ # Non-existent directory
}

test *&gt; c:\temp\log.txt
</code></pre>
Here is the log file:
<pre><code> Répertoire : C:\temp


Mode LastWriteTime Length Name
---- ------------- ------ ----
-a--- 07/06/2008 11:06 176275 HPIM1427.JPG
-a--- 07/06/2008 11:06 69091 HPIM1428.JPG
-a--- 07/06/2008 11:06 174661 HPIM1429.JPG


ls : Lecteur introuvable. Il n'existe aucun lecteur nommé « z ».
Au caractère C:\temp\test.ps1:14 : 1
+ ls z:\ #non existent dir
+ ~~~~~~
 + CategoryInfo : ObjectNotFound: (z:String) [Get-ChildItem], Driv
 eNotFoundException
 + FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.GetC
 hildItemCommand
</code></pre>
You can control what do you want to output with the new V3 redirection operators:
<pre><code>Do-Something 3&gt; warning.txt # Writes warning output to warning.txt
Do-Something 4&gt;&gt; verbose.txt # Appends verbose.txt with the verbose output
Do-Something 5&gt;&amp;1 # Writes debug output to the output stream
Do-Something *&gt; out.txt # Redirects all streams (output, error, warning, verbose, and debug) to out.txt
</code></pre>

blocks|key|420881|text|为了直接记录到文件，使用Start-Transcript可能更容易：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|420882|#+Get+script+name
$ScriptFullPath+=+$MyInvocation.MyCommand.Path
#+Start+logging+stdout+and+stderr+to+file
Start-Transcript+-Path+"$ScriptFullPath.log"+-Append

[Some+PowerShell+commands]

#+Stop+logging+to+file
Stop-Transcript|code-block|syntax|javascript|420883|日志文件将与脚本位于同一目录中。|420884|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.host/start-transcript^0|C|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|F|7|W|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|X|8|@]|9|@]|C|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

It would be maybe easier to use <a href="https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.host/start-transcript" rel="nofollow noreferrer">Start-Transcript</a> in order to log directly to a file:

<pre><code># Get script name
$ScriptFullPath = $MyInvocation.MyCommand.Path
# Start logging stdout and stderr to file
Start-Transcript -Path "$ScriptFullPath.log" -Append

[Some PowerShell commands]

# Stop logging to file
Stop-Transcript
</code></pre>

The log file will be in the same directory as the script.

blocks|key|421056|text|我在Windows+Server+2016上测试了以下代码，只调用了powershell一次。这样，您可以使用带有空格的文件夹名称：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|421057|Powershell.exe+-NoProfile+-ExecutionPolicy+Bypass+-WindowStyle+minimized+"scriptName.ps1+*>>+'\\servername\sharename\folder+name+with+space\logfilename.log'"|code-block|syntax|javascript|421058|entityMap^0|Y|A|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

I tested the following on Windows Server 2016, only call <code>powershell</code> once. This way you can have folder names with a space:
<pre><code>Powershell.exe -NoProfile -ExecutionPolicy Bypass -WindowStyle minimized &quot;scriptName.ps1 *&gt;&gt; '\\servername\sharename\folder name with space\logfilename.log'&quot;
</code></pre>

blocks|key|202636|text|PowerShell+3及更高版本允许重定向单个流(传出、详细和错误)。但是，任务调度器无法理解它们。执行重定向的是PowerShell。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|202637|因为PowerShell正在调用PowerShell，所以@cmcginty's+solution在半路上工作。它只支持标准流(error和out)。如果你想使用所有的流，你需要使用：|offset|length|202638|程序或脚本：C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe|style|CODE|202639|参数：-windowstyle+minimized+–NonInteractive+–NoProfile+-c+"powershell+-c+path_to_ps1.ps1+4>>verbose.log+5>>debug.log"|202640|起始位置：path_to_ps1|202641|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/13827861/185123^0|0|T|K|0|0|6|1L|0|3|34|0|5|B|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|F|3|G|5|6|7|10|8|@$D|11|E|12|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@$D|14|E|15|H|I]]|9|@]|A|$]]|$1|L|3|M|5|6|7|16|8|@$D|17|E|18|H|I]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

PowerShell 3 onwards allows individual streams (out, verbose, and error) to be redirected. However, Task Scheduler does not understand them. It's PowerShell that does the redirection.
<a href="https://stackoverflow.com/a/13827861/185123">@cmcginty's solution</a> halfway works, since PowerShell is invoking PowerShell. It only supports standard streams (error and out). If you want to use all streams you need to use:
Program or script: <code>C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe</code>
Argument: <code>-windowstyle minimized –NonInteractive –NoProfile -c &quot;powershell -c path_to_ps1.ps1 4&gt;&gt;verbose.log 5&gt;&gt;debug.log&quot;</code>
Start in: <code>path_to_ps1</code>

blocks|key|202705|text|我写这个答案的灵感来自Anders的一个评论问题(如何添加时间戳？)，以及两次调用PowerShell的多个回复，我认为这并不是必需的。任务调度程序显然是"powershell.exe“的，对于这些参数，我会简单地建议：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|202706|-noninteractive+-c+"scriptpath.ps1+*>>logpath.txt"|code-block|syntax|javascript|202707|要每天保留一个文件，请执行以下操作：|202708|-noninteractive+-c+"scriptpath.ps1+*>>logpath-$((get-date).ToString('yyyy-MM-dd')).txt"|202709|如果您确实需要一个带有时间戳的日志文件，您可以删除第二个">“(两个表示附加到任何现有文件)，并扩展时间格式：|202710|-noninteractive+-c+"scriptpath.ps1+*>logpath-$((get-date).ToString('yyyy-MM-dd_HH-mm-ss-fff')).txt"|202711|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|S|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|U|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

I'm inspired to write this answer by a comment-question from Anders (How do you add a timestamp?), and by the multiple replies that invoke PowerShell twice, which I would argue is not required. The task scheduler program is clearly &quot;powershell.exe&quot; and for the arguments I would suggest simply:
<pre><code>-noninteractive -c &quot;scriptpath.ps1 *&gt;&gt;logpath.txt&quot;
</code></pre>
To keep a file per day, then:
<pre><code>-noninteractive -c &quot;scriptpath.ps1 *&gt;&gt;logpath-$((get-date).ToString('yyyy-MM-dd')).txt&quot;
</code></pre>
And if you do want a log file with timestamp, you could remove the second &quot;&gt;&quot; (two indicating append to any existing file) and expand the time format:
<pre><code>-noninteractive -c &quot;scriptpath.ps1 *&gt;logpath-$((get-date).ToString('yyyy-MM-dd_HH-mm-ss-fff')).txt&quot;
</code></pre>

blocks|key|202503|text|下面的代码将详细输出发送到屏幕，并将其记录到文件中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|202504|something+you're+doing+-Verbose+4>&1+%7C+Tee-Object+"C:\logs\verb.log"+-Append|code-block|syntax|javascript|202505|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The below sends verbose output to the screen as well as log it to a file.

<pre class="lang-none prettyprint-override"><code>something you're doing -Verbose 4&gt;&amp;1 | Tee-Object "C:\logs\verb.log" -Append
</code></pre>

When running a simple PowerShell script from Task Scheduler, I would like to redirect the output to a file. 

There is a long thread about this very topic <a href="http://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/32952fdf-b3b8-44f9-a3c4-62bd802b1f39" rel="noreferrer">here</a>, yet it's not clear if they reached the most appropriate solution in the end. I'm interested if anyone on Stack&nbsp;Overflow has also solved this problem, and how they did it?

How can I redirect PowerShell output when run from Task Scheduler?

当从Task Scheduler运行一个简单的PowerShell脚本时，我希望将输出重定向到一个文件。关于这个话题有很长的线索，但还不清楚他们最终是否得到了最合适的解决方案。我感兴趣的是，Stack Overflow上是否有人也解决了这个问题，以及他们是如何做到的？

问从任务计划程序运行时，如何重定向PowerShell输出？
EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从任务计划程序运行时，如何重定向PowerShell输出？EN

回答 10

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问从任务计划程序运行时，如何重定向PowerShell输出？
EN