Question

我将PowerShell作为行政管理机构,并使用以下的编码线,为更新窗户开户。罚款

Start-Process  wusa.exe  -ArgumentList  C:Tempwindows10.0-kb5032189-x64_0a3b690ba3fa6cd69a2b0f989f273cfeadba745f.msu  -verb runas

但是,现在,我正试图以某种方式利用这部法典,在遥远的电脑上操作档案。窗户更新档案的名称和偏远个人电脑的确切位置相同。

I came up with this code below which first gets admin credentials and passes it to the the invoke-command. Then the invoke-command runs the Start-Process code.

$Username =  username123 
$Password =  84fWfghnsf&5Fh 
$pass = ConvertTo-SecureString -AsPlainText $Password -Force
$Cred = New-Object System.Management.Automation.PSCredential -ArgumentList $Username,$pass
Invoke-Command -ComputerName 8HPF31J7V6.domain.local -Credential $Cred -ScriptBlock {Start-Process  wusa.exe  -ArgumentList  C:Tempwindows10.0-kb5032189-x64_0a3b690ba3fa6cd69a2b0f989f273cfeadba745f.msu  -verb runas}

问题在于,当我这样做时,遥远的《刑法》没有发生。

I also don t get any errors when running

任何关于我做什么错误的想法,或除此以外的任何其他解决办法?

Answer 1

Start-Process 电话:_wusa.exe <>>>>>><<<<<><><><>><>>>>>t/strentreleases/
Otherwise, with an ad-hoc remoting session implicitly created via use of the -ComputerName parameter, the Start-Process-launched process is automatically terminated when the Invoke-Command call returns.


通过PowerShell s remoting tra >,inviible在目标机器上执行, 代码>-Verb RonAs<> 代码/代码>是无意义的:


如果遥远过程已经升级is,则no effect。 请注意,如果遥控指挥系统的用户身份是目标机器的管理人,则远程程序自动提升<>。


如果是肯定的(只有在你明确准许非行政管理的用户使用PowerShell重操的情况下才会发生这种情况),那么电话必定会失败,因为不能提出UAC dialog。


www.un.org/Depts/DGACM/index_spanish.htm

虽然本答复中的信息原则上是正确的,但js2010。指出,为了成功地操作<代码>wusa.exe ,即为了安装Windows Updates,光靠表面上高的远距离会议运行即可而不是<>。

这一服务器系统回答提供了背景资料,https://github.com/mgajda83/PSWindowsUpdate”rel=“nofollow noreferer”> 第三方模块 PSUpdate<<>>>>。可提供一种解决办法,如果使用其时间安排特征<>。

因此,<><>>> ∗∗>

# ... credential construction code ($Cred) omitted # Note: If the *current user* is allowed to make remoting calls, # you may not need to construct credentials and don t need the # -Credential parameter below. # Note the use of -Wait, removal of -Verb RunAs Invoke-Command -ComputerName 8HPF31J7V6.domain.local -Credential $Cred -ScriptBlock { Start-Process -Wait wusa.exe -ArgumentList C:Tempwindows10.0-kb5032189-x64_0a3b690ba3fa6cd69a2b0f989f273cfeadba745f.msu }

Read on for an asynchronous alternative. Note that the (Start-Process -PassThru …).ExitCode technique shown below, for reporting the remote process exit code, can equally be used with the synchronous approach above.

<<><>Asynchronouslement:>

www.un.org/Depts/DGACM/index_spanish.htm 如果您不希望<代码>。 Invoke-Command 呼吁等待遥控发射过程(wusa.exe)终止。

在最简单的情况下,将-AsJob 转换 加入上述呼吁,其中将Invoke-Command 退回 >。可按要求就产出和完成情况提问的物体,<><>><>Receive-Job>>>和 <>>>>>>>>>>>> 和

www.un.org/Depts/DGACM/index_spanish.htm 通过 https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/new-pssession” rel=“nofollow noreferer”>New-PSSession,并将之通过scode><>-Session<<>>>>>>>>。这样的会议在以下网址上开放:https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.core/remove-pssession”rel=“nofollow noreferer”>Remove-PSSession 或由于无所作为而过时。

However, to make the call asynchronous, you must then not use -Wait with Start-Process, and track the lifetime of the process in the remote session, by adding -PassThru to output a process-information object that you must capture in a variable, and consult again in a later Invoke-Command call with the same -Session argument.

www.un.org/Depts/DGACM/index_spanish.htm 附有<代码>-AsJob的同步变量<>/strong>,其中进一步显示如何报告遥远过程exit代码:

# ... credential construction code omitted # Note the use of -AsJob and the use of -PassThru with Start-Process # so as to be able to report the process exit code. $remoteJob = Invoke-Command -AsJob -ComputerName 8HPF31J7V6.domain.local -Credential $Cred -ScriptBlock { ( Start-Process -Wait -PassThru wusa.exe -ArgumentList C:Tempwindows10.0-kb5032189-x64_0a3b690ba3fa6cd69a2b0f989f273cfeadba745f.msu ).ExitCode } # ... perform foreground activity here. # Now wait for the remote job to complete - which happens when # wusa.exe terminates - and report its exit code. $exitCode = $remoteJob | Receive-Job -Wait -AutoRemoveJob

友情链接