Jason Yoder, MCT

I have always said that one of the greatest benefit to teaching PowerShell (and Windows) is that different people bring different ideas to the table.  Things get fun for me when someone looks at what we are doing from a different angle and asked an interesting question. This week’s class in Fort Wayne produced one of those questions.  We were looking at some of the options that are available to use with creating variables with the New-Variable cmdlet.  In particular, we were looking at constants.  Let’s build one. PS C:\> New-Variable -Name Test1 -Value ([Bool]$True) -Option Constant Now let’s take a look at the variable object. Name        : Test1 Description : Value       : True Visibility  : Public Module      : ModuleName  : Options     : Constant Attributes  : {} We can see from the Options property that we have created a constant.  We are going to attempt to change that value of this constant to FALSE. PS C:\> Set-Variable -Name Test

Often while teaching PowerShell, we get into a discussion about how someone, usually me, types this: Get-Help Get-Date Instead of Get-Help –Name Get-Date PowerShell parameters utilize positioning.  Good authors of cmdlets will determine which parameter will be the most frequently used and put that parameter in the first position.  That means if the user types a cmdlet, they can immediately provide the data for that parameter without calling the parameter name.  Take a look at the –Name parameter of Get-Help -Name     Gets help about the specified command or concept. Enter the name of a cmdlet, function, provider,     script, or workflow, such as `Get-Member`, a conceptual topic name, such as `about_Objects`, or an     alias, such as `ls`. Wildcard characters are permitted in cmdlet and provider names, but you     cannot use wildcard characters to find the names of function help and script help topics.         To get help for a script that is not located i

How to start a PowerShell Script from a Batch File In last week’s PowerShell class in Phoenix, we had a last minute question.  It involved trying to simplify the launching of a PowerShell script for users.  Having end users working with PowerShell has long been a cumbersome task.  End users like a GUI.  We can put a GUI interface on top of our code, but it is difficult to do manually or you need a third party solution.  When you build a GUI, it also takes an additional skill set that most IT Pros do not have. We decided to go with a batch file.  Yes, I know.  Old tech but we will give it new life.  Here is our test code for this project. We saved this file as c:\ps\Test1.ps1. Write-Host "I work!!!" -BackgroundColor DarkMagenta Yes, I know.  Not exactly exciting.  The purpose of this is to get it to launch with a batch file. We looked at the PowerShell.exe Command-Line Help (https://docs.microsoft.com/en-us/powershell/scripting/core-powershell/console/

Here is one from this week’s PowerShell class. We just finished a lesson on methods and I passed on “The first rule of Computer Science” to my class that one of my professions, Dan Matthews, passed on to me.  It simply states “Never re-invent the wheel”.  With that, we started to talk about the value of methods.  The question popped us as to which version of .Net is PowerShell using and how to select a different version?  Well, here is how to determine the current installed versions of .Net:   PS C:\> Get-Childitem "HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP"     Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP Name                           Property                                                                                                                             ----                           --------                                                                                                                         

I’m currently in the middle of writing version 2 of my Security+ learning engine.  Some of you from last weeks Security+ class know that I have been developing a tool using SAPIEN PowerShell Studio to help you with the massive amount of terminology that you need to know for the Sec+ exam.  You also remember that I was putting in some safe guards to help protect the application from piracy.  I’m going to share one of those safeguards.  Here is a current view of version 2 of the product. What I want to do is to disable the ability to copy the questions and answers to the clipboard.  Here is how you do it.  In the Designer view, click on the object that you want to protect.  In this case, I am clicking the text box that contains the questions.  In the Properties dialog, set the value for ShortcutsEnabled to False .  This turns off the right clicking capability of the object. While talking about Active Directory Rights Management in the past, I’ve been hit hard that I

This week we had a little surprise when we were working on the auditing component of our Security+ class here in North Carolina.  The labs this week are built in Azure and I gave each one a public IP address.  On Wednesday afternoon with the VMs online since Monday, we took a look at the failure login attempts.  We got a big surprise with over 11,000 bad logon attempts.  We then started the second set of VMs fresh.  It took about 10 minutes until we started to see the attempts to access those VMs.  If this does not tell you we operate in a hostile environment, nothing will.  Here is the PowerShell code that we used and the results on the systems online for 10 minutes. Get-EventLog -LogName Security -InstanceId 4625 |     Select-Object -Property TimeGenerated ,     @{N = "AccountName" ;E = { $_ . Message . Split( "`n" ) [ 12 ]. Replace( "Account Name:" , $Null ) . Trim()}} ,     @{N = "Domain" ;E = { $_ . Message . Split( &qu