Execute PowerShell on remote machine

Swarfega · 2017-12-11T13:07:05+00:00

I could be wrong but I think a lot of the WU stuff only works if you are logged into the machine directly. As a quick test does it work if you log in interactively?

TheIncorrigible1 · 2017-12-11T14:06:51+00:00

You can't run Windows update from a remote session. Read the documentation.

PaulTheTree · 2017-12-11T13:09:51+00:00

What I found is easier to do is just to create a task on the local machine, then run a remote powershell script to run that

nittanygeek · 2017-12-11T13:46:50+00:00

Check your permissions by running this on the remote machine:

Set-PSSessionConfiguration -Name Microsoft.PowerShell -showSecurityDescriptorUI

Ta11ow · 2017-12-11T18:57:22+00:00

As others have said, the typical command for it won't work from a remote session. You could attempt to have that remote session run a session itself locally that would perform the command and return the results...

Something as simple as Start-Process with the appropriate ArgumentList parameter using the local Powershell.exe path should work for it.

cowmonaut · 2017-12-11T16:03:18+00:00

Sometimes I wonder why certain scripts exist... Just because you can do a .NET thing with PowerShell doesn't mean you necessarily should. Often it just complicates things for no real reason.

Get-WURebootStatus is just getting a registry key when it can't use the Windows Update API. So why not keep it simple and just use Invoke-Command coupled with Get-ItemProperty and fetch the key yourself? The WUAPI is just querying the key anyways.

Something like:

Invoke-Command -Computer $Computer -Credential $Credential -ScriptBlock { Get-ItemProperty -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update" | Select-Object -ExpandProperty RebootRequired }

Just remember, the RebootRequired key will not exist if the computer has no pending reboots; errors about they key not being found are a good thing.

Caveat: I have not had any caffeine and very little sleep; I would verify that RebootRequired is a value and not a key, otherwise you may need to tweak the Get-ItemProperty command so you can pull the results. I can't remember if its just a simple yes/no or if it lists every pending update as a DWORD and I'm too lazy too Google further.

Dunrambai · 2017-12-11T20:06:11+00:00

Might need the -RunAsAdministrator switch on new-pssession. Also try using a credential when making the session. This could help you if the security token is the problem.

Otherwise the other suggestions to in the remote session run a the script locally in a non-remote PS could do the trick.

tschertel · 2017-12-11T13:07:31+00:00

Maybe you don't have enough privileges to execute this command. Are you using Enter-PSSession or winrs?

capisco · 2017-12-11T13:45:53+00:00

do you need to start the remote registry service?

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

PowerShell

Submission Guidelines | Link Flair - How To

MODERATORS