New Way to add Note Properties with PowerShell V3

For those of you who have taken my PowerShell V2 class probably remember the step-by-step exercise that I took you through to help you build a custom object. In PowerShell V3, we can create a new NoteProperty with a smaller amount of code. Below is code that creates an object with a single note property.

$Obj = New-Object -TypeName PSObject

$Obj | Add-Member -MemberType NoteProperty -Name "Value1" -Value 10
Using the Add-Member cmdlet, we declare the member type that we are adding “NoteProperty”. Then we provide it with a name and a value. In PowerShell V3, two new parameters were added to the Add-Member cmdlet. They are –NotePropertyName and –NotePropertyValue. Below is the same object created with this new method.

$Obj = New-Object -TypeName PSObject

$Obj | Add-Member -NotePropertyName "Value1" -NotePropertyValue 10

If your code will be running on clients or servers using PowerShell V2, do not use this new method. Take a look at the screen shot below.

You can see that the script successfully executes in PowerShell V3. When I switch the shell to the V2 engine and then executed the code, PowerShell V2 hit a run time error because its version of Add-Member does not have a parameter for ‘NotePropertyName’.
Just one of the little hidden tricks inside of PoSH V3. As always, code for the lowest level of PowerShell that your code will execute on.

Comments

Sticky Key problem between Windows Server 2012 and LogMeIn

This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this. First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .

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...

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.

Jason Yoder, MCT

Search This Blog