CODEWITHSUNDEEP
powershellpowershell-remotinginvoke-commandwindows-update
Alex Pilon
Alex Pilon

Reputation: 103

Access denied while running Windows Update using Powershell's Invoke-Command

I've been trying to setup a Powershell module that would remotely call Windows/Microsoft update on a server using Invoke-Command, then process the updates, and send everything back to the calling server so it can send an email report.

My issue comes when I try and call the downloader: Powershell seems to be requesting Elevated rights on the remote computer.

Here is a snippet of what I'm trying to run and fail:

Invoke-Command -ComputerName $Server -Credential $Credentials -ScriptBlock {
    $UpdateSession = New-Object -ComObject "Microsoft.Update.Session"
    Write-Progress -Activity "Updating" -Status "Checking for new updates"
    $Criteria = "IsInstalled=0 and Type='Software'"
    $Updates = $UpdateSession.CreateUpdateSearcher().Search($Criteria).updates
    $Downloader = $UpdateSession.CreateUpdateDownloader()
    $Downloader.Updates = $Updates
}

I know the issue isn't with remoting, as the first 4 commands work fine. The $Credentials variable points to pre-defined credentials, which are Local Admin on the remote server.

When the script gets to the 5th line, $Downloader = $UpdateSession.CreateUpdateDownloader(), I get this error from Powershell:

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
    + CategoryInfo          : OperationStopped: (:) [], UnauthorizedAccessException
    + FullyQualifiedErrorId : System.UnauthorizedAccessException
    + PSComputerName        : SERVER.sidlee.inc

What could be causing this exactly ?

Thanks in advance for the help!

Upvotes: 3

Views: 9314

Answers (1)

user1972814
user1972814

Reputation: 181

As i just hit the same wall, and Google isn't of much help either, here is what i could dig up.

For the record, i am pretty much doing the same thing (using custom PS code to check remote systems for Windows Updates) but using WinRM over Python instead of Invoke-Command and also got stuck on Microsoft.Update.Searcher.Search() throwing a E_ACCESSDENIED error.

The UnauthorizedAccessException is indeed not related to Powershell but the underlying API.

I suspect Microsoft started cutting off impersonation in remote session in some recent update (Powershell v5?) as this was (and still is) working just fine on older Windows versions (e.g. Server 2012 with Powershell v3 or 2012 R2 with v4)

To get around this you will need to authenticate (on the remote server) prior to executing your stuff with a PSCredential object.

So Remote Auth -> Local Auth -> Run stuff for example using Start-Process -Credential ...

e.g.

$pass = ConvertTo-SecureString "PA$$W0RD" -AsPlainText -Force
$creds = New-Object System.Management.Automation.PSCredential "User", $pass
Start-Process -Credential $creds powershell -ArgumentList "-Command & { ... whatever you want to do ... }"

Keep in mind that this poses a security risk as your password will be parsed in clear text, so don't do this over an unencrypted channel!

Upvotes: 0

Related Questions