This months meeting is the first of two looking at the new PowerShell functionality in Windows Server 8. Yes, there is so much it will take two sessions!
When: Tuesday, Apr 24, 2012 7:30 PM (BST)
This is the first of two...
I have seen a few interesting variations on using where-object during the games. This is normally aliased to where. You can use ? if you are fanatical about aliases but to me your PowerShell starts to become unreadable if its heavily aliased. Consider get-process. It returns a set of process...
Second event is to find running services that can be stopped
I thought I’d publish a series on how I would go about solving these plus some comments and observations on the submitted scripts.
First event of the games
The beginners section of the scripting games can be often answered with one pipeline of PowerShell.
Notice that I stated one pipeline not one line
Since the early days of PowerShell there has been an almost mystical reverence paid to the concept of the “one-liner” ie...
I’m seeing a lot of scripts where code is used to perform an action that is available as a parameter on a cmdlet that is used earlier in the pipeline. Read the help file for the cmdlets you are going to use to see how you can get PowerShell to do the work for you instead you having to create...
As with previous games I’ll publish a series of comments on the games. I won’t deal with any event specific issues until the games events are all closed but there are some things coming through that while not affecting any gradings don’t make the best use of PowerShell.
We’re just about at the halfway point with 5 events available – remember there is only a week to complete an event. Deadlines start on Monday.
The overall quality of submissions from what I’ve seen so far is up on last year which is an achievement. What is staggering is that...
Jump over to http://blogs.technet.com/b/heyscriptingguy/
for event 1 in the beginners and advanced categories
A forum question asked how to find the primary name from an alias or CNAME record.
Get-WmiObject -Namespace 'root\MicrosoftDNS' -Class