PowerShell articles, tutorials, and guides from community experts.
Voting is now open!
As of this morning you can vote for the sessions that you want to see at the 2013 PowerShell Summit! We have 97 session proposals (see below), plus additional content from the PowerShell Team. Your vote is really important, so please take some time to indicate what you would like to see from a PowerShell-specific conference with deep technical depth.
Here"™s what you need to do:
Voting is open!
As you know, the PowerShell Summit North America 2013 is coming in April 2013, and we’re relying on you to tell us what sessions you’d like to see there. We’ve already accepted dozens of proposed sessions, and we’re ready for you to vote.
Go ahead and take the survey now. (opens in a new window/tab)
While voting, you can technically choose as many sessions as you want - but remember that we can’t present them all, so try to pick no more than 20 sessions as your “favorites.” Also note that the Summit will include additional, to-be-announced sessions presented by Microsoft employees and PowerShell product team members.
You can read the session proposals’ descriptions in our forums; we suggest having that open in another window right next to the survey itself. That way, you can read through the abstracts, decide if you like a session, and vote on it in the survey. Sorry for having the information in two places - we’re gonna work on something cleaner for 2014 ;).
**You have until midnight October 28th, 2012, to vote. **And if you’re asking, “midnight in what time zone,” then we suggest you stop procrastinating and vote already!!!
Our inaugural meeting was as follows:
On the topic of deploying a GPO to set your script execution policy, Bhargav Shukla from the Philadelphia Exchange User Group brought to our attention KB2467565 which address the following issue:  “You cannot install an update rollup for Exchange Server 2010 with a deployed GPO that defines a PowerShell execution policy for the server to be updated”. So if you do set the script execution policy through group policy don"™t apply it to your Exchange 2010 servers!
Meeting materials zip file: PhillyPosh_2012-1004
Oisin and I have been busy prepping the PowerShell Community Extensions to support Windows PowerShell 3.0. With this release, we are providing two packages. There is a Pscx-2.1.0-RC.zip that is xcopy deployable just like PSCX 2.0. Just remember to unblock the ZIP before extracting it otherwise you"™ll get errors when you try to import the module. Pscx 2.1 can be used to target both Windows PowerShell 2.0 and 3.0. In order to do this, Pscx 2.1 is still compiled against .NET 2.0 and it can"™t take advantage of any Windows PowerShell 3.0 specific features.
In case you haven"™t heard already, there is a great opportunity to learn a lot more about PowerShell coming up next year. It"™s the PowerShell Summit North America 2013 conference, and it is held on Microsoft campus in Redmond, WA from April 22 to 24, 2013. This conference is run by the PowerShell.org community, and it will present a ton of deep technical content on anything to do with PowerShell. What content will be covered, you ask? Well, that"™s up to you.
What’s the average tech conference cost these days? $1500? $2000? And that’s just to get in, to say nothing of hotel, air, food, and whatnot.
The PowerShell Summit North America 2013 has an idea. Lets do a community-owned event, with a goal of breaking even and supporting an annual event, but not worry about a profit.
Lets say you live in the US. A ticket to Seattle in April will run you $500-700 after taxes. Maybe less if you can get on a discount carrier like Southwest - they fly to SEA. Hotel will run you under $450 for three nights. Say you decide to splurge on a car for four days, probably for under $200 (including all the ridiculous taxes on rental cars). Toss in another $250 for food? That takes you to under $1600. PowerShell Summit only costs $550 - less if you register during one of the Early Bird tiers; as low us $450, in fact. That’s $2100-2200 total, or just a bit over what some conferences charge for their registration fee alone!
What about quality? Well, you’ll get the same food Microsoft employees get. So that can’t be all bad. You’ll attend sessions delivered by Microsoft product team members, along with independent experts. You’ll interact directly with PowerShell team managers, too, in a small-event format that lets you provide product feedback directly to them. Heck, with under 100 fellow attendees, you’ll get plenty of face time with everyone.
It’s going to be a great event, and it will definitely be affordable. It’s being run by members of the community, not a conference company. This will hopefully become OUR event, an annual gathering of PowerShell enthusiasts, experts, and team members. A chance to network, to learn, to share, and to grow.
I hope you’ll be able to join us!
When Kirk Munro and I set this site up, and started redirecting traffic from the old PowerShellCommunity.org, one of our main goals was to make this a truly community-owned resource. We wanted it hosted independently (my company, Concentrated Tech, is being paid to host the site, so we get pretty good service and total control). We didn’t want to be beholden to anyone’s commercial interests or whims (companies do get distracted by their real jobs from time to time, after all).
When we started talking to Microsoft about holding a PowerShell Summit, we wanted that to be community-owned too, and not tied to a commercial interest - in part so that we could keep the price low, but also so that Microsoft would be able to support us without getting into any possible conflicts of interest with any of its ISV partners.
Today, our intention becomes legally realized. PowerShell.org., Inc., a Nevada corporation, is born - and we’re offering ownership shares to help raise capital. This capital will be used to pay for necessities like bookkeeping, and also to help bootstrap the Summit event. Shareholders are _legal owners of the corporation, _and will vote for its Board of Directors - who in turn appoint the Officers that make things happen. Our first Board will consist of myself, Kirk, Jeffery Hicks, Richard Siddaway, and Jason Helmick.
**Want to become a community owner? **You’ll want to start with our “Shareholder Brochure,” which is available in the new “PowerShell.org, Inc.” forum on this site. That forum will also get you our Bylaws and Articles of Incorporation; the Brochure will outline the purpose of the corporation, and explain what it means to be a shareholder. The forum also contains the Share Purchase Order form, which you can use to purchase shares, and contains documents that outline our initial Board of Directors and Officer lineup and other important details.
That’s right, for just $400 you can guarantee yourself a seat at the PowerShell Summit North America 2013, to be held at Microsoft’s campus in Redmond, WA. Just 10 tickets will be made available at this low-low-low price, which is $150 off the normal registration rate.
Why so low? Why are they called “I’m Feeling Lucky” tickets? Because while we’re committed to an April 2013 date, we haven’t actually locked in dates with Microsoft, yet. So to purchase these, you’ve got to be feeling flexible… or lucky!
But it’s not a marriage. The tickets are completely refundable, up to 30 days prior to the event. So if we manage to lock in the three dates you can’t attend, we’ll give you your money back. You can also transfer the ticket to someone else, at any time (although they’ll be paying you directly for the ticket, and we won’t get involved in that transaction).
Once these sell out, or we lock in our dates, we’ll commence the Early Bird period, with a rate of $475 and just 30 tickets available. That rate will be good through the end of December, unless we sell out. Full rate of $550 kicks in after that, when we’ll sell the remaining tickets to fill our roughly 100-person venue.
Thinking about presenting? Start submitting topics in the Forums! You can get all the other juicy details on the Summit’s dedicated site, and catch the Summit’s Twitter feed for ongoing announcements.
Microsoft recently posted the online help for PowerShell v3 Workflow (http://technet.microsoft.com/en-us/library/jj134242), and I wanted to take an opportunity to explore some of what the help says - and perhaps offer an outsider’s perspective.
Workflow is a set of technologies included with PowerShell v3, and is available on any computer running v3 (which can include Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows 8, and Windows Server 2012). A workflow is a special kind of PowerShell script that looks a lot like a function. When run, however, PowerShell translates the workflow to Windows Workflow Foundation (WWF) code, and hands it off to WWF to execute. That means the contents of a workflow are a bit different than the contents of a script.
This is a free e-book that covers PowerShell Remoting. There’s a brief overview and tutorial of actually using Remoting, but that part isn’t in-depth. What this e-book provides, that you won’t find elsewhere, is step-by-step, screenshot-based instructions for configuring Remoting for any imaginable scenario. You’ll also find troubleshooting tutorials and examples, and even information on how to explain Remoting to your corporate IT security team. It’s all the stuff that isn’t documented in PowerShell’s own help - and it’s completely free. You don’t even need to register to download the file!
Try adjusting your search terms or browse all content.
