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

Determine which Domain Controller a client is connected to with PowerShell

When a Windows client comes online, it must find a domain controller to bind to.  Either through a static configuration or DHCP, the client will request a list of all Domain Controllers in the domain from a DNS server.  Once the list is received, the client will randomly go through the list to find a DC that will respond.  Once the client has authenticated itself with the DC, the DC will transmit the site information to the client.  The site information will contain the site name, the subnet(s) associated with that site, and any domain controllers in that site.  The client will then take a look at it’s own IP address to determine which site it is in.  From the list of DCs in the same site, it will attempt to bind to one of those DCs to receive it’s Group Policies.You can use PowerShell and WMI to locate the domain controller that a client is connected to.Get-WMIObject Win32_NTDomainLook for the DomainControllerName property.

Test to see what that data type of a value is in PowerShell

PowerShell has a comparison operator called –is.  The –is operator simply response True or False when you use it to verify the data type of a value.  The valid data types in PowerShell are:
[string]    Fixed-length string of Unicode characters
[char]      A Unicode 16-bit character
[byte]      An 8-bit unsigned character
[int]       32-bit signed integer
[long]      64-bit signed integer
[bool]      Boolean True/False value
[decimal]   A 128-bit decimal value
[single]    Single-precision 32-bit floating point number
[double]    Double-precision 64-bit floating point number
[DateTime]  Date and Time
[xml]       Xml object
[array]     An array of values
[hashtable] Hashtable object

Below is a script that will use –is to test some values.
$String="Hello"$Boolean=$True$Int=15Write-Host"Test for string"$String-is [String] $Boolean-is [String] $Int-is [String] Write-Host" "Write-Host"Test for Boolean"…

Where did a User’s Account Get Locked Out?

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 ManagementDouble click User Account ManagementCheck Configure the f…