As I write this, we’re close to sign-off on the outline of 10961A, which is a new 5-day Microsoft course on PowerShell v3. I sat down yesterday and starting doing some detailed-level design work on the proposed Module 9, which will cover PowerShell Remoting.
I love Remoting (and yes, I capitalize the “R” when referring to the specific feature, much as I would for Workflow). And although I’ve taught Remoting over and over and over since it was introduced in v2, although with this course I’m trying something a bit new.
My company has been contracted by Microsoft to design and author Microsoft Official Curriculum (MOC) course 10961A, Automating Administration with Windows PowerShell v3. While there is no announced release date I can share, I did want to share some of the experience.
As I write this, 10961A’s proposed outline is going through several review cycles. In the meantime, I wanted to sit down and start doing some detail-level design on some of the more complex labs in the course - the most complex of which is a proposed Module 10, consisting of little more than a big, 2-hour lab where you write a script to provision a newly installed Server Core computer.
I’ve written previously about my frustration with reporting in PowerShell - how I see admins struggle with ugly, low-level COM code to manipulate Excel spreadsheets, just so they can get nice-looking reports with a degree of automation.
Enough.
The right thing to do is put your data in SQL Server, and use SQL Server Reporting Services to generate awesome looking reports, complete with charts and graphs. With the right setup, you can completely automate data collection, report generation, and delivery.
So, as you may know, I have an ongoing hobby project called _Creating HTML Reports in PowerShell. _I’m working on an update for next year, and one of the things I’ve been looking at are embedded charts within the report.
Problem is, I don’t know what people would actually chart. Now… I’m going to ask you for ideas, but you need to read this whole post before you go popping a comment in.
A long time ago… about a year, in fact… Jason Helmick and I started talking about a community-owned PowerShell “certification.” It went nowhere. Well, not very far. Some background on exams: Microsoft, in my opinion, will never do a PowerShell cert. I say this having been part owner of a company that did outsourced exam development for the company. The deal is that Microsoft tries to certify _job tasks, _not _tools. _Nobody (well, maybe me) wakes up thinking, “gonna do me some PowerShell today.” No, PowerShell is the means to an end: “gonna automate me some user creation today” is more likely. And Microsoft tries to certify that end. PowerShell’s an important tool, and it already shows up on certification exams here and there. For the most part, I agree with Microsoft’s reasoning, there. The argument can be summarized as saying “bosses don’t hire IT pros based on their ability to operate a low-level tool, they hire them to perform job tasks, which encompasses the tool.” Except that, in the case of PowerShell, I think it’d be tremendously useful for an employer to use PowerShell expertise as a discriminating factor in hiring. I mean, “someone who can automate stuff” is more valuable than “someone who can only do stuff manually,” in any situation. So “PowerShell Verified” was intended to be a way for someone to prove - at least to themselves - that they’ve taken their PowerShell skills _to the minimum level necessary to be an effective automator. _Not a guru. Not an expert. Not Poshoholic. _Minimally effective, _who could then grow from there with experience. So that’s what I’m going to put together. I want to explain why I’m not using the word “Certification,” though. In my mind, certifications come from, mainly, first-parties like Microsoft. Microsoft has to jump through a lot of hoops to make sure their exam content is accurate, legally defensible, blah blah blah. They worry about security, brain dumps, and other stuff that diminishes the value of the certification. I don’t have that kind of bandwidth or their resources, so in many ways my little program will be less effective than a “real” certification. Plus, few bosses will give a rat’s patooty what that Don Jones guy said about your skillz (I can’t even convince bosses to buy you guys 12-core 64GB workstations for your desk). So my “Verified” program is going to be _low stakes, _meaning you take it to prove something to _
yourself
_. Here’s how this is going to go.
To cap off the 2013 PowerShell Summit the PowerShell Team is going to host a half day Windows PowerShell scenario walkthrough. This is designed to not only familiarize folks with specific PowerShell features, but also to help the team see how you interact with these features.
The event will take place on April 24 from 1pm - 5pm. Â During this time we will collectively solve a problem from the ground up using many of the new features in Windows PowerShell 3.
As we’ve been finalizing our speaker and session collection, we’ve been able to release a small block of Summit tickets into the general admission pool. Also, the end of October saw the expiration of a set-aside block for PowerShell MVPs, releasing that block’s unsold tickets back into the general admission pool as well.
As it stands, the G.A. pool now has 57 tickets, of which we’ve sold 24. That leaves 33 tickets left for the April 22-24 event at Microsoft’s corporate headquarters in Redmond, WA.
Idera’s gone and made PowerShell Plus free. Given that it’s been updated to support PowerShell v3, this will probably become many folks’ go-to editor (PowerGUI, the former champ, is more or less out of development and hasn’t been updated for v3).
Idera says:
“Idera is dedicated to providing products that help our customers and community members be successful in their jobs,” said Rick Pleczko, CEO of Idera. “PowerShell Plus is a proven and essential productivity tool so we wanted to get it into the hands of IT professionals everywhere.
One of the ballyhooed new features in PowerShell v3 is the new “simplified” syntax for Where-Object and ForEach-Object. I’m going to focus on the former for this article. In essence, instead of doing this:
Get-Service | Where-Object { $_.Status -eq 'Running' } You can now do this also:
Get-Service | Where Status -eq Running Last week, I had the opportunity to include this new syntax in a class I was teaching - mainly to beginners - and I came away with mixed feelings.
For more than 200 weeks now (there’s an episode a week), Jon Walz and Hal Rottenberg have been bringing us the PowerScripting Podcast. It’s become an almost official “voice” of and for the PowerShell community. In it, the two don’t focus much on technical tips or anything like that. Instead, the highlight is a weekly interview with a mover and shaker in the PowerShell community. For me, they put a face on the community.