Be a Part of PowerShell History (Please!)

I’ve decided to embark on what will doubtless be a months-long project: a book that covers the history of PowerShell, from its earliest inception to the shell we all know and use today. But I want to do more than just document the dry facts: I want to capture the impact.

I’m going to be working with some of the earliest Microsoft team members who worked on PowerShell, so that part’s covered. But Microsoft’s end of things is far from the whole story: how PowerShell impacted its users – that’s you, perhaps – is just as important.

So here’s what I’d love for you to do: drop a comment below. Tell me how you reacted to PowerShell. Tell me how you found it, and what your initial experience was. Tell me how PowerShell grew (or didn’t) for you, and describe any real turning points you came to. If PowerShell made a change in your life, tell me about that. As much as possible, give me a time frame for your comments – at least approximate years – so I can work your comments into the overall chronology.

I’d even love comments about your pre-PowerShell life. Did you use KiXtart or VBScript? How’d that work out? Was automation not a thing for you prior to PowerShell? If not, what was your working life like? Some contrast between “the way things were” and “the way things can be” is an important element of the overall narrative I’m trying to construct.

Your comments may be used in the final book, so by posting here you’re giving implicit permission for me to use your text. I’d appreciate you including your first/given name, if you don’t mind doing so.

And I’d also appreciate you spreading this post as far and wide as possible, so that I can get as much input and “color” as possible.

Thank you!

26 thoughts on “Be a Part of PowerShell History (Please!)

    1. jean gruneberg

      Apologies for the wall of text. 2014 failed a security audit from our regulator, most servers were at least 4 years out of compliance. Total environment is somewhere around 10 – 14 Dev/QA labs spanning about 1000 servers and Prod with around 400 servers. Due to the complexity of the systems and the amount of patches to apply; some decision were taken early in the process. We would only use 3 labs as test labs before going to Production. We obtained business and regulator sign-off for a 60 day cycle (1x 4 hour window every 60 days) – our business is highly susceptible to financial loss – 1 hour outage equates to roughly $1 million lost.

      We ran through the labs the first time, applying only critical patches and only as many as we could deploy in a 4 hour window, still took me nearly 5 days to patch the 3 labs. First run into production, 6+ staff from Data Centre, sys admins and DBA’s manually logging into servers, stopping services and rebooting. 72 hours of effort over 2 outage windows. This was silly and not sustainable.

      Decided to Automate the process with PowerShell. Build out of initial ‘simple’ PowerShell scripts that would stop application services, stop DB services, reboot DB’s, start DB services, reboot App servers, start app service………………. Scripting also had to take into account, sequences of bringing services back online in specific order within our software stack. We constantly refined the process and scripts to the point we could patch Staging (160 servers) in a 1.5 hour window.

      As automation really started to produce time benefits – we rebuilt the plan for Prod – moving to 2 outage windows per month; 1 non site / player impacting (4 hours) and 1 site / player outage window (4 hours).

      Currently patching window is handled by on-call SysAdmin and DBA manually kicking off about 15 PowerShell scripts in a specific order. We patch current 11 Dev/QA labs and Casino Production with all MS OS patches on a 30 day cycle. Total of < 3 hours of effort to patch Prod each month, approximately 10 hours to patch all labs each month. Using current scripts, we are building these into Jenkins pipelines. Then finally automation of Production patching via scheduled task in Jenkins to run the patching pipeline – free up staff time as they won’t have to manually run the process – from 72 hours of effort to 0 hours per month?

      Maybe…..

  1. Brian

    2002 – 2005: Doing a mix of help desk, Windows, Netware, and Linux administration at an arts organization, doing everything from install printer drivers, to writing Perl scripts to automate tasks on our Linux servers.

    2005 – 2015ish: Move to a large university to become their Exchange admin. When 2007 rolls around, I’m pleasantly surprised at how much I enjoy using Powershell and the ease of administration that comes with it. I become known as a ‘Powershell guy’ and script writing becomes a regular part of my job. The limited scope of the job starts to wear on me until…

    2016-Present: the university kicks off the Office 365 migration project. I’m no longer the Exchange admin. Now, I straddle the line between admin and dev. I level up my skills and treat writing code with a seriousness I hadn’t employed before. Writing modules, unit testing, creating in-house standards, and setting up a dev pipeline for the Windows team occupy large portions of my time. I contribute code the migration project as well as replacing legacy code for onboarding, license management, and many, many more. Then I begin training coworkers, helping them move away from the ‘clicky-click’ module of administration.

    Don’s books, the Powershell Summit, and a large community of Powershell users that share their knowledge had a huge impact on my career. From financial, personal/career growth, to job satisfaction, Powershell has had a huge, beneficial impact on my life.

  2. Chris Thomas

    I started learning PowerShell around 2012 or so, but never found a real good use for it with my day-to-day job at the time. It wasn’t until my school district decided we’d buy $1.4 million worth of iPads, well before Apple had any sort of tools to help that work at scale, that I saw real value in PowerShell for myself. The Apple ID creation and verification process was very manual. I asked for time to sit down and write a script to try and do it for us and was allowed to. It took my longer than I care to admit, but I cobbled together a script that would reach into the generic Apple ID exchange mailboxes we had setup, look for the most recent email from apple, use the verification link to browse to the website, tab around (because I didn’t know how to work with webpage elements at the time) and fill in the appropriate stuff and then verify the Apple ID. We ended up letting it run for a weekend and it did a couple thousand Apple ID’s with very little interaction or errors. I was pretty proud of it (https://github.com/chrisATautomatemystuff/presentation-examples/blob/master/AppleVerification.ps1). This was around 2014 I did that.

    I’ve been in K12 IT since 2000 and I was always the type of tech that would memorize the number of tabs, arrows and enters to proceed through the Next-Next-Finish type installers when I’d have to install it on a lab of 30. This was before I had an automation mindset. A little later in my career I had my ‘batch cheat sheet’ with commands I had learned and I’d write batch files so I could login to computers and just ‘run -> x:\a.bat’ and made life easier. Later I discovered psexec and was thrilled to not have to leave my seat to accomplish tasks around the school district. I still struggled with HOW to execute some things on remote machines though. Once I saw PowerShell though I fell in love because the syntax was so easy to understand with some practice.

    At this point in my career, I don’t even care what the technology is … VMWare, SharePoint, Google, RESTful API … if I can work with a SME on that topic I can help them write PowerShell to make their lives easier. It’s an amazing tool!

  3. Jayson Bennett

    Just previous to getting very interested in PowerShell, I had just started working at a children’s hospital as an AD/Systems administrator. My first project was to go through all of the accounts and determine which ones had not logged in for 30 days and disable them all. At that time there were 20,000 users in the AD environment and I really didn’t want to go through them all by hand.

    In doing a bit of research, I found out about all of the cool things that PowerShell could do when it came to AD. I signed up for Jason Helmeck’s class based on Learn PowerShell in a Month of Lunches, and dove in head first. I returned from his class and was able to come up with a script that went through every active user to check the last logon date and disable everyone that had not logged in for 30 days then move them to a disabled users OU. Without PowerShell, that project would have taken me weeks to complete.

    As far as I know, that script is still running weekly on a scheduled task nine years after I wrote it.

  4. Karen Flores

    My story with Powershell is tightly coupled to Azure. Long time ago, when I started working with Azure powershell was one of the first tools that I used to interact with Azure. Over the years, I have enjoyed the evolution of the cmdlets, specially, Azure cmdlets. Azure cmdlets make my life so easy, initially, by helping me to build scripts for provisioning a few resources,and ,later, by providing a way to build one-click-deployment of complex environments with many resources. Powershell has helped me in the automatization of many tasks and I just love discovering new features. I love how Azure and Powershell have evolved to bring more functionality over time. Powershell is my number one tool whenever I need to script something in Azure.

  5. P. Fierlafijn

    Powershell has roughly overtook my professional life as system engineer. I was working with a small group of colleagues in at a federal administration that needed a lot of automation to work efficiently. We where only as much that the daily routine jobs made automation moved automation to a corner and was something we did when time was left.
    VBScript would have been the language of choice, if it was that I didn’t like the language. So I used JScript instead. However I still struggled to efficiently implement what I needed too. The link between the systems and the languages seemed to be too week.
    Around 2007, I attended Techdays, where was promoted Powershell. I was thinking, this is again a 1 day wonder product that would never last. But I was intrigued, because the functionality that was demonstrated, was exactly what we needed to automate.
    After a while, and several other encounters with the evangelists of Powershell, I tried to find some materials to understand the world of Powershell. After a while I stumbled on the Microsoft Virtual Academy series about Powershell. Jason Helmick and Jeffrey Snover (yes, the father of Monad that became Powershell) did explained Powershell with such enthusiasm and exactly what I needed, that this was the real start, for me, to love and use Powershell intensively.
    Along the way I learned about Powershell, I was inspired by some other great minds like Ashley McGlone and… Don Jones. All these people and the evolution of Powershell has made me, who I’m now. A respected system engineer with a catch phrase: With Powershell it is possible to do this 😀

    So, I believe that Powershell has made my career worthwhile and now that this help you form a picture of a fully converted Powershellee.

  6. Ralph

    Back in the days, I was doing lots of Kix and – like everyone – VBScript.
    I started working with PowerShell when it was still called Monad, and I was immediately in love with the uniform and structured way cmdlets worked.
    It took a while to stop creating VBScript-like PowerShell scripts, but I guess all of us went through that stage (and some are still in that stage):-).
    The fact you can now do ‘almost’ anything in any environment with PWSH is the biggest win to me.
    I keep urging and teaching colleagues to fully embrace PWSH.

  7. Darren Rolfe

    I was assigned a project in 2015 to work with a financial company in the UK. The project was to implement Server Core. It was my role to technically advise the Project Management Team on how this could be implemented. As part of this I was to train the companies 1st and 2nd line support teams on Server Core. As anyone will know Server Core does not have a GUI. It made sense therefore to use PowerShell to communicate with the Server Core systems. It was my responsibility to train all of the 1st and 2nd line support teams to use PowerShell. I put together an hours lesson on the nuts and bolts of PowerShell including Remoting. I wrote all of the cmdlets into a text file so the students could practice in their own time after they had attended the training. I subsequently used that material in other projects where engineers needed PowerShell knowledge. I even used it when delivering a Windows 10 workshop in Lithuania.

    I joined a new company where there was approx. 60 level 3 support engineers. The vast majority of who did not have PowerShell experience. I took it upon myself to train them. By this point, the nuts and bolts session was about 90 mins long and the Remoting session almost 2 hours. I decided to write some training on PowerShell Scripting. This I delivered to much appreciation.

    In my next company, again I needed to train engineers on PowerShell (anyone notice a pattern yet?). So I took them through the three training sessions. I started to write a fourth training session on Desired State Configuration. That is still a work in progress.

    In short, PowerShell has changed my engagement with others in the industry. I’m seen as an expert although I do not advertise myself as one. I just say, “I know the basics of PowerShell, well”

  8. Vakul More

    My love for Powershell started in late 2010. We have scheduled task jobs which were running the exe’s built on .NET and were running once in a day to pick a file. Then came a situation where we had to pick the file whenever it was dropped and then we started using Poweshell and never looked back. My love for Powershell keeps growing now that I’m using Azure.

  9. John J Howard

    Before PowerShell I was using VBscript, my boss at the time was pushing perl and I felt like neither one was a good solution this was maybe 2001 give or take a year or three. We had a virus outbreak on the client PCs, and we needed to get a specific patch on all our servers. I wrote a VB script that checked each machine for a service pack, and if it did not exist it created a scheduled task to install the service pack and reboot. Then updated a text file with the name of each server that would reboot and at what time. We manually alerted people of the coming downtime based off the text file.

    At this time our 350-bed hospital operated on maybe 50 servers. Now the same 350 bed hospital uses well over 500 servers. Which is down from a high point of over 800 servers.

    The next big challenge that fell on me was when our HR department said their new system was tied to AD so every employee had to have an AD account. Our AD users would go from 400 to over 1000 and every AD account would need to be created and active before orientation. I started writing a script to handle this when I went to my first Techmentor and had your all-day class on PowerShell. You had me power-shelled up. I had the code knocked out in a few hours, and because I had a SQL background I pulled a query from the HR system. Within a few months our IT department decided to standardize on AD account based on employee ID and I wrote the script and process to migrate our organization.

    Today we have automated our onboarding process, which is also tied to automating accounts on our Electronic Medical Record as well as Role based access. At the base of it all is the code I wrote after Techmentor. It is all handled through Powershell.

  10. Michael Levan

    My PowerShell journey was quite interesting. I was on 3 weeks of paternity leave. Learning how to be a parent. After 3 weeks I went back to work and had a new boss (which years later is one of my best friends and we work together at a different company now). He wanted to teach me a valuable skill, PowerShell. I never, ever wrote code before. In fact I was scared to. I thought I was “too dumb” or that I didn’t “have what it took”. He decided to show me that wasn’t true. I remember when i wrote my first 1 liner. It was to interact with Hyper-V. After that I became obsessed. I used my lunch break to go through PowerShell In A Month Of Lunches. I would go to the cafeteria across the street with my personal laptop. Every day id find a table and get to work studying.

    After that I couldn’t get enough. I was writing code for everything. I wrote some PowerShell modules as well. I then picked up Python to accompany PowerShell as I was working a ton with Linux.

    Fast forward 3 years. I’m a Lead DevOps Engineer working with multiple tools, but of course still PowerShell and Python.

  11. Aaron

    Powershell changed my life…. I realize that such a statement may seem exaggerated, but every Powershell enthusiast can relate in some way to the overwhelming benefits, and career opportunities that learning Powershell has given them.

    I had worked in a operations management position for 5 years, and dreaded going into work everyday. The stress was awful, but the monotony was worse. I was 30 years old, had a wife, two boys under 2 years old, and living on my single income. I was afraid it was too late to change careers and find work I actually enjoyed. However, my older brother who worked as a system administrator for a large tech company told me about how he used Powershell in his job and loved it. He was a Powershell enthusiast and thought I could learn it and open up an opportunity to change into the IT field. So he actually gave me the book he used that helped him learn, “Learn Powershell In a Month of Lunches”.

    That was about 6 months ago, and I was fortunate that an opportunity opened up at my current company in our IT department soon after I started learning. The little I knew at the time allowed me to get my foot in the door, but also gave me the opportunity to make an immediate impact and learn in a practical way.

    Powershell is easy to learn and is incredibly practical and useful in most every environment. Since I started, i’ve scripted automated tasks that run daily, created GUI tools for our Operations department, and many more things like interacting with web APIs and more.

    I now love what I do, and I’m excited about the career and financial opportunities this new path will help provide for me and my family. I will forever be a Powershell evangelist and look forward to continuing to gain a more in-depth knowledge, and hopefully have the opportunity to teach and train others how Powershell can potentially change their lives as well.

    I would like to also thank you personally Don. You’ve inspired me greatly with your enthusiasm for teaching, and all your training materials that have helped me immensely. I hope I can pay-it-forward someday and help bring up others that are hungry to learn and aspire to do great things. Thank you!

  12. Kameron Berget

    PowerShell changed the trajectory of my career!

    In 2010, I was working for an energy company (about 1300-1400 employees) as their IT Manager. I was the only person in IT so we did everything from rack servers, travel to job sites, image and deploy laptops, deploy applications, training, etc. As we grew we started to expand our IT department and one of the positions was an IT Business Analyst focused on improving the work processes of some of our largest teams (Wind,Solar, Oil). He introduced me to PowerShell when a need arose to automate invoice processing. We had a construction specific ERP system that handled invoices and approvals but did not offer a way of aggregating alerts to users about invoices in need of review. We used PowerShell to process the SQL database daily (Using the SQLPSX) module to query data from SQL, process it, and generate branded, action-driven emails to each user allowing them to approve multiple invoices as once. Eventually this process was expanded into several key automated nightly jobs. We then rolled this script (10k+ lines) into its own PowerShell module that we used to automate several aspects of our ERP system.

    Up until this time, the only code I had ever written was batch files. This was the first object oriented language I was exposed to and something clicked. I started digging into C# and using PowerShell for anything I had to do more than once. Still today, it is my Swiss-Army knife of tools that enables me to be much more efficient at my job.

    Since that job I have relocated and become a SharePoint Architect/Developer. I am able to architect SharePoint server farms and also write custom, complex solutions all because of the trajectory that PowerShell set me up on. I started my own consulting business in 2015 and my demand as a SharePoint developer has never been higher. Yesterday I had a client with an old SSRS server running in SharePoint 2010. The farm was unhealthy and they were not able to get all of their SSRS data-driven subscriptions from their reports. I was able to use PowerShell to query the SQL database, extract the subscriptions table, parse all of the data and create a dynamic HTML page for their business users to use as a guide for re-creating the subscriptions in 2019.

    For 10 years PowerShell has been the first tool I use for almost everything and I don’t see that changing anytime soon…

  13. Brad Sterkenburg

    I got my start with PowerShell v2. I was an avid VBScript user and was happily using VB.net to achieve some of the bigger tasks I needed to achieve in a more end-user friendly way.

    My very first use of PowerShell came at a time when my work life was filled with panic. In this moment, we were dealing with an intentional deletion of approximately 6,000 Active Directory user accounts. As I said, the deletion was intentional…unfortunately the outcome was not.

    With zero experience and a bunch of Get-QAD cmdlets, we rapidly recovered by accessing the AD recycle bin, parsing the list of deleted accounts, applying a boatload of limiting criteria, and piping the resulting user set through to a restore-user cmdlet. I was absolutely SOLD on the power of the shell after that. Today, there are few things which we do where PowerShell isn’t a part of the equation.

    Following that event, I purchased the PowerShell TFM book by Don. It rocked my scripting world. Thanks Don, Jeff, Jason, Snover, and all who have played a part in our adoption of this revolutionary language.

  14. Carl Davis

    While working for a large AntiVirus company in 2007 (starts with an S and ends with C), they asked me to lead the newly formed VMWare team. It consisted of three people and I was the only US based associate. I had always used the command line to get work done in Windows and SQL using DOS or VBScript (if I absolutely had to). Now I had a need to do the same automation in VMWare. After a little research I discovered the VIClient create by VMWare which was based on PowerShell and I was hooked. I was able to automate almost 100% of my job! I never took a class to learn PowerShell, but learned as I went. I went back into a Windows SysAdmin role and it was amazingly easy to port all the knowledge I gained from VMWare over to a Microsoft environment. Now I am attempting to do the same thing with a networking team automating Cisco Infrastructure. My knowledge of PowerShell and Automation has been the sole driver for my career growth over the last 13 years.

  15. jatinpurohit

    Started my IT Career in 2014, I was first started my career as System admin, responsible for managing VMware, Windows, Active directory and File servers for a large retail customer. Being a software engineering graduate I didn’t liked what i was into at first because i always wanted to code and thought Software developers are only the ones who make a difference (I was wrong though). But as time goes on I realized that there is much I can do with infrastructure if i learn powershell. and that is where i started my journey with Powershell in 2015. Initially i was only focused on writing one liners or small scripts for sys admin job but later i was able to automate the tasks which looked difficult to automate first. I must say, I learned basics of Powershell in a week and was able to execute cmdlets and write small powershell scripts at ease. This proves that powershell is one of the simplest scripting and automation platform which can be learned by anyone.

    I remember my first automation work with powershell which actually made me visible and had an impact on IT in a +ve way. We used to receive thousands of tickets for disk space alert and ops team use to login to the servers and perform clean up operation based on provided SOP. This was certainly time consuming and repetitive in nature. for me this was an opportunity. I took this challenge and wrote a POSH script which was than integrated with our ticketing system. a runbook was created in system center orchestrator. Each time disk alert triggered, Orchestrator will pick up this incident and than does the clean up operation by executing the same PowerShell script which i wrote and than update the ticket with the log details so that everybody can understand what action was performed. Ticket will automatically be closed if it met the required condition.

    I mean, for me this was something great and a differentiator me from others. This success was something which helped me to gain reputation and promotion within the ranks. The major difference it made to the Server team was, PowerShell was not even a nice-to have thing when i joined the team initially. When they saw the impact it became a Nice-to have skill set and later became a must skill set for at least level 2/3 engineers. Having powershell skill set within your team certainly creates an ecosystem where others also seek to learn Powershell.

    Its been 5 years now and I have so many stories to tell but one thing is sure that it has changed my professional career in upward direction. I started my career as a system administrator and now transitioned into Sr. Product engineer role with product engineering group. Initially i was the consumer or PowerShell modules for sys admin task and now i am writing my own powershell module for one of our recovery product developed on a Linux platform, Isn’t that amazing 🙂

  16. Jon Mattivi

    My initial experience dabbling with PowerShell starting in 2008 was a love/hate relationship. I was dedicated to VBScript back in the day to automate tasks and deploy scripts with SCCM. I was making PowerShell more complicated trying to replicate what I was doing with VBScript. I was finally able to wrap my head around using cmdlets as one-liners to do the equivalent of 25 lines of VBScript. Since then I haven’t looked back.

    PowerShell has steered my career as a Systems Engineer primarily working with AD and SCCM to where I’m at today as an Infrastructure Automation Developer. Prior to PowerShell, I feel any “automation” as it related to Windows was scripting and not “development”. In my opinion, PowerShell has set the standard for Windows development to improve process efficiency. I’m looking forward to improving my own skill set using pwsh to become a better cross-platform developer.

    I’ve even incorporated PowerShell into my personal life for various tasks, for example, automating my photo and movie library organization/management. Being too frugal to buy expensive thermostats for my home, I’ve used PowerShell to automate my wireless thermostats based on outside temperature for my heat pump to save money on propane! So PowerShell is literally saving me hundreds of dollars annually!!

  17. Rob Simmers

    2002 – Working a Call Center as a desktop technician, we were using Windows NT 4.0 with mandatory profiles, Group Policy and scripts (VBScript) to create very restricted profiles for end users. Typically, if you are calling a 1-800 number to compliment or complain about something, it was being redirected to one of our 40+ groups which meant 40+ profiles. A team started getting an error when they would launch an application, so I asked the person responsible for it to troubleshoot it and the started throwing things around their desk, breathing sporadically before telling me that they didn’t have time and it was working when they tested. They insisted the user was doing something wrong, to which I replied all that they can do is double click it, what can they do wrong and another tangent ensued. This was the moment I said I’m learning VBScript so I’m not dependent this person.

    2003 – Luckily, there was a super bright, friendly guy that had reading material but also mentored and explained things to me. I would write a script and they would look at it, typically laugh and then go into why I overcomplicated things and showed me how to make things efficient. By early 2003, the tirade gentleman was asking me how to do things and troubleshoot his scripts

    2004 – I started working as a Systems Engineer and this is when toolmaking became prevalent because I wanted to do something like type in some information, like a server name and execute code to get WMI information. Starting with command-line prompts I ventured into ASP and HTA’s to make things pretty to consume and get CSVs out. My manager found out that I was using VBScript automation to manage servers and told me he wanted me to spend more time walking into the datacenter and touching the physical servers and what I was doing was a waste of time.
    2006 – [Powershell released] Started working for a bank that was interested in automation of Operating System deployment and there was a guy there that wrote a ASP website that was used for approvals before SMS would schedule software pushes. Very automation centric team where I learned a lot about how applications work and are built.

    2008 – Started working for Aerospace company and they were starting to do zero-touch Operating System Deployments with MDT (a VBScript library) at this point I thought I was an expert in VBScript. I started frequenting a forum visualbasicscript.com (decommissioned) where I found quickly, I had some much more to learn, but I wanted to mentor and help other people understand the power of automation. This is when I was writing frameworks in VBScript for software deployments, HTA’s, ASP.NET (C#, JavaScript) websites to interface with SCCM and even considered becoming a developer. One of the things I started using more and more in VBScript was Scripting.Dictionary which was a hash table as it so much more powerful than trying to manage text logs because it was so much easier in C# or VB.NET with Object Oriented Design (OOD). This is when I started seeing more and more people say this is 10x easier in Powershell and I would try to understand objects and the pipeline in Powershell. I bought a book and started understanding the core concepts and started writing scripts. This was a tough transitional period because years learning VBScript, all the internal scripts were VBScript and I was the only one that was learning Powershell trying to advocate it. Also, I remember visiting the call center (Manager et al., 2004) to catch up with colleagues and they were still using the vbScripts and HTA’s where the aforementioned same manager was amazed at all of this automation and how quickly they could get server information from typing in a servername.

    2014 – Started learning Identity Access Management (IAM) and starting writing modules for custom integrations to perform Create, Read, Update, Delete (CRUD) operations for applications that are custom or had no supported integrations. I still believe in mentoring and contribute to Powershell.org but have not delved into blogs. At this point I use Powershell for AD, Exchange, SCCM, SQL, VMWare, Nutanix, API’s and whatever other applications I interface with at customers. Anything I can automate, I’m in!!

  18. Pingback: Book: "Shell of an Idea," the Untold History of PowerShell | PowerShell.org

  19. Thomas Maurer

    Back in 2006, I was working for a small consulting company, which helped customers with Windows Server, Windows Clients, Active Directory, Microsoft Exchange, and so on. I worked a lot, modifying and writing Windows batch files to build some basic automation on Windows. When PowerShell was first released, it was as well all know elementary, but I was convinced that it is going to be the future in automation on Windows. A couple of years later, I was hired by a service provider, which I very quickly was responsible for the Microsoft/Windows environments, with IIS web hosting and MSSQL database hosting. Most of the automation was build based on VBScripts, and I realized really quickly that I would need to build some automation to manage all of that infrastructure. At this point, we had PowerShell version 2, which again added a lot of great features like basic remoting capabilities, building of modules, and most importantly, the PowerShell ISE.
    I think one of my biggest challenges but also one of the best learning experiences, and the project which gave me a jumpstart in my career, was when we were starting to build a SharePoint Hosting environment based on SharePoint 2010. It was in 2009 when I started working to develop my own PowerShell modules, working with web services, and much more. PowerShell still was missing a couple of important features, and we worked around this using C# code. I started to share my learning about PowerShell on my blog (www.thomasmaurer.ch), which helped me to get exposer in the Microsoft community. And until today, I have a couple of blog posts from 2009, which people are still looking up fairly regularly. In addition, this project also helped me to get a new job when I showed this project to a Microsoft employee who then recommended me to a successful Microsoft consulting company in Switzerland.
    Today I am working for Microsoft, and I am still using PowerShell almost daily, and I am still trying to help the community to get better.

  20. Alvaro Torres Tatis (@ATorresTatis)

    In 2015 I needed to write a program to extract information from a web page. I could do it using C # or using a technology that was widely talked about on the Internet by the release of 4.0 version couple years ago, so I decided to do it in the latter. And from there I change the way I write programs, now we develop many more APIs putting a PowerShell module in front to manage, making easier user training, test automation and deployment. Today, we’re using PowerShell almost daily, and we have been developed more than 100 modules for almost any kind of purposes.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.