&lt;?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Articles from December 2013 on PowerShell.org - Welcome Automaters!</title><link>https://powershell.org/articles/2013/12/</link><description>Recent content in Articles from December 2013 on PowerShell.org - Welcome Automaters!</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://powershell.org/articles/2013/12/index.xml" rel="self" type="application/rss+xml"/><item><title>State of the Org, ending 2013</title><link>https://powershell.org/articles/2013-12-30-state-of-the-org-ending-2013/</link><guid>https://powershell.org/articles/2013-12-30-state-of-the-org-ending-2013/</guid><pubDate>Mon, 30 Dec 2013 19:24:37 +0000</pubDate><description>&lt;p&gt;I wanted to take a moment and wish everyone a very happy new year, and to do a sort of wrap-up of 2013 from PowerShell.org&amp;rsquo;s perspective.&lt;br&gt;
We started 2013 with a bang, including our first-ever PowerShell Summit North America, held on-campus at Microsoft in Redmond. We&amp;rsquo;ll be returning to the Seattle area in April 2014 for &lt;a href="https://powershell.org/community-events/summit/"&gt;PowerShell Summit North America 2014&lt;/a&gt;, and are planning the first &lt;a href="https://powershell.org/community-events/summit/"&gt;PowerShell Summit Europe 2014&lt;/a&gt; in Amsterdam in September. For the N.A. show, we need about 50 more Summit attendees to break even, and can accommodate about 100 more than we&amp;rsquo;ve currently got registered.&lt;br&gt;
We ran a very successful Scripting Games that kicked off just as the Summit was ending. Thousands participated, tens of thousands of dollars in prizes were handed out, and most importantly the Games made the transition from being a much-loved child of the Microsoft Scripting Guys to being a community-owned event that can hopefully continue forever. We&amp;rsquo;ve got the first Winter Scripting Games in a loooong time starting in just a few days, in fact.&lt;br&gt;
In the wake of The Scripting Games, we ran a summer-long series of &lt;a href="https://powershell.org/category/great-debates/"&gt;Great Debates&lt;/a&gt;, and your comments on those informed the first-ever &lt;a href="https://powershell.org/newsletter/"&gt;Community Book of PowerShell Practices&lt;/a&gt;, now offered as a free ebook.&lt;br&gt;
PowerShell.org, Inc. closed its first fiscal year at the end of June 2013, and financially we lost just a bit of money. Don&amp;rsquo;t worry - that was always more or less the intent; we&amp;rsquo;re not running the corporation to make a buck, but rather to more-or-less break even. At the moment, we have $29,988.25 in our checking account, most of which is earmarked for Summit 2014 expenses.&lt;br&gt;
We&amp;rsquo;re now providing hosting services for about 17 &lt;a href="https://powershell.org/user-groups/"&gt;local and regional user groups&lt;/a&gt;, giving them a spot to post upcoming meeting dates, post-meeting file attachments, and other details. We&amp;rsquo;re hoping this helps raise awareness of the efforts they&amp;rsquo;re all making to have a strong local PowerShell support system in place.&lt;br&gt;
2013 also saw the &lt;a href="https://powershell.org/powerscripting-podcast/"&gt;PowerScripting Podcast&lt;/a&gt; become a welcome part of PowerShell.org. Host Jon Walz also got his first MVP Award, a long-awaited and well-deserved honor that he now shares with co-host Hal Rottenberg. Everyone appreciates the hard work they do, and we at PowerShell.org wanted to make sure they had the resources to keep doing it (equipment ain&amp;rsquo;t free), so we offered to help out when they needed, and they graciously accepted. We&amp;rsquo;re delighted to be working with them.&lt;br&gt;
PowerShell.org played an important role in developing Microsoft&amp;rsquo;s official entry-level PowerShell training, course 10961, by giving the authors (e.g., me) a place to survey folks about topic, level of coverage, and more, and to solicit feedback on the &amp;ldquo;A&amp;rdquo; and &amp;ldquo;B&amp;rdquo; revs while updating the course for PowerShell v4. This site (and all of you) also played an important role in selecting topics for the advanced-level training, course 10962, which will be developed in 2014. Finally, you all helped provide feedback for Microsoft Courseware Marketplace course 55039, which covers PowerShell scripting and toolmaking. When you see a survey posted here, jump in - it makes a very real difference in some very important projects!&lt;br&gt;
2013 was also the year we Moved to Azure, spinning up an Azure-hosted CentOS VM that&amp;rsquo;s now running the site. It&amp;rsquo;s gotten faster, is a bit easier to maintain, and is a heck of a lot more highly available thanks to Microsoft&amp;rsquo;s cloud hosting.&lt;br&gt;
I&amp;rsquo;m extremely proud to have had so many folks jump in and help out this year. Dave Wyatt, Matt Penny, Matt Johnson, Mike Shepard, and Nicholas Getchell have all taken on curator roles for the free ebooks we offer on PowerShell.org. They&amp;rsquo;re doing a wonderful job in making sure those titles stay updated - so much so, that &lt;a href="https://powershell.org/newsletter/"&gt;we&amp;rsquo;re now just linking to the books&amp;rsquo; GitHub repository&lt;/a&gt;, where you can download the DOC files directly. Dave Wyatt has also been &lt;a href="https://powershell.org/author/dlwyatt/"&gt;posting some incredibly detailed and informative blog posts&lt;/a&gt; that I hope you&amp;rsquo;re reading - I really appreciate his contributions here. I also want to thank Matt Tilford, Chris Hunt, and Mark Keisling, who have taken on editorial duties for the &lt;a href="https://powershell.org/newsletter/"&gt;TechLetter newsletter&lt;/a&gt;. Our aim is to put out a solid, informative, technically deep monthly offering and these guys are absolutely on the job. I hope you&amp;rsquo;re subscribed, because if you aren&amp;rsquo;t, you&amp;rsquo;re missing out. Finally, MVP &lt;a href="https://powershell.org/author/stevenmurawski/"&gt;Steven Murawski&lt;/a&gt; has made PowerShell.org his home for Desired State Configuration (DSC) blogs and code, and he&amp;rsquo;s been prolific. His employer, StackExchange, has been an early adopter of the DSC technology, and Steven&amp;rsquo;s been sharing pretty much everything he&amp;rsquo;s learned.&lt;br&gt;
We&amp;rsquo;ve had some transitions in 2013. Board member and co-founder Kirk Munro has had to step away from day-to-day duties with PowerShell.org, although he remains a member of the board. Board member Jason Helmick has stepped into a second-in-command position, and is more or less running the North America Summit from an operational perspective. Jason earned his first MVP Award this year, giving us an all-MVP Board that also includes myself, Jeffery Hicks, and Richard Siddaway.&lt;br&gt;
I&amp;rsquo;m extremely proud of everything we&amp;rsquo;ve accomplished. I&amp;rsquo;m delighted that so many folks are jumping into the &lt;a href="https://powershell.org/forums/"&gt;forums&lt;/a&gt; and offering answers to questions - it&amp;rsquo;s a massive relief on my own workload, and there are some damn smart folks offering their help to the community for free. In fact, we plan to recognize some of them in our first-ever PowerShell Heroes award, scheduled for January 2014. We&amp;rsquo;re also going to make good on a promise I made when we started this site: our above-and-beyond contributors are going to become part-owners of this community with an award of stock in PowerShell.org, Inc. That&amp;rsquo;ll give them some concrete control over the community they&amp;rsquo;re helping to build. Look for that mid-2014, when we near the end of our fiscal year.&lt;br&gt;
For 2014, I&amp;rsquo;d like to thank our returning sponsors, &lt;a href="http://www.sapien.com"&gt;SAPIEN Technologies&lt;/a&gt; and &lt;a href="http://interfacett.com"&gt;Interface Technical Training&lt;/a&gt;. These folks give a lot, financially, to help make this site work. Please show them your appreciation in every way you can. In 2014, my company, &lt;a href="http://concentratedtech.com"&gt;Concentrated Tech&lt;/a&gt;, is also coming aboard as a sponsor, and I&amp;rsquo;ll be offering my first-ever public PowerShell training.&lt;br&gt;
I think 2014 should be a great year, both for PowerShell.org and for the broader PowerShell community that we&amp;rsquo;re trying to serve. If you&amp;rsquo;re new here, or you&amp;rsquo;ve just been lurking, please jump in and help. Write an article about something you learned, answer a question in the forums, or volunteer to help out. We&amp;rsquo;re all in this together, and the stronger a community we all make _together, _the more we&amp;rsquo;ll be able to support each other when needs arise.&lt;br&gt;
I look forward to serving you in 2014!&lt;br&gt;
Don Jones&lt;br&gt;
President and CEO&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>I wanted to take a moment and wish everyone a very happy new year, and to do a sort of wrap-up of 2013 from PowerShell.org&rsquo;s perspective.<br>
We started 2013 with a bang, including our first-ever PowerShell Summit North America, held on-campus at Microsoft in Redmond. We&rsquo;ll be returning to the Seattle area in April 2014 for<a href="https://powershell.org/community-events/summit/">PowerShell Summit North America 2014</a>, and are planning the first<a href="https://powershell.org/community-events/summit/">PowerShell Summit Europe 2014</a> in Amsterdam in September. For the N.A. show, we need about 50 more Summit attendees to break even, and can accommodate about 100 more than we&rsquo;ve currently got registered.<br>
We ran a very successful Scripting Games that kicked off just as the Summit was ending. Thousands participated, tens of thousands of dollars in prizes were handed out, and most importantly the Games made the transition from being a much-loved child of the Microsoft Scripting Guys to being a community-owned event that can hopefully continue forever. We&rsquo;ve got the first Winter Scripting Games in a loooong time starting in just a few days, in fact.<br>
In the wake of The Scripting Games, we ran a summer-long series of<a href="https://powershell.org/category/great-debates/">Great Debates</a>, and your comments on those informed the first-ever<a href="https://powershell.org/newsletter/">Community Book of PowerShell Practices</a>, now offered as a free ebook.<br>
PowerShell.org, Inc. closed its first fiscal year at the end of June 2013, and financially we lost just a bit of money. Don&rsquo;t worry - that was always more or less the intent; we&rsquo;re not running the corporation to make a buck, but rather to more-or-less break even. At the moment, we have $29,988.25 in our checking account, most of which is earmarked for Summit 2014 expenses.<br>
We&rsquo;re now providing hosting services for about 17<a href="https://powershell.org/user-groups/">local and regional user groups</a>, giving them a spot to post upcoming meeting dates, post-meeting file attachments, and other details. We&rsquo;re hoping this helps raise awareness of the efforts they&rsquo;re all making to have a strong local PowerShell support system in place.<br>
2013 also saw the<a href="https://powershell.org/powerscripting-podcast/">PowerScripting Podcast</a> become a welcome part of PowerShell.org. Host Jon Walz also got his first MVP Award, a long-awaited and well-deserved honor that he now shares with co-host Hal Rottenberg. Everyone appreciates the hard work they do, and we at PowerShell.org wanted to make sure they had the resources to keep doing it (equipment ain&rsquo;t free), so we offered to help out when they needed, and they graciously accepted. We&rsquo;re delighted to be working with them.<br>
PowerShell.org played an important role in developing Microsoft&rsquo;s official entry-level PowerShell training, course 10961, by giving the authors (e.g., me) a place to survey folks about topic, level of coverage, and more, and to solicit feedback on the &ldquo;A&rdquo; and &ldquo;B&rdquo; revs while updating the course for PowerShell v4. This site (and all of you) also played an important role in selecting topics for the advanced-level training, course 10962, which will be developed in 2014. Finally, you all helped provide feedback for Microsoft Courseware Marketplace course 55039, which covers PowerShell scripting and toolmaking. When you see a survey posted here, jump in - it makes a very real difference in some very important projects!<br>
2013 was also the year we Moved to Azure, spinning up an Azure-hosted CentOS VM that&rsquo;s now running the site. It&rsquo;s gotten faster, is a bit easier to maintain, and is a heck of a lot more highly available thanks to Microsoft&rsquo;s cloud hosting.<br>
I&rsquo;m extremely proud to have had so many folks jump in and help out this year. Dave Wyatt, Matt Penny, Matt Johnson, Mike Shepard, and Nicholas Getchell have all taken on curator roles for the free ebooks we offer on PowerShell.org. They&rsquo;re doing a wonderful job in making sure those titles stay updated - so much so, that<a href="https://powershell.org/newsletter/">we&rsquo;re now just linking to the books&rsquo; GitHub repository</a>, where you can download the DOC files directly. Dave Wyatt has also been<a href="https://powershell.org/author/dlwyatt/">posting some incredibly detailed and informative blog posts</a> that I hope you&rsquo;re reading - I really appreciate his contributions here. I also want to thank Matt Tilford, Chris Hunt, and Mark Keisling, who have taken on editorial duties for the<a href="https://powershell.org/newsletter/">TechLetter newsletter</a>. Our aim is to put out a solid, informative, technically deep monthly offering and these guys are absolutely on the job. I hope you&rsquo;re subscribed, because if you aren&rsquo;t, you&rsquo;re missing out. Finally, MVP<a href="https://powershell.org/author/stevenmurawski/">Steven Murawski</a> has made PowerShell.org his home for Desired State Configuration (DSC) blogs and code, and he&rsquo;s been prolific. His employer, StackExchange, has been an early adopter of the DSC technology, and Steven&rsquo;s been sharing pretty much everything he&rsquo;s learned.<br>
We&rsquo;ve had some transitions in 2013. Board member and co-founder Kirk Munro has had to step away from day-to-day duties with PowerShell.org, although he remains a member of the board. Board member Jason Helmick has stepped into a second-in-command position, and is more or less running the North America Summit from an operational perspective. Jason earned his first MVP Award this year, giving us an all-MVP Board that also includes myself, Jeffery Hicks, and Richard Siddaway.<br>
I&rsquo;m extremely proud of everything we&rsquo;ve accomplished. I&rsquo;m delighted that so many folks are jumping into the<a href="https://powershell.org/forums/">forums</a> and offering answers to questions - it&rsquo;s a massive relief on my own workload, and there are some damn smart folks offering their help to the community for free. In fact, we plan to recognize some of them in our first-ever PowerShell Heroes award, scheduled for January 2014. We&rsquo;re also going to make good on a promise I made when we started this site: our above-and-beyond contributors are going to become part-owners of this community with an award of stock in PowerShell.org, Inc. That&rsquo;ll give them some concrete control over the community they&rsquo;re helping to build. Look for that mid-2014, when we near the end of our fiscal year.<br>
For 2014, I&rsquo;d like to thank our returning sponsors,<a href="http://www.sapien.com">SAPIEN Technologies</a> and<a href="http://interfacett.com">Interface Technical Training</a>. These folks give a lot, financially, to help make this site work. Please show them your appreciation in every way you can. In 2014, my company,<a href="http://concentratedtech.com">Concentrated Tech</a>, is also coming aboard as a sponsor, and I&rsquo;ll be offering my first-ever public PowerShell training.<br>
I think 2014 should be a great year, both for PowerShell.org and for the broader PowerShell community that we&rsquo;re trying to serve. If you&rsquo;re new here, or you&rsquo;ve just been lurking, please jump in and help. Write an article about something you learned, answer a question in the forums, or volunteer to help out. We&rsquo;re all in this together, and the stronger a community we all make _together, _the more we&rsquo;ll be able to support each other when needs arise.<br>
I look forward to serving you in 2014!<br>
Don Jones<br>
President and CEO</p>
]]></content:encoded></item><item><title>Introducing the Judges for Winter 2014 Scripting Games</title><link>https://powershell.org/articles/2013-12-28-introducing-the-judges-for-winter-2014-scripting-games/</link><guid>https://powershell.org/articles/2013-12-28-introducing-the-judges-for-winter-2014-scripting-games/</guid><pubDate>Sat, 28 Dec 2013 15:50:47 +0000</pubDate><description>&lt;p&gt;In the last few years there has been a long list of people judging the Scripting Games. Those people were expected to view as many entries as possible, preferably all, and score the entries as well as providing feedback on the individual entries. That is a ton of work especially when you consider that the judges were all volunteers.&lt;br&gt;
This time round we&amp;rsquo;re attempting to spread the load somewhat. Mike Robbins has done a superb job recruiting coaches for the &lt;a href="https://powershell.org/2013/12/23/introducing-the-coaches-of-the-2014-winter-scripting-games/"&gt;&lt;/a&gt; Its their job to look at the entries and make suggestions and hints to the teams - if the teams wish to take advantage of this option. Looking at the list of coaches - I know I would take advantage of their assistance if I was competing.&lt;br&gt;
That leaves judging. This time we&amp;rsquo;re using a small group of judges. We have prepared scoring criteria for the events with some additional style points available to the judges. This will make MOST of the scoring objective but we&amp;rsquo;ve a bit of subjectivity available for individual judges to pick out, and hopefully comment on, things they like or don&amp;rsquo;t like.&lt;br&gt;
The judges are all very experienced PowerShell practitioners with more books written, talks given, blog posts created and classes taught between them than anyone would want to count. In alphabetical order your judges for the Winter 2014 Scripting Games are:&lt;br&gt;
Don Jones - founder and CEO of powershell.org. Author of several PowerShell books including the highly recommended Learn PowerShell v3 in a Month of Lunches and co-author of PowerShell in Depth. Don is a PowerShell MVP, PowerShell educator, columnist and course creator.&lt;br&gt;
Jason Helmick - Board member of powershell.org. A PowerShell MVP and author of Learn IIS in a Month of Lunches which includes lots of PowerShell. Jason also delivered the recent two-part Introducing PowerShell MVA sessions with Jeffrey Snover. PowerShell educator, columnist and speaker.&lt;br&gt;
Jeffery Hicks - Board member of powershell.org. PowerShell MVP. Co-author of PowerShell in Depth, lead editor of PowerShell Deep Dives and author of other PowerShell books. Jeffrey is also a PowerShell columnist and educator&lt;br&gt;
Ed Wilson - The Scripting Guy. Ed runs the Hey! Scripting Guy &lt;a href="http://blogs.technet.com/b/heyscriptingguy/"&gt;&lt;/a&gt; Author of several PowerShell books including Windows PowerShell Best Practices and Windows PowerShell Scripting Guide. Ed also delivers PowerShell classes and is a much in demand speaker.&lt;br&gt;
The list of judges is completed by&lt;br&gt;
Richard Siddaway - Board member of powershell.org. PowerShell MVP. Co-author of PowerShell in Depth and author of PowerShell in Practice and PowerShell and WMI. Frequent blogger on PowerShell related topics.&lt;br&gt;
Between them the judges have accumulated over 30 years of PowerShell experience that is focussed on judging the Games. They are all looking forward to the Games and hope to see your entries.&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>In the last few years there has been a long list of people judging the Scripting Games. Those people were expected to view as many entries as possible, preferably all, and score the entries as well as providing feedback on the individual entries. That is a ton of work especially when you consider that the judges were all volunteers.<br>
This time round we&rsquo;re attempting to spread the load somewhat. Mike Robbins has done a superb job recruiting coaches for the<a href="https://powershell.org/2013/12/23/introducing-the-coaches-of-the-2014-winter-scripting-games/"/> Its their job to look at the entries and make suggestions and hints to the teams - if the teams wish to take advantage of this option. Looking at the list of coaches - I know I would take advantage of their assistance if I was competing.<br>
That leaves judging. This time we&rsquo;re using a small group of judges. We have prepared scoring criteria for the events with some additional style points available to the judges. This will make MOST of the scoring objective but we&rsquo;ve a bit of subjectivity available for individual judges to pick out, and hopefully comment on, things they like or don&rsquo;t like.<br>
The judges are all very experienced PowerShell practitioners with more books written, talks given, blog posts created and classes taught between them than anyone would want to count. In alphabetical order your judges for the Winter 2014 Scripting Games are:<br>
Don Jones - founder and CEO of powershell.org. Author of several PowerShell books including the highly recommended Learn PowerShell v3 in a Month of Lunches and co-author of PowerShell in Depth. Don is a PowerShell MVP, PowerShell educator, columnist and course creator.<br>
Jason Helmick - Board member of powershell.org. A PowerShell MVP and author of Learn IIS in a Month of Lunches which includes lots of PowerShell. Jason also delivered the recent two-part Introducing PowerShell MVA sessions with Jeffrey Snover. PowerShell educator, columnist and speaker.<br>
Jeffery Hicks - Board member of powershell.org. PowerShell MVP. Co-author of PowerShell in Depth, lead editor of PowerShell Deep Dives and author of other PowerShell books. Jeffrey is also a PowerShell columnist and educator<br>
Ed Wilson - The Scripting Guy. Ed runs the Hey! Scripting Guy<a href="http://blogs.technet.com/b/heyscriptingguy/"/> Author of several PowerShell books including Windows PowerShell Best Practices and Windows PowerShell Scripting Guide. Ed also delivers PowerShell classes and is a much in demand speaker.<br>
The list of judges is completed by<br>
Richard Siddaway - Board member of powershell.org. PowerShell MVP. Co-author of PowerShell in Depth and author of PowerShell in Practice and PowerShell and WMI. Frequent blogger on PowerShell related topics.<br>
Between them the judges have accumulated over 30 years of PowerShell experience that is focussed on judging the Games. They are all looking forward to the Games and hope to see your entries.</p>
]]></content:encoded></item><item><title>January Charlotte PowerShell User Group Meeting</title><link>https://powershell.org/articles/2013-12-27-january-charlotte-powershell-user-group-meeting/</link><guid>https://powershell.org/articles/2013-12-27-january-charlotte-powershell-user-group-meeting/</guid><pubDate>Fri, 27 Dec 2013 14:15:39 +0000</pubDate><description>&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;Here is some additional information about the Winter Scripting Games:&lt;/p&gt;
&lt;h5 id="teams-can-consist-of-between-2-to-6-scripters-and-official-registration-opens-on-jan-2nd" class="ps-heading"&gt;Teams can consist of between 2 to 6 Scripters and official registration opens on Jan 2nd.&lt;a class="ps-heading-anchor" href="#teams-can-consist-of-between-2-to-6-scripters-and-official-registration-opens-on-jan-2nd" aria-label="Link to this section" title="Link to this section"&gt;&lt;i class="fas fa-link" aria-hidden="true"&gt;&lt;/i&gt;&lt;/a&gt;
&lt;/h5&gt;
&lt;p&gt;There will be a total of 4 official events for the Winter Scripting Games:&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>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.</p><p>Here is some additional information about the Winter Scripting Games:</p><h5 id="teams-can-consist-of-between-2-to-6-scripters-and-official-registration-opens-on-jan-2nd" class="ps-heading">Teams can consist of between 2 to 6 Scripters and official registration opens on Jan 2nd.<a class="ps-heading-anchor" href="#teams-can-consist-of-between-2-to-6-scripters-and-official-registration-opens-on-jan-2nd" aria-label="Link to this section" title="Link to this section"><i class="fas fa-link" aria-hidden="true"/></a></h5><p>There will be a total of 4 official events for the Winter Scripting Games:</p><p><em>January 19th, January 26th, February 2nd, &amp; February 9th</em></p><p>Check out the<a href="https://powershell.org/2013/12/16/2014-winter-scripting-games-schedule/">schedule</a> for all the details. In addition, be sure to follow the<a href="https://twitter.com/search?q=%23pshgames&amp;src=hash">#pshgames</a> hashtag on twitter. There is also<a href="http://mikefrobbins.com/2013/12/23/introducing-the-coaches-of-the-2014-winter-scripting-games/">a list of Coaches</a> who are blogging and<a href="https://twitter.com/mikefrobbins/lists/pshcoaches">tweeting</a> helpful info and tips including this<a href="http://p0w3rsh3ll.wordpress.com/2013/12/26/be-prepared-for-the-winter-scripting-games-3-2-1-go/">excellent preparation guide</a>. Lastly, before you head over to the<a href="http://scriptinggames.org/">scripting games website</a> be sure to read this<a href="https://powershell.org/2013/12/21/important-scripting-games-login-and-operational-information/">Important Scripting Games Login and Operational Information</a> post.</p>
]]></content:encoded></item><item><title>Introducing the Coaches of the 2014 Winter Scripting Games</title><link>https://powershell.org/articles/2013-12-23-introducing-the-coaches-of-the-2014-winter-scripting-games/</link><guid>https://powershell.org/articles/2013-12-23-introducing-the-coaches-of-the-2014-winter-scripting-games/</guid><pubDate>Mon, 23 Dec 2013 17:21:37 +0000</pubDate><description>&lt;p&gt;A few weeks ago, just before the announcement to start recruiting your team for the 2014 Winter Scripting Games, I was contacted by Don Jones and Richard Siddaway about an opportunity to become the Head Coach for the Winter Scripting Games. I was honored to have been contacted and I&amp;rsquo;m a firm believer of taking advantage of opportunities when they emerge, especially when they&amp;rsquo;re PowerShell related, so I graciously accepted.&lt;br&gt;
One of my first responsibilities was to recruit a small team of coaches. I immediately went to work before potential coaches committed themselves to participating on teams. We had a huge number of people in the PowerShell community who had volunteered to be a coach and while we would have liked to have selected everyone who volunteered, we only had a specific number of positions to fill. Without further ado, here is the list of the coaches for the 2014 Winter Scripting Games:&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>A few weeks ago, just before the announcement to start recruiting your team for the 2014 Winter Scripting Games, I was contacted by Don Jones and Richard Siddaway about an opportunity to become the Head Coach for the Winter Scripting Games. I was honored to have been contacted and I&rsquo;m a firm believer of taking advantage of opportunities when they emerge, especially when they&rsquo;re PowerShell related, so I graciously accepted.<br>
One of my first responsibilities was to recruit a small team of coaches. I immediately went to work before potential coaches committed themselves to participating on teams. We had a huge number of people in the PowerShell community who had volunteered to be a coach and while we would have liked to have selected everyone who volunteered, we only had a specific number of positions to fill. Without further ado, here is the list of the coaches for the 2014 Winter Scripting Games:</p><pre><code> **Name**
**Twitter**
[Boe Prox](http://learn-powershell.net/)
[@proxb](http://twitter.com/proxb)
[Carlo Mancini](http://www.happysysadm.com/)
[@sysadm2010](http://twitter.com/sysadm2010)
[Claus Nielsen](http://xipher.dk/)
[@claustn](http://twitter.com/claustn)
[Emin Atac](http://p0w3rsh3ll.wordpress.com/)
[@p0w3rsh3ll](http://twitter.com/p0w3rsh3ll)
[Jan Egil Ring](http://blog.powershell.no/)
[@JanEgilRing](http://twitter.com/JanEgilRing)
[Jeff Wouters](http://jeffwouters.nl/)
[@JeffWouters](http://twitter.com/JeffWouters)
[Jonathan Medd](http://www.jonathanmedd.net/)
[@jonathanmedd](http://twitter.com/jonathanmedd/)
[Lido Paglia](http://paglia.org/)
[@nicemarmot](http://twitter.com/nicemarmot)
[Matt Hitchcock](http://sgitpro.com/)
[@hitchysg](http://twitter.com/hitchysg)
[Rob Campbell](http://mjolinor.wordpress.com/)
[@mjolinor](http://twitter.com/mjolinor)
[Rohn Edwards](http://rohnspowershellblog.wordpress.com/)
[@magicrohn](http://twitter.com/magicrohn)
[Sahal Omer](http://www.get-exchange.info/)
[@GetExchange](http://twitter.com/GetExchange)
[Steve Murawski](http://stevenmurawski.com/)
[@StevenMurawski](http://twitter.com/StevenMurawski)</code></pre><p><a href="http://mikefrobbins.com/2013/12/23/introducing-the-coaches-of-the-2014-winter-scripting-games/">Click here</a>
 to be redirected to the original post of this article on the author’s blog site where you can read the remainder of the article.</p><p>µ</p>
]]></content:encoded></item><item><title>My outline for accelerated PowerShell training</title><link>https://powershell.org/articles/2013-12-20-my-outline-for-accelerated-powershell-training/</link><guid>https://powershell.org/articles/2013-12-20-my-outline-for-accelerated-powershell-training/</guid><pubDate>Fri, 20 Dec 2013 22:40:00 +0000</pubDate><description>&lt;p&gt;When I teach PowerShell, either at a private client or in a public class, I tend to use my own outlines. I&amp;rsquo;m comfortable with them, and they work really well. They formed the basis for the Microsoft 10961 and 55039 courses, although I had to make some changes to accommodate Microsoft standards and varying MCT delivery styles. But I&amp;rsquo;m often asked if there&amp;rsquo;s a &amp;ldquo;MOC-equivalent&amp;rdquo; outline that combines the entry-level 10961 with the scripting-focused 55039.&lt;br&gt;
Yup.&lt;br&gt;
First, do understand that I naturally teach at a very concise and accelerated pace. I don&amp;rsquo;t spend much time on slides; I tend to skip right to demos, and use those to explain what I&amp;rsquo;m explaining. If you follow a more common delivery style of around 5min per slide, plus taking your time on demos, my approach might not work well for you. I also tend to not tell a lot of ancillary stories, I tend to make students take break during lab time (rather than individually scheduling breaks), and I tend to be as concise as possible in my lectures.&lt;br&gt;
Also, when accelerating these courses together, you don&amp;rsquo;t do &lt;em&gt;all&lt;/em&gt; of the labs. For labs with multiple components (find these 20 command), I&amp;rsquo;ll do about 1/3 of them. For the 55039 main-sequence labs, I&amp;rsquo;ll tell students to pick the &amp;ldquo;A,&amp;rdquo; &amp;ldquo;B,&amp;rdquo; or &amp;ldquo;C&amp;rdquo; version rather than doing all three; sometimes I&amp;rsquo;ll just have them do the &amp;ldquo;D&amp;rdquo; version (which gives them a pre-done starting point for each module, rather than making them build on their own work from a previous module).&lt;br&gt;
For Day 1, I&amp;rsquo;ll cover modules 1-5, and maybe module 6, from 10961. Day 2 will be modules 7, 9, 11, and 12 (covering 6 first, if I didn&amp;rsquo;t get it done on Day 1). That&amp;rsquo;s the &amp;ldquo;core&amp;rdquo; PowerShell stuff. It&amp;rsquo;s a fast delivery; it&amp;rsquo;s possible to spread those out over three days if you prefer, but I explicitly skip modules 6, 8, and 10 at this stage.&lt;br&gt;
When my students all have strong shell or scripting skills, 2 days often gets me through that. If they&amp;rsquo;re newer, I&amp;rsquo;ll go slower on modules 1-5, do more of the labs, and take 3 days to cover that 10961 material.&lt;br&gt;
The remainder of the course comes from 55039. That&amp;rsquo;ll be 2 or 3 days, depending on how long it took you to do the 10961 material. Regardless, I&amp;rsquo;ll cover modules 2-5. I&amp;rsquo;ll usually skip module 6, and try to end the day with module 7 on debugging. I&amp;rsquo;ll cover module 8, 9, and 10. That&amp;rsquo;s usually 2 days, so it&amp;rsquo;s the last thing I do if I took 3 days to cover the 10961 stuff.&lt;br&gt;
If I got through 10961 in 2 days, I&amp;rsquo;ll finish the 55039 material, covering modules 11, 13, and 16. If students insist on workflows, I&amp;rsquo;ll throw that module in there - I have mixed feelings and results when it comes to workflow, so it&amp;rsquo;s not part of my standard accelerated delivery. If you have extra time, my priority then goes to modules 15, 13, and 14, in that order. 14 gets you some GUI-building experience, so if the class is pushing for that I&amp;rsquo;ll include that module instead of workflow.&lt;br&gt;
If all that seems a little informal - well, it is. I&amp;rsquo;m very good at reading my students, and making sure folks are actually keeping up, so I don&amp;rsquo;t press too hard. This is a &lt;em&gt;lot&lt;/em&gt; of conceptual and practical material to cover in a week.&lt;br&gt;
Price-wise, in the US, I see this kind of accelerated class going for around $3500, although a lot of training centers offer significant discounts. This accelerated outline is absolutely worth it: you&amp;rsquo;re literally taking someone from zero and teaching them how to build their own script modules and tools in PowerShell. It&amp;rsquo;s a &lt;em&gt;lot&lt;/em&gt; to cover; not every class will be up to it.&lt;br&gt;
The labs in both courses are solid, and I&amp;rsquo;m especially happy with the ones in 55039 in terms of what they cover, and in how challenging they are. I&amp;rsquo;ll warn you that the 55039 labs don&amp;rsquo;t do a lot of hand-holding. Students are expected to &lt;em&gt;learn&lt;/em&gt; the material and then execute the labs; the &amp;ldquo;answer keys&amp;rdquo; are outright sample solutions, not hints. But if you teach the material as provided, everything students &lt;em&gt;need&lt;/em&gt; is in there - if they&amp;rsquo;re willing to work hard and retain what you&amp;rsquo;ve shared.&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>When I teach PowerShell, either at a private client or in a public class, I tend to use my own outlines. I&rsquo;m comfortable with them, and they work really well. They formed the basis for the Microsoft 10961 and 55039 courses, although I had to make some changes to accommodate Microsoft standards and varying MCT delivery styles. But I&rsquo;m often asked if there&rsquo;s a &ldquo;MOC-equivalent&rdquo; outline that combines the entry-level 10961 with the scripting-focused 55039.<br>
Yup.<br>
First, do understand that I naturally teach at a very concise and accelerated pace. I don&rsquo;t spend much time on slides; I tend to skip right to demos, and use those to explain what I&rsquo;m explaining. If you follow a more common delivery style of around 5min per slide, plus taking your time on demos, my approach might not work well for you. I also tend to not tell a lot of ancillary stories, I tend to make students take break during lab time (rather than individually scheduling breaks), and I tend to be as concise as possible in my lectures.<br>
Also, when accelerating these courses together, you don&rsquo;t do <em>all</em> of the labs. For labs with multiple components (find these 20 command), I&rsquo;ll do about 1/3 of them. For the 55039 main-sequence labs, I&rsquo;ll tell students to pick the &ldquo;A,&rdquo; &ldquo;B,&rdquo; or &ldquo;C&rdquo; version rather than doing all three; sometimes I&rsquo;ll just have them do the &ldquo;D&rdquo; version (which gives them a pre-done starting point for each module, rather than making them build on their own work from a previous module).<br>
For Day 1, I&rsquo;ll cover modules 1-5, and maybe module 6, from 10961. Day 2 will be modules 7, 9, 11, and 12 (covering 6 first, if I didn&rsquo;t get it done on Day 1). That&rsquo;s the &ldquo;core&rdquo; PowerShell stuff. It&rsquo;s a fast delivery; it&rsquo;s possible to spread those out over three days if you prefer, but I explicitly skip modules 6, 8, and 10 at this stage.<br>
When my students all have strong shell or scripting skills, 2 days often gets me through that. If they&rsquo;re newer, I&rsquo;ll go slower on modules 1-5, do more of the labs, and take 3 days to cover that 10961 material.<br>
The remainder of the course comes from 55039. That&rsquo;ll be 2 or 3 days, depending on how long it took you to do the 10961 material. Regardless, I&rsquo;ll cover modules 2-5. I&rsquo;ll usually skip module 6, and try to end the day with module 7 on debugging. I&rsquo;ll cover module 8, 9, and 10. That&rsquo;s usually 2 days, so it&rsquo;s the last thing I do if I took 3 days to cover the 10961 stuff.<br>
If I got through 10961 in 2 days, I&rsquo;ll finish the 55039 material, covering modules 11, 13, and 16. If students insist on workflows, I&rsquo;ll throw that module in there - I have mixed feelings and results when it comes to workflow, so it&rsquo;s not part of my standard accelerated delivery. If you have extra time, my priority then goes to modules 15, 13, and 14, in that order. 14 gets you some GUI-building experience, so if the class is pushing for that I&rsquo;ll include that module instead of workflow.<br>
If all that seems a little informal - well, it is. I&rsquo;m very good at reading my students, and making sure folks are actually keeping up, so I don&rsquo;t press too hard. This is a <em>lot</em> of conceptual and practical material to cover in a week.<br>
Price-wise, in the US, I see this kind of accelerated class going for around $3500, although a lot of training centers offer significant discounts. This accelerated outline is absolutely worth it: you&rsquo;re literally taking someone from zero and teaching them how to build their own script modules and tools in PowerShell. It&rsquo;s a <em>lot</em> to cover; not every class will be up to it.<br>
The labs in both courses are solid, and I&rsquo;m especially happy with the ones in 55039 in terms of what they cover, and in how challenging they are. I&rsquo;ll warn you that the 55039 labs don&rsquo;t do a lot of hand-holding. Students are expected to <em>learn</em> the material and then execute the labs; the &ldquo;answer keys&rdquo; are outright sample solutions, not hints. But if you teach the material as provided, everything students <em>need</em> is in there - if they&rsquo;re willing to work hard and retain what you&rsquo;ve shared.</p>
]]></content:encoded></item><item><title>Coaches and Judges Selected for Winter Scripting Games</title><link>https://powershell.org/articles/2013-12-19-coaches-and-judges-selected-for-winter-scripting-games/</link><guid>https://powershell.org/articles/2013-12-19-coaches-and-judges-selected-for-winter-scripting-games/</guid><pubDate>Thu, 19 Dec 2013 17:32:44 +0000</pubDate><description>&lt;p&gt;We&amp;rsquo;ve had an outpouring of support for the upcoming games, with more volunteers than we know what to do with!&lt;br&gt;
At this point, we have our judging panel completely full; we&amp;rsquo;re operating with a fairly small group of celebrity judges this time around. Games Master Richard Siddaway will introduce our judges in a few days.&lt;br&gt;
We&amp;rsquo;ve also filled our roster of Coaches, and Head Coach Mike Robbins will provide that lineup soon also.&lt;br&gt;
If you&amp;rsquo;ve volunteered but not heard from Richard or Mike, then you should definitely start recruiting a team for when registration and team formation opens in a couple of weeks!&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>We&rsquo;ve had an outpouring of support for the upcoming games, with more volunteers than we know what to do with!<br>
At this point, we have our judging panel completely full; we&rsquo;re operating with a fairly small group of celebrity judges this time around. Games Master Richard Siddaway will introduce our judges in a few days.<br>
We&rsquo;ve also filled our roster of Coaches, and Head Coach Mike Robbins will provide that lineup soon also.<br>
If you&rsquo;ve volunteered but not heard from Richard or Mike, then you should definitely start recruiting a team for when registration and team formation opens in a couple of weeks!</p>
]]></content:encoded></item><item><title>How "Quick and Dirty" Becomes "Permanent and Annoying."</title><link>https://powershell.org/articles/2013-12-10-how-quick-and-dirty-becomes-permanent-and-annoying/</link><guid>https://powershell.org/articles/2013-12-10-how-quick-and-dirty-becomes-permanent-and-annoying/</guid><pubDate>Tue, 10 Dec 2013 22:23:37 +0000</pubDate><description>&lt;p&gt;Consider the following:&lt;/p&gt;
&lt;p&gt;&lt;code&gt;$computers = Get-ADComputer -filter * -searchBase &amp;quot;ou=test,dc=company,dc=pri&amp;quot; foreach ($computer in $computers) { write-host &amp;quot;computer $computer&amp;quot; $result = Do-Something -computername $computer Write-Host &amp;quot;$($result.property) and $($result.value)&amp;quot; } &lt;/code&gt;Would you ever consider that acceptable? Some folks might well say, &amp;ldquo;sure! if I was just testing this, throwing in those Write-Hosts is no big deal. Heck, even if I was the only one who was going to use this, Write-Host isn&amp;rsquo;t bad.&amp;rdquo;&lt;br&gt;
And the point I&amp;rsquo;m going to make doesn&amp;rsquo;t just apply to Write-Host. It applies to &lt;em&gt;anytime&lt;/em&gt; when you&amp;rsquo;re doing something that you &lt;em&gt;know&lt;/em&gt; breaks &amp;ldquo;best practices,&amp;rdquo; but you justify it because it&amp;rsquo;s &amp;ldquo;just for you&amp;rdquo; or because &amp;ldquo;it&amp;rsquo;s just for testing.&amp;rdquo;&lt;br&gt;
To wit: if you need your script to output some status or tracking information, as in the above, use Write-Verbose. Yes, Write-Verbose requires a script or function to have this at the top:&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>Consider the following:</p><p><code>$computers = Get-ADComputer -filter * -searchBase "ou=test,dc=company,dc=pri" foreach ($computer in $computers) { write-host "computer $computer" $result = Do-Something -computername $computer Write-Host "$($result.property) and $($result.value)" }</code>Would you ever consider that acceptable? Some folks might well say, &ldquo;sure! if I was just testing this, throwing in those Write-Hosts is no big deal. Heck, even if I was the only one who was going to use this, Write-Host isn&rsquo;t bad.&rdquo;<br>
And the point I&rsquo;m going to make doesn&rsquo;t just apply to Write-Host. It applies to <em>anytime</em> when you&rsquo;re doing something that you <em>know</em> breaks &ldquo;best practices,&rdquo; but you justify it because it&rsquo;s &ldquo;just for you&rdquo; or because &ldquo;it&rsquo;s just for testing.&rdquo;<br>
To wit: if you need your script to output some status or tracking information, as in the above, use Write-Verbose. Yes, Write-Verbose requires a script or function to have this at the top:</p><p><code>[CmdletBinding()] Param()</code>Small price to pay for all the functionality it adds, but why not just use Write-Host and be done with it?<br><strong>Begin as you mean to proceed.</strong> That means, from the outset, assume everything is going to be a production-class tool and that it needs to be done right. You don&rsquo;t create output using Write-Host*, or output formatted text instead of objects, or any of a dozen other things because <em>eventually</em> that thing you made &ldquo;just for you&rdquo; will end up copied and pasted into something that everyone in the organization depends upon.<br>
And weren&rsquo;t you the one complaining you never have time to do stuff? So where are you going to find the time to go back and <em>re-do something the right way</em>? You won&rsquo;t. Your quick-and-dirty &ldquo;just for me&rdquo; will end up becoming an ugly pimple for the rest of time.<br>
It is <em>rarely</em><em>harder to do something the right way</em> in PowerShell. Yes, the right way might not be what habitually flies off of your fingertips - but that&rsquo;s not extra time, that&rsquo;s just you changing a habit. And again, Write-Host is just a convenient and easy example. I once was helping someone on a script, and in twelve different places, they had copied-and-pasted a short little logical construct to test connectivity to a computer on a specific protocol. It was maybe four lines of code. Most instances were commented out, indicating they&rsquo;d just been for testing.<br>
&ldquo;Why,&rdquo; I asked, &ldquo;didn&rsquo;t you put that into a function, and build a toggle into the function?&rdquo;<br>
&ldquo;Oh, it was just for testing.&rdquo;<br>
&ldquo;Yes, but this script is running a critical process now. It isn&rsquo;t just for testing. And it&rsquo;s fugly.&rdquo;<br>
&ldquo;I didn&rsquo;t have time to go back and&hellip;&rdquo;<br>
Just stop. Ugh. I know. Well, you had time to copy and paste in a dozen places, which took longer than just making the damn function would have taken in the first place.<br>
So the point: bad practices are always bad. Good practices are always good. And you should stay on the right side of the Force all the time, even when it&rsquo;s &ldquo;just for you,&rdquo; because someday that code is going to wind up being not &ldquo;just for you&rdquo; anymore. Begin coding as you mean to proceed: write as if everything&rsquo;s for posterity.</p><p>*unless you&rsquo;re specifically drawing an on-screen menu or something. Maybe then.</p>
]]></content:encoded></item><item><title>Charlotte Powershell User Group Holiday-themed Scripting Games</title><link>https://powershell.org/articles/2013-12-10-charlotte-powershell-user-group-holiday-themed-scripting-games/</link><guid>https://powershell.org/articles/2013-12-10-charlotte-powershell-user-group-holiday-themed-scripting-games/</guid><pubDate>Tue, 10 Dec 2013 22:16:10 +0000</pubDate><description>&lt;p&gt;The Charlotte Powershell Users Group meeting was held on Dec 5th. Jim put together a nifty challenge related to image manipulation. We started off with this nifty image. Pretty huh?&lt;br&gt;
&lt;a href="https://powershell.org/wp-content/uploads/2013/12/stegan1.png"&gt;&lt;img src="https://powershell.org/wp-content/uploads/2013/12/stegan1.png" alt="stegan1"&gt;&lt;/a&gt;&lt;br&gt;
The challenge was to manipulate the image using PowerShell to find the hidden message. After some discussion, the code was cracked and the image was displayed. As is normal with Powershell, there were multiple ways to achieve the end goal. Feel free to stop reading here and grab the image if you want to give this a go yourself. Spoilers are below.&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>The Charlotte Powershell Users Group meeting was held on Dec 5th. Jim put together a nifty challenge related to image manipulation. We started off with this nifty image. Pretty huh?<br><a href="https://powershell.org/wp-content/uploads/2013/12/stegan1.png"><img src="https://powershell.org/wp-content/uploads/2013/12/stegan1.png" alt="stegan1"/><br>
The challenge was to manipulate the image using PowerShell to find the hidden message. After some discussion, the code was cracked and the image was displayed. As is normal with Powershell, there were multiple ways to achieve the end goal. Feel free to stop reading here and grab the image if you want to give this a go yourself. Spoilers are below.</p><p>Here is one way to find the hidden message:<br>
add-type -AssemblyName system.drawing<br>
$height = $img.Height - 1<br>
$width = $img.Width - 1<br>
$img = [System.Drawing.Image]::FromFile(&ldquo;c:\temp\stegan1.png&rdquo;)<br>
0..$height | %{<br>
$y=$<em>;<br>
0..$width | %{<br>
$x=$</em>;<br>
$p = $img.GetPixel($x,$y);<br>
if ($p.r -ne 0) {<br>
$img.setpixel($x,$y,[System.Drawing.Color]::Green)<br>
}<br>
}<br>
}<br>
$img.save(&lsquo;c:\temp\update.png&rsquo;)<br>
Merry Christmas and Happy Holidays from your Charlotte Powershell Users Group.</p>
]]></content:encoded></item><item><title>PhillyPoSH 12/05/2013 meeting summary and presentation materials</title><link>https://powershell.org/articles/2013-12-09-phillyposh-12052013-meeting-summary-and-presentation-materials/</link><guid>https://powershell.org/articles/2013-12-09-phillyposh-12052013-meeting-summary-and-presentation-materials/</guid><pubDate>Tue, 10 Dec 2013 03:51:19 +0000</pubDate><description>&lt;ol&gt;
&lt;li&gt;
&lt;p&gt; &lt;a href="https://twitter.com/sunnyc7"&gt;Sunny Chakraborty&lt;/a&gt; gave an in-depth presentation on WMI Eventing using PowerShell. A copy of his presentation and scripts can be found &lt;a href="https://powershell.org/wp-content/uploads/2013/12/PhillyPosh_12_05_2014-Sunny.zip"&gt;here&lt;/a&gt;, and a &lt;a href="http://www.youtube.com/watch?v=h3V6K8ov1Ao"&gt;recording&lt;/a&gt; of his presentation can be found on our &lt;a href="http://www.youtube.com/channel/UCAc_ow5FIJtRpvew__9Iqzg"&gt;YouTube channel&lt;/a&gt;. If you want to learn even more about WMI, Sunny recommends checking out &lt;a href="http://www.lissware.net/"&gt;Alain Lissoir&amp;rsquo;s&lt;/a&gt; webpage and downloading he WSH and VBS scripts hosted on his site for the two books he was written: &amp;ldquo;&lt;a href="http://www.amazon.com/exec/obidos/tg/detail/-/1555582664/qid=1048198398/sr=8-1/ref=sr_8_1/102-5879685-5285706?v=glance&amp;amp;s=books&amp;amp;n=507846"&gt;How to exploit the power of Microsoft&amp;rsquo;s WMI to create mission-critical computing infrastructures&lt;/a&gt;&amp;rdquo; and &amp;ldquo;&lt;a href="http://www.amazon.com/exec/obidos/tg/detail/-/1555582990/qid=1048198398/sr=8-2/ref=sr_8_2/102-5879685-5285706?v=glance&amp;amp;s=books&amp;amp;n=507846"&gt;Leveraging Windows Management Instrumentation (WMI) Scripting&lt;/a&gt;&amp;rdquo;&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<ol><li><p> <a href="https://twitter.com/sunnyc7">Sunny Chakraborty</a> gave an in-depth presentation on WMI Eventing using PowerShell. A copy of his presentation and scripts can be found<a href="https://powershell.org/wp-content/uploads/2013/12/PhillyPosh_12_05_2014-Sunny.zip">here</a>, and a <a href="http://www.youtube.com/watch?v=h3V6K8ov1Ao">recording</a> of his presentation can be found on our<a href="http://www.youtube.com/channel/UCAc_ow5FIJtRpvew__9Iqzg">YouTube channel</a>. If you want to learn even more about WMI, Sunny recommends checking out<a href="http://www.lissware.net/">Alain Lissoir&rsquo;s</a> webpage and downloading he WSH and VBS scripts hosted on his site for the two books he was written: &ldquo;<a href="http://www.amazon.com/exec/obidos/tg/detail/-/1555582664/qid=1048198398/sr=8-1/ref=sr_8_1/102-5879685-5285706?v=glance&amp;s=books&amp;n=507846">How to exploit the power of Microsoft&rsquo;s WMI to create mission-critical computing infrastructures</a>&rdquo; and &ldquo;<a href="http://www.amazon.com/exec/obidos/tg/detail/-/1555582990/qid=1048198398/sr=8-2/ref=sr_8_2/102-5879685-5285706?v=glance&amp;s=books&amp;n=507846">Leveraging Windows Management Instrumentation (WMI) Scripting</a>&rdquo;</p></li><li><p>Announcements:</p><ul><li><p>January&rsquo;s meeting will be on the 2nd Thursday (<em><strong>01/09/2014</strong></em>) of January as opposed to the       1st</p></li><li><p>Since we didn&rsquo;t get to last months homework assignment we are pushing it to January&rsquo;s meeting. Here it is again and hopefully this will be a fun task that we can discuss during our next meeting:</p></li></ul></li></ol><pre><code>&gt; **Title**: On This Day in Pictures
&gt; **Description:** You have folder of photos on your computer that you take with your Smartphone or digital camera. From time to time you want to be reminded of the cool and interesting things you snapped photos of years before on this day. Being a PowerShell scripter you imagine that PowerShell would be a quick and easy tool for exploring your photo's meta-data to re-discover some fun memories you had by emailing yourself some pictures you took on this same day last year or any year before. You decide to format the email as HTML including the pictures and some data about them. Finally, using the task scheduler to set your script to run every morning so you can take a trip down memory lane with your photos on this day in history. As a PowerShell scripter you roll up your sleeves and get to work.
&gt; **Requirements:**
&gt;
&gt; 1. Your script should look into a directory that may contain sub folders for image files (you may want to support .jpg, .jpeg, .png, etc.).
&gt; 2. The script should then determine the date a photo was taken. Examining the [EXIF][8] meta-data might be handy.
&gt; 3. Get the date the script runs and find all the photos taken on the same day other than the current year.
&gt; 4.  Finally send an email containing the photos taken on this day in history*</code></pre>
]]></content:encoded></item><item><title>Scheduled site downtime</title><link>https://powershell.org/articles/2013-12-02-scheduled-site-downtime/</link><guid>https://powershell.org/articles/2013-12-02-scheduled-site-downtime/</guid><pubDate>Mon, 02 Dec 2013 22:13:41 +0000</pubDate><description>&lt;p&gt;Windows Azure has advised us of scheduled downtime on Friday, December 6, from approximately 15:00 hours (US Pacific) until approximately midnight Pacific time.&lt;/p&gt;</description><content:encoded>&lt;![CDATA[<p>Windows Azure has advised us of scheduled downtime on Friday, December 6, from approximately 15:00 hours (US Pacific) until approximately midnight Pacific time.</p>
]]></content:encoded></item></channel></rss>