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

Adding a Comment to a GPO with PowerShell

As I'm writing this article, I'm also writing a customization for a PowerShell course I'm teaching next week in Phoenix.  This customization deals with Group Policy and PowerShell.  For those of you who attend my classes may already know this, but I sit their and try to ask the questions to myself that others may ask as I present the material.  I finished up my customization a few hours ago and then I realized that I did not add in how to put a comment on a GPO.  This is a feature that many Group Policy Administrators may not be aware of. This past summer I attended a presentation at TechEd on Group Policy.  One organization in the crowd had over 5,000 Group Policies.  In an environment like that, the comment section can be priceless.  I always like to write in the comment section why I created the policy so I know its purpose next week after I've completed 50 other tasks and can't remember what I did 5 minutes ago. In the Group Policy module for PowerShell V3, th

Return duplicate values from a collection with PowerShell

If you have a collection of objects and you want to remove any duplicate items, it is fairly simple. # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   # Remove the duplicate values. $Set1 | Select-Object -Unique 1 2 3 4 5 6 7 What if you want only the duplicate values and nothing else? # Create a collection with duplicate values $Set1 = 1 , 1 , 2 , 2 , 3 , 4 , 5 , 6 , 7 , 1 , 2   #Create a second collection with duplicate values removed. $Set2 = $Set1 | Select-Object -Unique   # Return only the duplicate values. ( Compare-Object -ReferenceObject $Set2 -DifferenceObject $Set1 ) . InputObject | Select-Object – Unique 1 2 This works with objects as well as numbers.  The first command creates a collection with 2 duplicates of both 1 and 2.   The second command creates another collection with the duplicates filtered out.  The Compare-Object cmdlet will first find items that are diffe

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.