Search
Generic filters
Exact matches only
Filter by Custom Post Type

PSDayUK 2018 - The UK PowerShell Conference

Jul 17, 2018
0

Hi all just a very quick post to point you to another post about the UK's PSDay conference happening on October 10th 2018.

We have an active call for speakers running for the next two weeks and  have some tickets already released,

For more details please see https://blog.kilasuit.org/2018/07/17/psday2018-info-share/

 

Many Thanks

Ryan

UK Powershell User Groups Lead and Cloud & Datacenter Managament MVP

Looking for a PowerShell.org Contributor

Jun 22, 2018
0

We're looking for someone who can publish a regular "What You Missed This Week" blog post on PowerShell.org each Friday (excepting the odd week off for vacations, of course).

This is meant just as a roundup of interesting posts from around the web; we know tons of people are blogging in their own spaces, and we'd like to call attention to some of the more noteworthy ones.

This isn't any more complex than a brief blurb for each:

Don Jones shares the beginnings of PowerShell Summit: How PowerShell + DevOps Global Summit Began

PowerShell.org's OnRamp Scholarship needs your help spreading the word: We Need Your Help.

There's no minimum or maximum each week, although I personally suspect more than a couple of dozen posts will overwhelm people. The idea is to curate what's out there, introduce folks who are getting their blogs going (and encourage them to keep going), and give the community some variety in its PowerShell diet.

If you're interested, drop a line to webmaster@powershell.org to get hooked up with blogging rights here. As you do so, indicate if you're up for every week (preferred) or every-other (in which case we'll try and find two of you and get you to split even- and odd-numbered weeks). You can also volunteer to be an "aggregator," feeding noteworthy articles to our main round-up-person each week to help them out.

If you've been longing to contribute but haven't thought of a way, this could be a high-impact, low-workload way to jump in and help out!

Can We Talk About PowerShell Core 6.0?

Microsoft recently announced the General Availability (that is, a non-beta release) of PowerShell Core 6.0. A companion document detailing breaking changes, along with some of the language in the announcement, has led to more than a few inquiries in my mailbox. Most take the tone of, "have I been wasting my time learning PowerShell?!?!?" because, at first glance, PowerShell Core looks deeply less functional than its predecessor. Let me tell you what I think.

Read more

PowerShell 2.0 deprecation

PowerShell 2.0 is being deprecated - see the PowerShell Team blog for full details

PowerShell + DevOps Global Summit Scholarship Program

Automation and scripting has become a major part of IT in recent years.  And PowerShell has played a giant role in the progression of that.  Every year, the wonderful people at PowerShell.org put on the PowerShell + DevOps Global Summit, that always produces outstanding results from amazing speakers and attendees.

As many of you in IT know, convincing your manager to attend conferences usually depends on a few key factors: Cost and budget, content, and sometimes, experience or seniority in the company.  And unfortunately, that last one may be a deciding factor far too often.  This year, PowerShell.org is making it a priority to help extend, not only the content and knowledge that comes with attending the PowerShell + DevOps Global Summit, but also the experience that comes along with it.  

PowerShell.org is looking for a few driven, over achieving PowerShell-ers, that may still yet be all too green in their company or role in IT to convince their superiors to send them to the PowerShell + DevOps Global Summit.  To be considered for this scholarship, we are particularly looking for individuals that would be considered part of a group which is "under represented" in the IT industry as a whole, including women, underrepresented minorities, and so on.  So, if you're the IT Director, or the Senior Systems Architect, this opportunity is not for you; however, if you are in those roles, and you know a real go-getter that has shown you some cool stuff they have done with PowerShell, please point them to this opportunity.

It's also worth noting that this specifically isn't for people in the situation of, "yeah, I do this stuff all the time and my employer should totally send me and they totally aren't." We're looking more for, "I'm working way above my pay grade and this might help give me the jump I need to get to a better place in life." That's the kind of thing you'll have to help us understand about you in your application. This scholarship isn't just to take a burden off your employer or net you a free trip to Redmond; it's to help someone raise themselves in life.

 

Applying

If you feel you fit the bill for this scholarship, you need to convince us!  We want to hear why you are the Chosen One.  So, if you’d like to be considered for the opportunity you will need to write an essay that demonstrates your passion for PowerShell and automation.  When constructing your essay, please use the following guidelines:

  • Demonstrate an intermediate or better understanding of PowerShell,  Scripting, and ToolMaking (If you’ve read Don Jones’ Learn PowerShell in a Month of Lunches, you should be fine).
  • Include specifics.  Site specific example on how you have used PowerShell to save your company a bunch of money, or how you’ve done something amazing.
  • Include examples.  We DO NOT want a submission that is just a script, but please include some clever snippets that you are proud of.
  • Have you shared your work, or made it reusable?  Please include information on how we can find it if you have.  The PowerShell Community is one of the best ones around, and we all love sharing code.
  • Be thorough.  We don’t have a hard word count,  but remember, the best essay wins!
  • Assure us that, should you be awarded this opportunity, you've spoken with your employer and getting the time off won't be a problem.

 

How We'll Decide

  • Applications can be submitted HERE (Google account required to apply).
  • We will be accepting applications from Friday, September 1st 2017 until Sunday, October 1st 2017.
  • The winner(s) will be selected based on the quality of their essay and the enthusiasm it conveys (make us want to keep reading).  Again, we are not looking for the seasoned PowerShell veteran that has been to the Summit the past four years, but the help desk analyst that has been using a collection of tools and scripts they created that is allowing them to be four times as productive.
  • The winner(s) will be chosen by a panel of four judges who are all very active members in the PowerShell community.
  • The winner(s) will be announced Wednesday, November 1st 2017 on PowerShell.org

 

What Awardees Receive

  • Up to $500 in airfare.
  • Four hotel room nights.
  • Full admission to the PowerShell + DevOps Global Summit.

Help Get the Word Out on the 'GetGoing' Program & Scholarship

Apr 20, 2016
2

PowerShellPodcastA couple of weeks ago, DevOps Collective (PowerShell.org's parent non-profit organization) announced the availability of the 'GetGoing' IT Ops Education Program and Scholarship.

For those of you who may not have yet heard, DevOps Collective and Pluralsight have partnered together to create a modern 'turnkey' curriculum that brings together mapped courses, recommended hands-on experiences, and live mentoring to prepare people for the real-world of IT Operations.  With this initiative, they've offered up to full-ride scholarships for 2016.  Applications for the scholarship have opened, and applications will be taken in until May 15th.

Now that the way has been paved, it's our turn as members of the community to get the word out; and doing so might be easier than you think!

Contact Your Local School Districts

I recently reached out to my hometown public school district, and was immediately met with enthusiasm from the local superintendent and their Science, Guidance, and Counseling departments.  It only takes a quick email with some bullet points on the program to get the conversation initiated.  I've included the text of my initial correspondence for you to use as a guide to help you on your way.

Contacting your school district is easy.  A quick search online for your district can get your to their website with contact info, often including the email addresses for the district superintendent and other office officials that can help!  Send them a copy of the brochure to help them get informed of the initiative.

Use Your Social Media Skills

Get the conversation going on social media!  Talk to your followers; speak out to local educational organizations; and make them aware of this awesome new program!

Inform Your User Groups

Get your user groups in on the action.  Enlist the greater community to get the word out faster!  Together we can canvas an even larger area and get more people interested!

Get Involved

Offer to become a mentor.  We all know that the best way to learn is from real world experiences.  We, as a community, have this vast repository of practical knowledge that no book can effectively provide.  We, as a collective resource, can help to bring a new generation of administrators, engineers, and architects into this world already prepared to take on DevOps, Agile IT, and more!

If you need a hand getting started, feel free to contact me at webmaster at powershell.org.  Now let's #GetGoing ourselves, and make this happen!

Here's my initial contact email that you can use to fit your own story:

Greetings [Contact Name],

I hope this email finds you well.

My name is [Your Name Here].  I'm a native to [City], IT Consultant, and an industry/community leader in Cloud and Datacenter Management.  I teach PowerShell for free to people in the community that have an interest in the technology at user groups in [location[s]].
I also do volunteer work for the DevOps Collective; a 501(c)(3) organization that is dedicated to creating conversations, improving connections between practitioners, and further develop the DevOps state of the art.
Recently, DevOps Collective announced the new “GetGoing” IT Ops Education Program & Scholarship.  More on the program can be researched here, but I thought I'd offer some of the bullet points on the major educational objectives that form the basis of the program:
  • Core understanding of business IT environments, including the various components that commonly form the business technology infrastructure.
  • Basic networking essentials, including client configuration and troubleshooting.
  • Essentials of business technology security.
  • Essentials for technology troubleshooting, including methodologies and patterns.
  • Essentials of virtualization technologies.
  • Help desk essential skills, including Microsoft Office basics, customer interaction, ticketing systems, and process-following.
  • Desktop support essentials.
  • Server support essentials.
  • Windows client operating system fundamentals, including client and server administration fundamentals.
  • Windows PowerShell fundamentals, including the use of PowerShell for core help desk tasks.
  • Fundamentals of Microsoft-based databases, collaboration, and messaging technologies.
Finally, DevOps Collective has partnered with Pluralsight to offer two full-ride scholarships.  One is a general availability scholarship, and the second is a diversity scholarship being offered to groups that underrepresented in IT in the United States.  The scholarship has a total value of approximately $11,000 dollars and includes:
  • Full access to a Pluralsight turnkey curriculum, giving you all the education the model curriculum specifies.
  • A paid mentor, who will check-in weekly with each student.
  • Paid-for hands-on experiences, including Azure time, predesigned hands-on labs, and even a build-it-yourself kit PC that students get to keep.
  • Practice tests, knowledge checks, and other supplemental materials.
  • Paid-for certification exams – students only pay if they need to re-take a test.
As a leader in the IT community with strong ties the [city], I feel that this is an important conversation that we need to have for the children of the city.  I grew up [your story].  I have enjoyed much success in my career in Information Technology, and I would love to see today's [school district] students empowered to become tomorrow's technology successes.
Please feel free to contact me if you have any questions.
Best Regards,

Microsoft's Brave New World Needs Version Numbers

In Microsoft's brave new world of agile, more-frequent software releases, including numerous pre-release cycles... Microsoft needs to rethink the way it communicates versioning.

Windows Management Framework (WMF) v5 has, for me, been pretty much the perfect example of what not to do, and the perfect example of Microsoft still shoehorning itself into old nomenclature that no longer fills the bill. I know a bunch of folks on the PowerShell team are probably still trying to figure out what works, too, so this isn't meant to be a hammer-on-'em post, but WMF5's lifecycle was, from a versioning perspective, pretty hellish.

We had several "technology preview" releases, which were simply named after their month of release. April 2015. November. Whatever. It was really difficult from within the product - e.g., via $PSVersionTable - to tell which one you were running, which made helping people difficult. None of these were supported in production until the "WMF5 Production Preview" released in late 2015, and in December we got "RTM" code. RTM means "Released to Manufacturing," which is kind of absurd as a milestone, because there's literally zero actual manufacturing going on. It's just a word Microsoft is used to using. Windows 10 shipped with a production-supported version of WMF5, but it still wasn't "final," meaning RTM WMF is better than what shipped with the RTM OS. God willing, what ships in Windows Server 2016 will be v5.1 or something, because if we get yet another 5.0 release folks are going to start throwing up their hands and quitting.

Now that Microsoft's all lovey-huggy with open source and Linux and stuff, can we just copy what those guys do?

Every time you release code, increment the version number. It's that simple. There's no "production preview," there's just "5.3." And you maintain a list of what's supported in production. If 5.3 isn't a production milestone, fine - say so. But it's still a real version, because it was released unto the world. The next release is 5.4. Then 5.5. And maybe 5.6 is supported in production, but once 5.7 is out, 5.6 remains supported for only 90 days. Or whatever. Just have a list of what's supported, and increment the version number every time you release it. 5.8 might only last a week before someone finds some heinous bug and releases 5.9 - that's fine. After that comes 5.10, and then 5.11, and so on.

6.0 is the first release of a major new evolution in the product, and it's probably a "preview" release. 6.1 will be a bit better, with fewer bugs and more features nailed down, but it won't be until maybe 6.5 that we get a "supported in production" release.

All of this is a lot easier to keep track of than vague "version" numbers like "April 2016 Production Preview."

And while we're at it, let's have a Get-PSVersionInfo cmdlet. It can wrap around the existing $PSVersionTable variable, of course, but it can also ping a web service on Microsoft.com to tell you what the latest version is, what the latest supported version is, and whether or not your current version is supported in production. OMG, that would be wonderful. 

PS C:\> Get-PSVersionInfo

Name                   Value
----                   ------
PSVersion              5.8
ProductionOK           False
LatestPSVersion        6.0
LatestProductionPSVer  5.9

This tells me that I have 5.8, and it isn't supported in production at this time. I can get 5.9, which is supported in production, although there's a newer 6.0 which obviously isn't supported in production.

So please. Vote for this on UserVoice.

Monday Night: PowerScripting Live with Jeffrey Snover & Friends!

The PowerScripting Podcast is pleased to announce:

PowerScripting Live with Jeffrey Snover & Friends!

Date: Monday, Nov 2, 2015

Time: 6 PM - 7 PM PST (1 hour)

Location: the Auditorium at the Hyatt Bellevue in Bellevue, Washington & live streamed at Crowdcast!

Agenda

The PowerScripting Podcast is live from the Auditorium at the Hyatt Bellevue! Join us in person if you are at the MVP Summit; this event is conveniently close to the MVP reception held immediately after. The event is a live Q&A interview with Jeffrey Snover, Technical Fellow & lead architect of Windows Server & System Center. He is joined on stage by PowerShell MVPs Tobias Weltner who will introduce ISESteroids, and Tome Tanasovski who will talk about Flancy--two projects you don't want to miss! Read more

Want to Blog at PowerShell.org?

PowerShell.org was never meant to be a small group of people doing good - it was meant to be a place where all of us can do good for each other. And that's why everyone is invited to blog here. 

Yup, even you.

If you'd like blogging permissions added to your account, just e-mail webmaster@ with your site username, and we'll make it so. Now, I do realize that a lot of folks would much rather blog in their own space, and that's totally, 100% cool. But, if you'd like to blog here, we only have a few rules.

Your Content is YOUR Content

If you ever decide you don't want to blog here anymore, we'll be happy to export your articles (in whatever form WordPress supports at the time) and give you that archive. You can then do whatever you want with your content.

Minimize Dupli-Blogging

We ask that, if you post an article here, that you not also post it in a ton of other places. This isn't an "exclusivity" thing at all - it's that search engines like Google "penalize" sites for carrying duplicate content, and that would make it harder for people to find other resources that we offer here.

That said, you're more than welcome to write a post elsewhere, and then write a shorter, "introductory" post here, pointing to your "main" article elsewhere. That's absolutely OK. We just ask that the shorter post you submit here be entirely original - that is, not just an excerpt of your longer post, but something uniquely written for this site. Again - that's just us trying to be square with the Goog.

For example, you might write a quick "tip" article here that offers someone genuine learning value, and then point them to a longer article that includes additional, related material on your own site.

That's It

PowerShell.org is meant to be a service to you and to the entire community. We get over 200,000 hits a month, so we're a pretty decent place for your writing to get more exposure - and to help more people. But we also want to be a respectful player in the community, so aside from the above ground rules, we really don't want to restrict you or ask you to do something that might not be good for you. 

Well, Also This

We've also created some generic artwork that you can set as the "Featured Image" for your post. When your post is fresh, it'll cycle through the front page of PowerShell.org in the "carousel" at the top of the page. Having an image makes it a little sexier. Just click "Set featured image" and then choose one of the media items we've provided. You'll find them in the Media Library from December 2015 (there's a drop-down list to filter to that month).

We look forward to hearing from you!

I need YOUR PowerShell Stories

Jun 30, 2015
0

We all love PowerShell and we all probably have some very entertaining stories about a situation where it really saved our butts (or caused problems). Either way, we can all tell some kind of interesting story around a memorable moment you had with PowerShell or automation in general.  I'd love to hear about them.

I'm looking for a short story anywhere from a few paragraphs to an entire article if you want.  The more detail the better. What kind of situation were you in? Were you under a deadline and PowerShell saved the day?  Did automation backfire in your face and you blew up your whole datacenter?  I want to know about it!

If you have any stories around PowerShell please send them to me by contacting me via my blog's contact page.  I will be editing and collecting them all up soon and putting them all into a community eBook here on powershell.org as well as my blog. If you don't want your name attached to the story let me know.

The deadline for submissions is 7/31/15.

I look forward to reading your contributions!

- Adam Bertram

Skip to toolbar