Skip to main content

PowerShell Switch Parameter

One of the things that I’ve noticed in the PowerShell cmdlets are parameters without values.  These switches alter the way that the cmdlet functions without providing any input.  This is the switch parameter functionality.  Here is how it works. 

When you declare a parameter as a switch parameter, its value is set to $False.  Using what ever logic you like, you can test to see if the condition became $True.  That means the user executed the function and specified the switch.  Let’s look at a simple example:

function Test1 ([Int32]$Value,[switch]$Add5){
if ($Add5 -eq $True) {$Value += 5}
Write-Host $Value
}





In the function Test1, we have two values, a number and the switch parameter called $Add5.  This function is simple.  You provide it a number and it displays the number.  If you add the –Add5 parameter, it adds 5 to the number you provided.  Here is an example:





PS C:\Users\Jason> test1 5

5


PS C:\Users\Jason>








In the above example, we executed the script with the value of 5.  The result was 5.










PS C:\Users\Jason> test1 5 -Add5

10


PS C:\Users\Jason>










In this example, we included the –Add5 switch parameter.  In our code, we stipulated that if this parameter is $True, the we add 5 to the $Value that we gave the function.





The switch parameter functionality is good to use when you need to have a Boolean value as a parameter.

Comments

Unknown said…
it's easy to understand. Nice post

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.

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 Management Double click User Account Management C...