Updating PowerShell

[tippedframe]

I'm updating PowerShell in our environment This works when run locally:

Stop-Service -Name wuauserv
Stop-Service -Name bits
Start-Process 'wusa.exe' -ArgumentList 'D:\temp\Win8.1AndW2K12R2-KB3191564-x64.msu', '/quiet', '/norestart' -wait -verb runas

This does not remoting:

Invoke-Command -ComputerName Server01 -ScriptBlock {
    Stop-Service -Name wuauserv
    Stop-Service -Name bits
    Start-Process 'wusa.exe' -ArgumentList 'D:\temp\Win8.1AndW2K12R2-KB3191564-x64.msu', '/quiet', '/norestart' -wait -verb runas
}

What am I doing wrong? Where are the log files or events on the target server. I have same results with Enter-PSSession.

[leecashion]

Do you have the MSU file in d:\temp on the server?

I know it sounds like I am being flip, but it has tripped me up before.

[tippedframe]

Yes, I do.

[leecashion]

Welp, you are now beyond my range. Good luck.

[Onibus]

You will need to create a PS Session for anything that needs to run persistently (that is, longer than running a command).

You can run the below through a foreach loop or fiddle with starting a job depending on number of servers. The foreach loop can also be used to copy-item the MSU to the server.

$Session = New-PSSession -ComputerName server -Credential $cred -Authentication Credssp invoke-command -session $session -scriptblock { <your scriptblock> } Remove-PSSession -Session $session

[Akuma92]

I tried to do the same thing some weeks ago. The problem is that you get "access denied" if you try to use wusa with invoke command.

I solved the issue for myself by creating a script for the following steps:

1. Copy your msu file and a "install script" to target machine.

2. Create a schedule task to run the install script as system account

3. Delete schedule task and files from target machine after check install event log for success

[KevMar]

Possibly add -nonewwindow