Skip to main content

How to Splat a Value with Multiple Arguments

Tonight I came upon a little different problem than usual.  Normally about this time of the night (9:00 PM in a different time zone than normal) I begin making all kinds of interesting logic errors.  Not tonight.  This evening I needed to splat a value with multiple arguments.  Yes, I know.  When I’m on these long business trips I can be absolutely boring.  I’m back home again in Indiana, and it is not the interesting part of the state.  That would be Brown County State Park.  No wilderness hiking this week. Back on topic, splatting allows you to provide a list of parameters and values to a PowerShell cmdlet in an organized way that prevents horizontal scrolling.  Best of all, no use of the back tick character. 

In this example, I am looking at splatting the Property parameter of Get-CIMInstance  here is the help file for this parameter.

PS C:\> Get-help Get-CimInstance -Parameter Property


-Property <String[]>

    Specifies a set of instance properties to retrieve.


    Use this parameter when you need to reduce the size of the object returned, either in memory or over the network.


    The object returned always has key properties populated, irrespective of the set of properties listed by the

    Property parameter. Other properties of the class are present but they are not populated.


    Required?                    false

    Position?                    named

    Default value               

    Accept pipeline input?       True (ByPropertyName)

    Accept wildcard characters?  false

We can see that this property accepts multiple values.  Take a look at –Property <String[ ]>.  Those [ ] square brackets tells us that we can provide multiple values separated by commas.  I’ve never actually tried to splat more than 1 value per parameter so this took a few attempts to get it right.  Here we go!

   $Splat = @{

        'ClassName' = 'Win32_NetworkAdapterConfiguration'

        'Property' =Description’,IPAddress’,IPSubnet’   


    Get-CimInstance @Splat


When you need to splat a parameter with multiple arguments, just make sure that each argument is encapsulated in its’ own set of quotes, then separate with a comma.  If you need to, press enter after a comma and add more arguments on the next line.  Again, a great way to avoid horizontal scrolling.

Time for bed.  I’ve got to teach Windows 8.1 in the morning.  Happy scripting!!!


Popular posts from this blog

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.

How to force a DNS zone to replicate

For many implementations of DNS in a Windows environment, DNS is configured as being Active Directory integrated.  In other words, the DNS zone information is actually stored as a partition in the active directory database.  When Active Directory replicates, the zone data transfers.  For standard DNS deployments, the data is stored in a file.  You have to configure zone transfers manually in the DNS console.   The question in class was how to initiate replication manually.  Once you have properly configured a Primary and secondary DNS server and configured the Primary server to allow zone transfers, you can manually initiate a zone transfer.   Below you can see our test environment.  The image is of to RDP sessions to two different servers.  The DNS console on the left is the primary.  You can see and entry for Test2 that is not in the secondary database.  The servers are named NYC-DC2 (Primary DNS) and NYC-DC1 (Secondary DNS).  The DNS zone is named . On the se

Disable SMB signing

It never fails.  Once ever couple of months I have a delegate in my class that has to keep a Windows NT4 box running.  There is nothing wrong with that.  Many applications build on Windows NT4 are solid.  Why upgrade and incur cost when no upgrade is really required?  That is generally the reason why Windows NT4 is being used.  Another reason is the vender went out of business, but the application that is required is really good and paid for. Two things to take note of.  If these Windows NT4 clients are going to be authenticating on a Windows Sever 2008 DC, then you may have a problem.  For WinNT 4.0 SP2 and earlier, SMB signing was not supported.  For WinNT4.0 SP3 and earlier, secure channel was not supported. SMB signing helps to prevent Man-in-the-middle attacks.  To open GPMC, click Start , click Run , type gpmc.msc , and then click OK . In the console tree, right-click Default Domain Controllers Policy in Domains\ Current Domain Name \Group Policy objects\Default Domain Co