Skip to main content

Reading and Resolving PowerShell Errors - Part 8

By
This is part 8 of my series of the most common PowerShell errors that are made in my PowerShell classes.  I will be posting one a day to help you understand why an error occurred and what the error’s meaning is.

Today’s error: No data returned from a remote command

Here is our starting code:
Invoke-Command -ComputerName DC, SVR1 -ScriptBlock {
        Param ($ID, $MT)
        Get-CimInstance -ClassName Win32_Logicaldisk |
        Where {$_.DeviceID -eq $ID -and $_.MediaType -eq $MT}
    } -ArgumentList 12,"C:"

And here is the full error:
There is no error except nothing comes back.

Resolution:
Change the order of the arguments.
In this example, we are passing information from the local device to the remote device.  The problem is in order of information being passed from the –ArgumentList to the PARAM() variables.  They are being passed in the wrong order.  The first item in the –ArgumentList will be past to the first variable in the PARAM() list.  The second to the second and so on and so forth. 
I have had people argue with me that they should be able to choose which value is saved to which variable.  Well, you do.  This is an ordered list.  Order it correctly.
Invoke-Command -ComputerName DC, SVR1 -ScriptBlock {
        Param ($ID, $MT)
        Get-CimInstance -ClassName Win32_Logicaldisk |
        Where {$_.DeviceID -eq $ID -and $_.MediaType -eq $MT}
    } -ArgumentList "C:",12

DeviceID DriveType ProviderName VolumeName Size        FreeSpace  PSComputerName
-------- --------- ------------ ---------- ----        ---------  --------------
C:       3                                 10368315392 1352790016 DC           
C:       3                                 10368315392 2048032768 SVR1  



Labels:

Comments

Post a Comment

Popular posts from this blog

How to run GPResult on a remote client with PowerShell

By
In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection.  In all cases, this will disrupt the user.  First, you need PowerShell remoting enabled on the target machine.  You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target.  Remember, the target needs to be online and accessible to you.
Post a Comment
Read more

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:          Remote Scheduled Tasks Management (RPC)          Remote Scheduled Tasks Management (RPC-ERMAP)          Windows Management Instrumentation (WMI-IN) I decided to create a little PowerShell script to crea...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more