Skip to main content

Reading and Resolving PowerShell Errors - Part 8

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  



Comments

Popular posts from this blog

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory.  To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

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.

Error icon when creating a GPO Preference drive map

You may not have an error at all.  Take a look at the drive mapping below. The red triangle is what threw us off.  It is not an error.  It is simply a color representation of the Replace option of the Action field in the properties of the drive mappings. Create action This give you a green triangle. The Create action creates a new mapped drive for users. Replace Action The Replace action gives you a red triangle.  This action will delete and recreate mapped drives for users. The net result of the Replace action is to overwrite all existing settings associated with the mapped drive. If the drive mapping does not exist, then the Replace action creates a new drive mapping. Update Action The Update action will have a yellow triangle. Update will modify settings of an existing mapped drive for users. This action differs from Replace in that it only updates settings defined within the preference item. All other settings remain as configured on the mapped drive. If the