The first topic we are going to cover is something called “Advanced Functions”. This topic has been covered many times before by other people. I wanted to put my spin on this.

When you use Advanced Functions you add the following line to the first line of your function or script.

[CmdletBinding()]

This line, when used in Windows PowerShell 2.0 scripts or functions, gives you the following cmdlets among other things.

• Write-Verbose
• Write-Debug

How does this help me document you ask?

I use Write-Verbose for everything I am doing in a script and function. From assigning variables, changing values, switching in and out of functions, I document EVERYTHING. You can put anything you want in Write-Verbose.

One cool trick I do is the following where it gives you the name of the script you are running when you run it.

Write-Verbose -Message "Running Script: $MyInvocation.MyCommand"

I also add things to my scripts and functions so that when other people run the script, they can see who wrote it and other information.

Write-Verbose -Message "Running Script: $MyInvocation.MyCommand"
Write-Verbose -Message "Author: Matt Johnson - email@address"
Write-Verbose -Message "Script Version: 1.0"
Write-Verbose -Message "Join the SE Michigan PowerShell Script Club"
Write-Verbose -Message "http://www.michiganpowershell.com"

Now when you run your script or function –verbose you get the added information you placed in your script. The possibilities are endless.

I also use Write-Debug but not as frequently. I use those lines to go into further detail on what I am doing. Something that people running my scripts may not want to see if they want more info.

I encourage you to add the [CmdletBinding()] statement to your PowerShell 2.0 scripts and functions and play around with those two statements.

Up Next: Inline Help

I am non-discriminatory on what I listen to as long as it is good content. I have a decent drive to work and use the opportunity to learn new things.

Below is my current list. Feel free to suggest more.

• Exotic Liability
• Forensic 4cast
• Hak5
• Hanselminutes
• Technet Edge
• InfoSec Daily
• Official Xbox Magazine
• OWASP Security Podcast
• Packet Pushers
• PauDotCom Security Weekly
• PowerScripting Podcast
• RunAs Radio
• SecuraBit
• Security Justice

The EXPTA {blog}: The New Exchange 2007 SP3 Password Reset Tool – Very cool feature of Exchange 2007 SP3. You are now able to force people to change their passwords on login to OWA. This will replace some work arounds that I have implemented. Note this isn’t available in Exchange 2010.

iOS 4: Exchange Mail, Contacts, or Calendars may not sync after update – What? My iPhone won’t sync Exchange and is killing my Exchange server? My iPhone isn’t evil! Or is it?

I sent in only 3 scripts as life got in the way. Too much school and working. Oh well. I did however complete 95% of each script but wasn’t happy with the code so I didn’t submit them. I know I should have submitted them anyways, but oh well. This however doesn’t mean I am done working on them. I plan on posting my solutions on my blog as I get time to finish them. (Probably sometime in June.)

The good thing is that I did learn some things and remember a few others. After all, isn’t that the whole reason for the Scripting Games anyways?

1. The first thing I remembered is how cool Tee-Object is. For those of you who don’t know Tee-Object sends what you pass it to both the screen and a file. I am assuming this is based of the tee command in Unix. No matter where it is from, I am going to try to remember to add this to my bag of tricks. See my example below. I am running Get-Process and selecting the first 10. I am then passing that to Tee-Object and saving it to a file and viewing the content at the same time. Very Cool!
   
2. I learned I was making things to hard for myself. Before the Scripting Games I would use a parameter named DEBUG and an if statement to write extra information to the screen when running a script. Good news! PowerShell v2.0 has a statement you can add to your scripts to force your scripts to recognize the debug parameter. Once you add that you can use the Write-Debug cmdlet. This makes life so much easier.
3. I remembered that there are tons of different resources. Use them. I can’t stress that enough. Without those resources everything gets exponentially more difficult.

There are also some thank you’s that need to go out.

1. The Scripting Guys. I can’t even imagine how much work goes into producing an event like this. Thank you for doing this for the community.
2. Joel Bennett (Jaykul) for hosting PoshCode and the repository for posting our scripts.
3. The sponsors of the Scripting Games.
• Tech·Ed 2010 North America
• PoshCode.org
• Microsoft TechNet
• SAPIEN Technologies
• Quest Software
• /n software
• Software FX
• 101FreeTechBooks.com
• ShellTools
• Idera

Lastly, I want to thank Ed personally for allowing me to write a solution for Advanced Event 4. I can say that has been the highlight of my scripting career.

I am still working on some of the advanced scripts and hope to submit them this weekend. Today was event 4. It dealt with environment variables. Unfortunately I won’t be submitting today’s scripts as I wrote the solution for the advanced event. I was honored that the Scripting Guys allowed me to write a solution. I can only hope they ask me to do it again next year.

You can pick up the beginner event here and the advanced event here.

I am working on a few blog posts to hopefully post next week. Until then you are going to have to suffer through some link posts.

Happy Scripting!

Happy Scripting!

You can download this function here.

Quick and Simple! Enjoy!

function Test-IsValidIP{
    param (
        [string]$ipAddress
    )

    #Regex Query
    $regexQuery = "^([1-9]|[1-9][0-9]|1[0-9][0-9]`
        |2[0-4][0-9]|25[0-5])(\.([0-9]|[1-9][0-9]`
        |1[0-9][0-9]|2[0-4][0-9]|25[0-5])){3}$"

    if ($ipAddress -match $regexQuery){
        return($true)
    } else {
        return($false)
    }
}

The scripting games start on April 26th and go to May 7th. I know I am encouraging everyone in the SE Michigan PowerShell Script club to participate and hopefully you do to!

There are 10 events in both an beginner and advanced categories. This year there are two languages that the scripts can be written in. Those are PowerShell and VBScript. (I heard that this is the last year for VBScript. Boohoo! VBScript will always have a place in my heart but change is good. And besides PowerShell is awesome!) These events encompass tasks that can help you with your day to day job. Looking at the 2010 Scripting Games Study guide gives us a hint at what the events might entail. From working with text files and folders to using WMI information I am sure that everyone will find this to be fun and challenging.

When you are done writing your script, you can post it up along with everyone else's submission on the special Scripting Games section of the PoshCode.org website. That site is at http://2010sg.poshcode.org. Very cool of PoshCode to do this if I do say so.

At the end of each event scripting experts will provide commentary on how they tackled the script and their solution. This is a great opportunity to learn from some of the best in the scripting community. You should note however that there are almost always many ways to solve a problem, but what some of the experts do is amazing in how well their scripts are written.

So with all that being said, I urge you to compete. Oh I forgot to mention there will be prizes? According to the FAQ they will be having 11 drawings, which amounts to one drawing per day and a grand prize. All you have to do to be eligible is to submit a script for the event! Now how easy is that? And who doesn’t love prizes? I know I do.

What do you do next? Well there are a few things you can do to get prepared.

1. Register to compete! You can do this by going to http://2010sg.poshcode.org. Make sure you do this so you can hit the round running on April 26th, 2010.
2. Read the Frequently Asked Questions. You can find them at http://bit.ly/2010sgdetails
3. Use the study guide the Scripting Guys so graciously provided at http://bitl.ly/2010sgstudyguide.
4. Read the Scripting Guys Blog and follow along as the Scripting Wife learns PowerShell! Their blog is at http://blogs.technet.com/heyscriptingguy/default.aspx
5. If you have your own website or blog, put the 2010 Scripting Games badge on your site so that everyone knows you are competing and you can help bring in more people! You can get that at http://bit.ly/2010sggrabbadge.
6. If you use twitter or Facebook, make sure you add the Twibbon for your profile picture! You can get the twibbon at http://twibbon.com/join/2010-scripting-games.

I hope to see you on the “Scripting Field”.

Happy Scripting!

The following is a RegEx string to validate input in the format of hh:mm:ss.

[01][0-9]:[0-6][0-9]:[0-6][0-9]

We can use a simple if statement to validate the time as seen below

$time = "22:33:22"

if ($time -match "[01][0-9]:[0-6][0-9]:[0-6][0-9]"){
    Write-Host $true
} else{
    Write-Host $false
}

Pat Richard pointed out that we can do this with a few less lines of code, so you can choose what way you want to do this. He used the –match switch against the variable itself. Here is what he suggested:

$time = "22:33:22"
$time -match "[01][0-9]:[0-6][0-9]:[0-6][0-9]"

With PowerShell 2.0, we can validate it when it is entered as a parameter by adding the following lines into your param() statement replacing the variable $userTime with the name of your variable.

[ValidatePattern("[01][0-9]:[0-6][0-9]:[0-6][0-9]")]
[string]$userTime

The following function validates time in the format of hh:mm:ss. It can also be downloaded here.

function Test-IsValidTime {
    <#
    .SYNOPSIS
        Checks to see if value entered is in valid format.

    .DESCRIPTION
        This function tests to see if the date entered in hh:mm:ss format is a valid time.

    .PARAMETER  time
        Time entered in format of hh:mm:ss.

    .EXAMPLE
        PS C:\> Test-IsValidTime -time '12:34:56'

    .INPUTS
        System.String

    .OUTPUTS
        System.Boolean

    .NOTES
        This function was written by Matt Johnson of the SE Michigan PowerShell Script Club.

    .LINK
        http://www.mwjcomputing.com/blog/

    .LINK
        http://www.michiganpowershell.com/

    #>

    param (
    [string]$time
    )

    if ($time -match "[01][0-9]:[0-6][0-9]:[0-6][0-9]"){
        return $true
    } else{
        return $false
    }

} #End Function Test-IsValidTime

Happy Scripting!

You can download this script here.

Happy Scripting!

######################################################
# Script Name: set-powershelldemo.ps1
# Written By: Matt Johnson - powershell@mwjcomputing.com
# Revision Date: 4/12/2010
# Version: 2.0
# Version History:
#  - 1.0: Inital Script
#  - 2.0: Added host info switch and display
# Description: This script sets the window for the demo.
# Command Line: ./set-powershelldemo.ps1
# Example 1: ./set-powershelldemo.ps1
# Example 2: ./set-powershelldemo.ps1 -displayHost
######################################################
param(
    [switch]$displayHost
)

# Get UserInterface Object
$userInterface = (Get-Host).UI.RawUI

# Set Window Title
$userInterface.WindowTitle = "MWJ Computing PowerShell Demo"

# Set Window Size
$windowSize = $userInterface.WindowSize
$windowSize.Width = 120
$windowSize.Height = 50
$userInterface.WindowSize = $windowSize

# Check for admin script
$wid=[System.Security.Principal.WindowsIdentity]::GetCurrent()
$prp=new-object System.Security.Principal.WindowsPrincipal($wid)
$adm=[System.Security.Principal.WindowsBuiltInRole]::Administrator
$IsAdmin=$prp.IsInRole($adm)

# Check to see if admin, if is change background to red.
if ($IsAdmin){
    (get-host).UI.RawUI.Backgroundcolor="DarkRed"
}

# Set Location to c:\fso
Set-Location -path 'C:\fso'

# Clear Screen
Clear

# Display Welcome Message
Write-Host -object "Welcome to the MWJ Computing PowerShell Demo."`
    -foregroundcolor Yellow
Write-Host -object `
    "For more information, please visit http://www.mwjcomputing.com/blog/." `
    -foregroundcolor Yellow
Write-Host -object "Happy Scripting!" -foregroundcolor Yellow

# Check for DiplayHost switch.
if ($displayHost){
    Write-Host -object ""
    Write-Host -object "UserName: $env:USERNAME" `
        -foregroundcolor Yellow
    Write-Host -object "HostName: $env:COMPUTERNAME" 1
        -foregroundcolor Yellow
    Write-Host -object "DomainName: $env:USERDNSDOMAIN" 1
        -foregroundcolor Yellow
    Write-Host -object "Date: $(Get-Date)" -foregroundcolor Yellow
    Write-Host -object "Execution Policy: $(Get-ExecutionPolicy)" `
        -foregroundcolor Yellow
}