Get-WmiObject access denied

Question

Hello,

I have a simple custom command supposed to get the user name which is connected to as specific computer.

The command line is :

$User = Get-WmiObject -Class Win32_ComputerSystem -ComputerName "%dNSHostName%" | Select-Object UserName

The error is :

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Trace de pile: at <ScriptBlock>, <No file>: line 8

If I connect to the Adaxes server, run a powershell with the same user that is configured for this script, and run the get-wmiobject cmdlet, then it works.

So why I get an access denied from the Adaxes console?

Thanks in advance!

Answer 1

Hello,

PowerShell scripts in Adaxes are executed using the credentials of the Adaxes service account (specified during Adaxes installation), but network operations (e.g. getting instances of WMI objects using the Get-WmiObject cmdlet) are performed using the credentials specified in the Run as section of the Run a program or PowerShell script action. It looks like the account specified in the section does not have the necessary native Active Directory permissions in the domain where the target computer object resides. Please, make sure that the account has the permissions in the domain and check whether the issue persists.

Comments

Thanks for your answer. I am sure about it, that's the problem. On the adaxes server, I run a powershell with "run as another user" and I used the "This acocunt" login. Doing this way I get the outpout from the cmdlet.

---

We are having this same exact issue after upgrading to 2021. Worked fine in 2017. Running the command manually in Powershell from the Adaxes server as the RunAs user also works fine. Was there ever a solution to this?

---

Hello,

First of all, Adaxes 2017 was using PowerShell 2.0. Adaxes 2021 uses the latest version of PowerShell installed. We were not able to reproduce the issue. If the same accounts are used, the command behaves the very same way in Adaxes and in Windows PowerShell. Maybe, there were some changes in the way the cmdlet works. As a solution, you can try the following approach:

# Get saved credentials.
$username = $Context.RunAs.UserName
$password = $Context.RunAs.Password | ConvertTo-SecureString -AsPlainText -Force
$credential = New-Object System.Management.Automation.PsCredential($username, $password)

$User = Get-WmiObject -Class Win32_ComputerSystem -ComputerName "%dNSHostName%" -Credential $credential | Select-Object UserName

---

Thank you. I edited our code and added the -credential option and it worked. It seems like for this cmdlet, 2021 is not properly passing the runas into the script. So far, this only seems to be a problem with Get-WMIObject as other Powershell scripts "runas" just fine.