Tag Archives: Scripting

January Charlotte PowerShell User Group Meeting


Our monthly meeting will be held on January 2nd, 2014. This years Scripting Games is a team based event. What better place to find/join a team than a User Group meeting? We look forward to seeing you there.

Here is some additional information about the Winter Scripting Games:

Teams can consist of between 2 to 6 Scripters and official registration opens on Jan 2nd.

There will be a total of 4 official events for the Winter Scripting Games:

January 19th, January 26th, February 2nd, & February 9th

Check out the schedule for all the details. In addition, be sure to follow the #pshgames hashtag on twitter. There is also a list of Coaches who are blogging and tweeting helpful info and tips including this excellent preparation guide. Lastly, before you head over to the scripting games website be sure to read this Important Scripting Games Login and Operational Information post.

Scripting Games 2013 have started


The 2013 Scripting Games kicked off during the PowerShell summit.  Event 1 is open and you can submit entries up until 23:59:59 GMT on 29 April 2013.  Voting on the entries starts at at midnight on 30 April.

You can enter and you can vote on the entries.  This is a community games run by powershell.org – all are welcome.

If you haven’t entered yet there is still plenty of time to get you entry in for event 1.  Start by reviewing the information at http://powershell.org/wp/the-scripting-games/

Enjoy and good luck

Scripting Wife Comments on Beginner Event 1


Summary: The Scripting Wife reveals her impressions of 2013 Scripting Games Beginner Event 1.

Hi everyone, I want to welcome you to the 2013 Scripting Games. This year the events were designed by the Windows PowerShell community, and the games are being run by the Windows PowerShell community. It is a very exciting and important year.

OK, so at first Beginner Event 1 did not make too much sense to me, so I had to read it multiple times before it dawned on me what was going on. You see, I am not a computer guru—I am more at home with Microsoft Excel than with Windows PowerShell. But Windows PowerShell is cool, and I have come to appreciate it over the years. In fact, I have found that some tasks are actually easier to do from Windows PowerShell than from the GUI (this is especially true for me in Windows 8).

Anyway, at first when I read this event, I was thinking event logs…hmmmm…I think I need to use Get-EventLog. I looked up the Help on Get-EventLog by doing the following:

help Get-EventLog

I looked through everything, but I did not find what I needed. Then it dawned on me that just because something says it is a log, does not mean it goes into an event log. These log files are really just files with a .log extension. I can treat them like they were text files. And I know how to work with text files.

Then I decided to look at some Hey, Scripting Guy! Blog posts about working with files for storage. I came up with this list of blogs. Next I decided to look at blogs that talk about working with dates and times, and I came up with this list of blogs.

By using these resources, I was able to come up with a solution to the Beginner Event 1. I spent a couple of hours reading and reviewing as part of the event, and I thought it was a fun process. I hope you will join in the spirit of the 2013 Scripting Games. You will be glad you do!

~Scripting Wife

Use PowerShell to Copy Files and Folders to a New Location


Summary: The Scripting Wife learns about using Windows PowerShell to copy files and folders in prep for the 2013 Scripting Games.

The days seem to start early, and the evening arrives later this time of year in Charlotte, North Carolina. I am sitting on the lanai drinking a cup of English Breakfast tea, and checking my email with my Microsoft Surface RT device. In my mind, it is a perfect way to ease in to the day, and my Surface is great for stuff like checking email and sending tweets.

I hear a sort of a thump, thump, thump, rattle, rattle, rattle sound and I look up. Strangely enough, I see nothing, so I go back to reading my email. But the sound persists. I get up from my swing and go into the house. I see the source of the noise: the Scripting Wife is digging through the front closet, and she has boxes, books, and other assorted paraphernalia spread out over the vestibule floor. In situations like this, I have learned to keep my mouth shut, and to wait for a natural opening.  

“I can’t find the flippin’ book,” the Scripting Wife exclaimed without looking up.

Not sure if this is a question, a remark, or even if it was directed at me, I decide to keep quiet.

“Well are you going to help?” she asked as she stood up.

“How can I help you, my peach?” I implored.

“You can help me find my autographed copy of Don’s book.”

I wait, knowing there is more to come.

“I saw your blog post about the upcoming 2013 Scripting Games, and I need to get back into shape by writing some code,” she stated.

“You are sort of like a scripting butterfly. You go here and there in random directions looking for nectar, but you never light for very long,” I paused to catch my breath.

“But I don’t need to know how to write scripts when I have my very own script monkey. Besides I just do this for fun,” she said.

“Well, I have no idea where you put your book, but I can help you for a few minutes if you wish,” I offered.

“I saw you reading your email, and I did not want to disturb you,” she said.

“Then why all the noise?” I asked.

“Maybe I figured if you came in here, then you were no longer reading your email and I could get you to help,” she posited.

“So what do you need to do?” I asked.

“Tell me about copying files. I have a bunch of pictures on my laptop that I want to copy up to the SAN so they do not get lost,” she said.

“Grab your laptop and come out to the lanai,” I instructed.

Using Copy-Item to copy files

“To copy a file from one folder to another, what cmdlet do you think you might use?” I asked.

Copy-File,” she posited.

“Close. It is called Copy-Item,” I said.

“Oh, yeah. Now I remember,” she said.

“Open your Windows PowerShell console, and use Copy-Item to copy any file from your C:\fso folder to your C:\fsox folder,” I said.

She thought for about a second and typed the following until she had a file selected:

Copy-I<tab><space>-p<tab><space>c:\fs<tab>\<tab> 

Next she typed the following:

-d<tab><space>c:\fsox\mylog.log<enter>

The completed command is shown here:

Copy-Item -Path C:\fso\20110314.log -Destination c:\fsox\mylog.log

When she pressed ENTER, an error arose. The command and the error message are shown in the following image.

Image of error message

“Well, that did not work,” she said, “I guess I do need to go find Don’s book after all.”

“No, I wanted to show you what happens if the destination folder does not exist,” I said.

“How can I avoid that problem?”

“You can use the Test-Path cmdlet. Type Test-Path and supply the path to the folder,” I said.

She typed the following into the Windows PowerShell console:

Test-P<tab><space>C:\fsox

The command is shown here:

Test-Path c:\fsox

The command and the output from the command are shown in the image that follows.

Image of command output

“So the command says False. I guess that means the folder does not exist?” she asked.

“Yep. That is right. Now use the MD command and give it a path so that you create the new C:\fsox folder,” I said.

She typed the following:

MD<space>C:\fsox<enter>

The command is shown here.

md c:\fsox

The command and the output from the command are shown in the image that follows.

Image of command output

“Now use the Up arrow and retrieve your previous Copy-Item command,” I said.

The Scripting Wife pressed the Up arrow a few times until the following command appeared:

Copy-Item -Path C:\fso\20110314.log -Destination c:\fsox\mylog.log

When the command appeared in the Windows PowerShell console window, she pressed ENTER to run the command. Nothing came back.

Easily copy multiple files by using Copy-Item

“That is OK, but I specifically want to copy my pictures, and I do not want to type a bunch of names. So how can I make Windows PowerShell copy my pictures for me?” she asked.

“To do that, use the Filter parameter and specify .jpg, which is the extension you use for your pictures. You will also need to specify the Recurse parameter,” I said.

She typed the following:

Copy-i<tab><space> -p<tab><space>c:\fso<space>-fi<tab><space>*.jpg<space> -d<tab><space> c:\fsox<space>-r<tab><enter>

The command is shown here:

Copy-Item -Path C:\fso -Filter *.jpg -Destination c:\fsox –Recurse

The newly copied files are shown in the following image.

Image of menu

“Cool,” she said as she bounded through the front door.

Scripting Games Prep Week will continue tomorrow when I will talk about Windows Management Instrumentation and obtaining basic computer information.

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at [email protected], or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.

Ed Wilson, Microsoft Scripting Guy 

Beginner Practice for 2013 Scripting Games


Microsoft Scripting Guy, Ed Wilson, is here.  Today we have Don Jones, from www.powershell.org and a practice event for the Beginner category of the 2013 Scripting Games.

Scripting Games logo

This is a practice event. You will not submit this event to the actual Scripting Games, and no official judging will be available for this event. If you would like to post your solution for peer review, please do so in The Scripting Games forum on PowerShell.org or in another venue of your choosing. It is your responsibility to solicit peer reviews from the community; no judges or moderators are scheduled to provide reviews for this practice event.

Image of Dr. Scripto

Dr. Scripto is in a quandary. On one hand, he has a request to calculate the current uptime for a set of servers in his domain. On the other hand, he’d love to go see the new Michael Bay movie. Query uptime, or watch exploding robots?

Easy choice. While Dr. Scripto enjoys a wonderful motion picture, you get to figure out the uptime thing.

You’ve been given a list of server names and IP addresses in a text file, C:\Servers.txt. It contains one name or IP address per line. You need to write a command that displays each computer’s name (even if you were given an IP address, you must display the name) and the number of hours, minutes, and seconds the computer has been online since its last restart. Your output should consist of four properties with hours, minutes, and seconds broken out into their own individual properties.

You can be assured that all of the servers in the list are in the domain, and that you’ll have authority to query them. They’re all running Windows Server 2008 R2 or later, and they all have Windows PowerShell 3.0 installed. There are no firewalls or other blockages between you and those computers, and your command can assume that all of the servers are online and reachable. (If one isn’t, an appropriate error message should display, but it need not contain the failed computer name or IP address.)

Your command should be as concise as possible—a one-liner, if you think you can do it, although you’re welcome to use full command and parameter names for better readability. The output of whatever command you write must enable someone to pipe the output to a CSV file, XML file, or HTML file, if they so choose; but you do not need to provide those functions in the command you write.

Hint   There’s a commonly-used WMI class that contains the most recent computer start-up time. There are also event log entries related to total uptime.

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at [email protected], or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.

Ed Wilson, Microsoft Scripting Guy 

2013 Scripting Games Competitor’s Guide


Summary: The 2013 Windows PowerShell Scripting Games Competitor’s Guide is posted today.

Microsoft Scripting Guy, Ed Wilson, is here. Don Jones from PowerShell.org is back with us today with the 2013 Scripting Games Competitor’s Guide.

Scripting Games logo

 

Take it away, Don…

Welcome to the 2013 Scripting Games, now managed by PowerShell.org! This guide is designed to help you understand how the games work and what you can expect.

Important   See yesterday’s blog, 2013 Scripting Games Start April 22!, for information about the events, tracks, voting, and prizes.

Register

First up, you’ll need to register for the Games by logging on to http://scriptinggames.org/. Note that there is no “www” on this URL. When you register, you’ll be asked to select a track. This is a one-time decision, and you may choose from:

  • None: You don’t want to compete, but you do want to grade other folks’ work by voting.
  • Beginner: You’ll be able to vote on all events, but you will be able to submit only one entry per event in the Beginner track.
  • Advanced: You’ll be able to vote on all events, but you will be able to submit only one entry per event in the Advanced track.

Caution   We ask that you not include any personally identifiable information in your entries. This includes your name, email address, or other contact information.

Games guidelines

Now, these are just ideas for you to consider. They’re not rules, and our judges won’t universally agree on every one of the ideas. So don’t think of this as a magic checklist that will make you win. You don’t even need to force yourself to do all of these things—but keep them in mind.

  • We love to see error handling, especially in the Advanced events. But we don’t like error suppression. That is, if an error occurs, we should see the error, or you should be doing something about it like logging it or displaying an alternate message.
    The exception: it’s okay to suppress an error that means “everything is going fine.” For example, you try to delete a file that doesn’t exist, and you get an error message. Well, that’s fine. At the end of the day, the file isn’t there, and that’s what you wanted. If you do choose to handle an error, make sure you’re doing so intelligently. Don’t wrap your entire code in a big Try{} block. Only wrap the commands that you anticipate will have an error, and Catch{} (and handle) that error.
  • We hate seeing people do more work than is necessary. For example, you shouldn’t ever prompt the user for a missing parameter. Use the Parameter() decorator in Windows PowerShell to mark the parameter as mandatory.
  • We love self-documenting scripts. That doesn’t just mean comments, although those are pretty awesome, too—especially comment-based Help. Using stuff like full command names and full parameter names (and no positional parameters) makes a script more self-documenting.
    Other examples are less obvious. Here’s one: if you’re accepting input arguments, do so via declared, named parameters, not by using the $args collection. $ComputerName (a named parameter) is a lot more meaningful than $args.
  • We hate inconsistency. In whatever you write, try to be consistent with what’s already in Windows PowerShell. A parameter named ComputerName is great; a parameter named ComputerNameS is not great. Nothing else in Windows PowerShell uses the plural, so you shouldn’t either.
  • We love scripts and commands that output objects and not formatted text. That means you shouldn’t embed a Format cmdlet in your script, nor should you use Write-Host in most cases. Exceptions are made by the name of your script or command; for example, we’d expect a command named Show-Info to show information on the screen, implying Write-Host is being used. A command named Get-Something, on the other hand, should output unformatted objects. We’ll pipe those to a Format command ourselves if we want them formatted.
  • We hate scripts that are hard to read. With scripts (as opposed to one-liners), focus on neat formatting. Avoid the backtick (`) as a line continuation trick because that little bugger is hard to see.
  • We love elegance. For example, a lot of folks think the expression “$computer cannot be reached” is easier and less complex than (“{0} cannot be reached” –f $computer)—even though these two expressions produce the same result. Both of those are prettier than ($computer + “ cannot be reached”). Just keep that in mind.
  • We hate redundancy…well, not in server farms, but definitely in script. For example, is all this really needed: Get-Service | Select-Object –Property @{n=’Name’;e={$PSItem.Name}}? Could you simply go for Get-Service | Select-Object –Property Name and get the same effect with less typing? We’re not saying this kind of thing will land you on a judges Worst list, but we know it’ll keep you off some judges Best lists.
  • We love functions that use [CmdletBinding()] and take advantage of the features it enables. For example, if you’re manually setting something like $VerbosePreference or $DebugPreference at the top of your script, you’re missing the point.
  • We hate scripts that pollute the global scope. It’s not yours. We don’t track mud into your house, don’t litter up our global scope with your variables.
    Exception: if you write a script module that politely adds global “preference” variables and then politely removes them when we unload it, that’s cool.

Don’t over obsess

In some event scenarios, we’ll give you an example of the expected output. It’s an example, not a mandatory deliverable. Basically, if you have all the right property names and the values look legitimate, you’re fine. They don’t need to be in the order we list them, and they don’t need to exhibit the exact same formatting, unless the event scenario calls out a specific requirement. In many cases, the example output is formatted to fit in a PDF file. It’s going to look different in the Windows PowerShell console, and we’re cool with that.

However, make sure that you meet the scenario requirements. If a requirement says to display a value in gigabytes, you’d better do it. Expect your Crowd Score to be pretty low if you display in bytes when the scenario explicitly asked for gigabytes.

Let’s be clear on something: if your goal going into the Games is to get on every judge’s Best list, you’re playing for the wrong reasons. If your goal is to get an amazing Crowd Score in every event, you’re probably going to be disappointed. This is a learning event.

Here’s another way to think about it: you’re going to have your script reviewed by dozens of peers, and possibly get some expert feedback from some of the biggest names in the industry. That alone is worth participating. The prizes are just icing on the cake!

DO NOT treat the previous list of guidelines as some kind of secret checklist for winning. It isn’t. They’re pretty good ideas in general, but they’re not the only good ideas. Like all rules they come with their own exceptions.

DO obsess about finding a clever, elegant, well-written solution to each problem. Knock our socks off! 

Try to not miss the point

Something different about the Games this year: You’ll notice that the only score you’ll receive is from your peers in the community—and we can’t tell them how to score you. Heck, some of them may not feel they’re even qualified to hand out scores, and a few of those might be right (more on that in a moment).

The score is nice—but it isn’t the point of the Games. The point is to think of creative approaches to real-world problems and to implement those approaches the best way you can.

Our expert judges will be picking their Best and Worst lists to highlight creativity, attention to detail, and overall sk1llz. Every judge will have different opinions, preferences, and techniques; and they’re all purely subjective. We’re not giving them any guidelines. So there’s no secret checklist for winning.

Our judges will blog about what they like and don’t like. And that is the real point of the Games: to learn.

Thanks to our presenting sponsors

Generous support from our sponsors makes the Games and all of PowerShell.org possible.
Please offer them your support and thanks.

Images of sponsor icons

GOOD LUCK!

~Don

Thank you to Don Jones and to the rest of the Windows PowerShell community for sharing this. Join me tomorrow when we will reveal two practice events for the 2013 Scripting Games.

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at [email protected], or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.

Ed Wilson, Microsoft Scripting Guy 

2013 Scripting Games Start April 22!


Summary: Announcing the Windows PowerShell 2013 Scripting Games, which begin April 22, 2013.

Microsoft Scripting Guy, Ed Wilson, is here. Don Jones is with us today from the offices of PowerShell.org. Tell us what you know about the 2013 Windows PowerShell Scripting Games, Don…

The Games are coming! With an all new software platform (kindly provided by Start-Automating.com, an organization that actually uses Windows PowerShell to power our website), we’re ready to roll. You’ll find Beginner and Advanced tracks, with some new twists.

Events and tracks

Events are open only for a limited period of time. Each event will go through four phases. Dates refer to midnight GMT of the indicated day (meaning, Feb. 2 would be “Feb. 2 at midnight GMT”). The four phases are:

  • Pending: The event is not yet open.
  • Open: You can download the event scenario (as a PDF for offline use) and submit entries. You usually get about five days to do this.
  • Review: No new entries are accepted, but everyone can vote on all events.
  • Public: No entries or votes are accepted, but anyone (logged on or not) can see the entries.

Remember, the Scripting Games are now managed by PowerShell.org, a community-owned corporation that runs the PowerShell.org website. The Games are still supported by Microsoft and The Scripting Guys, but we’re an independent organization and our actions and words do not represent Microsoft.

Here’s a bit about the tracks…

Beginner track   Consists of events where the answer is usually a one-liner, or at most, a couple of lines of code. We do not usually expect to see error handling or error suppression, extensive use of variables, and so on. We recognize that entries in the Beginner track may sometimes produce errors (like if the command can’t connect to a computer), and that’s fine. Judges will typically be less impressed with overcomplicated solutions, so keep it simple.

Advanced track   Consists of events where the answer is usually an advanced function with parameters. If you don’t know what an advanced function is, the Advanced track is not for you. We expect to see more attention to detail, and more use of built-in Windows PowerShell features.

Caution   We ask that you not include any personally identifiable information in your entries. This includes your name, email address, or other contact information.

There are several ways to win this year:

  • Every time you vote on someone’s entry (giving it a score of 1 to 5, with 1 as “bad” and 5 as “good”—whatever those terms mean to you personally), you earn one pointlet. Each pointlet serves as a prize raffle ticket.
  • You can win by being the crowd favorite! That simply means more people have given you high-scoring votes as part of your Crowd Score. These aren’t professional judges, but their opinion still matters.
  • Our professional judging panel will select their Best and Worst list for each event, and they will blog about what they liked and didn’t like. If you’re in the Best list for one or more judges, your entry will be reviewed by our mighty panel of celebrity judges, who will award First, Second, and Third places.
  • We’ll recognize the winners in each event and track, in addition to the overall winners for each track.

What does it take to impress the public and earn a high crowd score? We have no idea—it’s the public. Be creative and do the right thing.

What does it take to wind up on a judge’s Best list? Have a creative approach to the problem you’re given, and consider some of the guidelines in the next section of this guide.

Important note   “Win” does not mean “prize.” Not every recognized winner will receive a tangible prize (although we’re going to try). Every winner will have the right to use a badge on their PowerShell People profile, and we’ll announce those badges after the Games complete. (Oh, you don’t have a profile? Well, if you want to compete in the Games, there’s no better rehearsal than to write the script needed to set up your Powershell People profile!)

Prizes

We’d like to offer thanks in advance to our presenting sponsors, who are providing the majority of the prizes.

First prizes are awarded by our panel of celebrity judges. These judges will review the events that received the top community vote scores, but will use their own discretion for awarding the prizes. There are no fixed criteria for these prizes.

Note   We’ve got more prizes in the works…stay tuned to the Scripting Games site for news and announcements!

Overall winners across all events

First prize: Complimentary pass (admission only; no expenses are covered) to your choice of Microsoft TechEd North America 2013, TechEd Europe 2013, or TechEd NA 2014.

Second prize: SAPIEN Software Suite 2012 ($699 value) provided by SAPIEN Technologies

Third prize: Five ebooks (average value $200) provided by Manning Press

Event 6

First prize: PrimalScript 2012 ($349 value) provided by SAPIEN Technologies

Third prize: eBook (average value $40) provided by Manning Press

Event 5

First prize: PowerShell Studio 2012 ($349 value) provided by SAPIEN Technologies

Third prize: eBook (average value $40) provided by Manning Press

Event 4

Third prize: eBook (average value $40) provided by Manning Press

Event 3

Third prize: eBook (average value $40) provided by Manning Press

Event 2

Third prize: eBook (average value $40) provided by Manning Press

Event 1

Third prize: eBook (average value $40) provided by Manning Press

Crowd Favorite prizes

These prizes are awarded to the events with the top community vote score. We will award one prize for each event in each track.

Third prize (all events): ebook (average value $40) provided by Manning

Prizes for community voting

The top two community voters will receive a complimentary pass (admission only; no expenses are covered) to the PowerShell Summit North America 2014. “Top voters” will be identified by the quantity of votes (in either track) and by the quality (consistency, fairness) of their votes.

In addition, the following prizes will be raffled, with each vote that is cast acting as a raffle ticket:

  • Four $50.00 gift certificates to the SAPIEN Technologies online store, provided by SAPIEN Technologies
  • Twenty ebooks (average value $40) provided by Manning Press

Why you should vote

If you think you’re not qualified to vote on the entries…well actually, you are qualified. Just ask yourself, “Is this a script or command I’d want running in my production environment? Is this the work of a person I’d hire, if I had the opportunity? Did I learn something from this entry?”

Then vote with your heart. Everyone is qualified. And if you can leave a brief comment about why you voted the way you did, even better. The votes are anonymous, as are entries during the voting period, so be polite and professional, and treat others as you’d want to be treated yourself.

And remember, every vote equates to a prize raffle ticket!

Oh…this should go without saying, but we’re gonna say it anyway: don’t be mean. We do have systems in place to watch for odd voting patterns, like handing out all 1s or all 5s, just to rack up pointlets. We also watch for sequence patterns and other signs of abuse. All of those things trip alarms. We also look into things manually. If we find wrong doing, you’ll be banned from the Games for life. Seriously. Oh, we’ll talk to you about it first, we’re not mean. But we absolutely won’t stand for this system being abused.

The future of the Games is in peer review and voting. Your opinion—the opinion of someone working in a production environment—is what’s important in the real world, not the opinion of some fancy-pants judge.  Part of the Games (the expert judge commentary, for example) will make you a better voter and judge in the future, and that’s how we’re going to help build a better overall Windows PowerShell community. So respect the vote.

We sure hope you’ll play along. Be sure to watch the feed on Scripting Games site for the latest news and announcements!

~Don

Thank you, Don, for this information. Stay tuned. Tomorrow we have the 2013 Scripting Games Competitors Guide.

I invite you to follow me on Twitter and Facebook. If you have any questions, send email to me at [email protected], or post your questions on the Official Scripting Guys Forum. See you tomorrow. Until then, peace.

Ed Wilson, Microsoft Scripting Guy 

PhillyPoSH 04/04/2013 meeting summary


  1. Jason Helmick remotely gave a demo of Sapien’s Powershell Studio
  2. Ed Wilson, The Scripting Guy, gave a presentation on the different ways to remotely manage a Windows 8 workstation (remotely via the Charlotte PowerShell User Group)
  3. Announcements
    1. The Scripting games start on 04/25/2013, make sure to sign up! We plan on doing a post mortem once the games are done just like we did with the Winter Scripting Camp
    2. Check out the Mississippi PowerShell User, which meets virtually every 2nd Tuesday. Take a look at their schedule which is filled with great speakers.

The 2013 Winter Scripting Camp


We’ll be announcing Winter Scripting Camp the first week of February. This is a special invite-only event that will be open to subscribers of the PowerShell.org TechLetter. It will work just like the Scripting Games, but will feature only a couple of events and will not include any prizes. We will, however, announce the top scorers.

Scripting Camp is primarily an opportunity for us to audition our new platform, to kick the tires, and make sure everything’s ready for the official Games, which will kick off in April at the PowerShell Summit 2013 North America.

If you’re interested in Camping with us, please sign up for the TechLetter this week (prior to Feb 1st). We’ll be sending out a special notification to the TechLetter subscriber list with sign-up instructions.

Honorary Scripting Guy


I am pleased, honored and humbled to be selected as an Honorary Scripting Guy for 2012. I certainly would like to thank Ed Wilson, THE Scripting Guy. I would also like to congratulate my fellow honorees. If you aren’t following these people on Twitter, G+ or the blogosphere you are missing out on a wealth of information. I hear the music cuing so my time is almost up. But before I leave I would also like to thank all of you who read my work and support me. Without your interest, enthusiasm and support I’d just be some old guy in a bath robe banging on a keyboard.

Learn more about the other honorees here.

Post to Twitter Post to Plurk Post to Yahoo Buzz Post to Delicious Post to Digg Post to Facebook Post to FriendFeed Post to Google Buzz Post to Ping.fm Post to Reddit Post to Slashdot Post to StumbleUpon Post to Technorati

Episode 17 – With “The Scripting Guys!”


A Podcast about Windows PowerShell.

Listen:

In This Episode

  • Greg and Jean “The Scripting Guys” themselves are our special guests. Head over to the Script Center!
  • Jonathan was out with back problems.

Ways to interact with us:

See you next time!