{"id":9225,"date":"2023-02-28T12:58:44","date_gmt":"2023-02-28T17:58:44","guid":{"rendered":"https:\/\/jdhitsolutions.com\/blog\/?p=9225"},"modified":"2023-02-28T12:58:46","modified_gmt":"2023-02-28T17:58:46","slug":"automation-decisions","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/powershell\/9225\/automation-decisions\/","title":{"rendered":"Automation Decisions"},"content":{"rendered":"\n
\n

This post is an updated reprint from an article published to my premium PowerShell newsletter Behind the PowerShell Pipeline<\/em> available on Substack<\/a>. Subscribers receive 6-8 articles like this a month delivered to their inbox or available on the Substack app. I hope you\u2019ll consider subscribing. Trial subscriptions are available.<\/p>\n<\/blockquote>\n\n\n\n

I\u2019ve been scripting and automating things since the days of DOS 3.3, beginning with batch files. It always felt like magic. I could cast a charm simply by typing a few characters on a keyboard. Naturally, my magic skills went from batch files to VBScript to PowerShell. Throughout it all, I\u2019ve also had an internal decision tree regarding automation. Over the years, I\u2019ve seen IT pros new to scripting and automation needlessly struggle. Often it is due to a deficiency in their decision tree. Today, I thought I\u2019d help you nurture yours.<\/p>\n\n\n\n

Is it Worth the Investment?<\/h2>\n\n\n\n

This is the first question you should always ask when considering a new automation project. I\u2019m sure you\u2019ve all heard the phrase, \u201cJust because you can do something doesn\u2019t mean you should.\u201d This is especially true when it comes to PowerShell.<\/p>\n\n\n\n

PowerShell makes it easy to automate tasks. Ideally, you use PowerShell and automation to handle repetitive tasks, especially unglamorous tasks that must be done regularly. Any PowerShell solution that you develop will require an investment. At a minimum, you are investing time to write your code. This is time you are taking away from other work. Depending on the task, you may need to invest in additional educational material such as books or courseware.<\/p>\n\n\n\n

As you consider a new PowerShell project, you need to be able to estimate how much time you will need. This becomes easier as you gain experience. And with experience, you\u2019ll also find you can do more in less time. You need to weigh the time required against the time saved. For example, I probably wouldn\u2019t take the time to build tooling around enabling the Active Directory Recycle Bin feature. Yes, you use PowerShell, but this is not an ongoing task. But I would create a PowerShell tool around resetting a user\u2019s password.<\/p>\n\n\n\n

Of course, there are exceptions. You may want to develop a PowerShell solution as a means of improving and expanding your scripting skills. I\u2019ve been known to joke about spending a day writing a PowerShell function that saves me a few seconds. But, over the course of a year, those seconds add up. And when I\u2019m finished, I\u2019ve most likely learned something that I can use in future projects. In these situations, I\u2019m using a different metric to justify my investment. It isn\u2019t the time I\u2019m saving but the learning process that warrants my time.<\/p>\n\n\n\n

The bottom line is you need to look at the task at hand, consider how much of an investment it will require, and calculate the cost-benefit ratio. Your time is limited and valuable so use it wisely.<\/p>\n\n\n\n

Can It Be Scripted?<\/h2>\n\n\n\n

You also need to consider if you can even automate the task at hand. I\u2019ve seen many requests for automation help over the years that boggle my mind. This is a case where you must understand PowerShell and recognize what it is designed to do and, more importantly, what it can\u2019t. Here is a shortlist.<\/p>\n\n\n\n