Skip to main content

ByValue for Generic Objects

This is post 4 of 7 in this series.

Some cmdlets are designed to work with any object.  Take a look at the –InputObject parameter of Sort-Object.

-InputObject []
    Specifies the objects to sort.
   
    When you use the InputObject parameter to submit a collection of items, Sort-Object
    receives one object that represents the collection. Because one object cannot be
    sorted, Sort-Object returns the entire collection unchanged.
   
    To sort objects, pipe them to Sort-Object.
   
    Required?                    false
    Position?                    named
    Default value                none
    Accept pipeline input?       true (ByValue)
    Accept wildcard characters?  false

Whenever you see a parameter accepting objects of type Object or PSObject, then you know that this cmdlet can handle anything. Let’s take a look at the results of Get-SMBShare without using Sort-Object

PS C:\> Get-SmbShare

Name   ScopeName Path                              Description   
----   --------- ----                              -----------   
ADMIN$ *         C:\WINDOWS                        Remote Admin  
C$     *         C:\                               Default share 
D$     *         D:\                               Default share 
E$     *         E:\                               Default share 
IPC$   *                                           Remote IPC    
print$ *         C:\WINDOWS\system32\spool\drivers Printer Drivers

Just by looking at it, the cmdlet sends the objects into the pipeline sorted alphabetically on the Name property.  Now let’s pipe it to Sort-Object.

PS C:\> Get-SmbShare | Sort-Object

Name   ScopeName Path                              Description   
----   --------- ----                              -----------   
ADMIN$ *         C:\WINDOWS                        Remote Admin  
C$     *         C:\                               Default share 
D$     *         D:\                               Default share 
E$     *         E:\                               Default share 
IPC$   *                                           Remote IPC    
print$ *         C:\WINDOWS\system32\spool\drivers Printer Drivers

The results are the same.  Well, that was useful.  The thing that we forgot to do was to tell Sort-Object how to sort our objects.

PS C:\> Get-SmbShare | Sort-Object -Property Description

Name   ScopeName Path                              Description   
----   --------- ----                              -----------   
C$     *         C:\                               Default share 
D$     *         D:\                               Default share 
E$     *         E:\                               Default share 
print$ *         C:\WINDOWS\system32\spool\drivers Printer Drivers
ADMIN$ *         C:\WINDOWS                        Remote Admin  
IPC$   *                                           Remote IPC   


For this cmdlet to do anything, you need to give it some instructions.  In this case, which property to sort on. Sort-Object has been around since PowerShell v1.0.  Get-SMBShare was introduced in PowerShell v3.0, but only if you are running Windows 8 or newer.  In other words, the author of the Sort-Object cmdlet had no idea that the cmdlet Get-SMBShare would ever be created.  The author simple coded the Sort-Object cmdlet to accept all objects. Because of this, we can continue to sort objects evening with PowerShell v5.1.

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