Book Image

Enterprise PowerShell Scripting Bootcamp

By : Brenton J.W. Blawat
Book Image

Enterprise PowerShell Scripting Bootcamp

By: Brenton J.W. Blawat

Overview of this book

Enterprise PowerShell Scripting Bootcamp explains how to create your own repeatable PowerShell scripting framework. This framework contains script logging methodologies, answer file interactions, and string encryption and decryption strategies. This book focuses on evaluating individual components to identify the system’s function, role, and unique characteristics. To do this, you will leverage built-in CMDlets and Windows Management Instrumentation (WMI) to explore Windows services, Windows processes, Windows features, scheduled tasks, and disk statistics. You will also create custom functions to perform a deep search for specific strings in files and evaluate installed software through executable properties. We will then discuss different scripting techniques to improve the efficiency of scripts. By leveraging several small changes to your code, you can increase the execution performance by over 130%. By the end of this book, you will be able to tie all of the concepts together in a PowerShell-based Windows server scanning script. This discovery script will be able to scan a Windows server to identify a multitude of components.
Table of Contents (21 chapters)
Enterprise PowerShell Scripting Bootcamp
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
3
Working with Answer Files
Index

Script execution speed


When PowerShell scripts are executing, they consume both memory and CPU resources on a system. With larger scanning scripts, this may spike system resources for a noticeable duration of time. As a result, it's important to optimize your scripts to quickly execute the task at hand. One of the cmdlets that you can use to measure script execution time is the measure-command cmdlet. To measure the execution time, you call the measure-command cmdlet and place the code you want to execute in curly brackets. The output of the measure-command cmdlet will display the Days, Hours, Seconds, Milliseconds, Ticks, TotalDays, TotalHours, TotalMinutes, TotalSeconds, and TotalMilliseconds of the operation. This represents the duration of time the code took to execute the section of code.

To measure a command by leveraging the measure-command cmdlet, you can perform the following:

measure-command { ping localhost } 

The output of this is shown in the following screenshot:

In this example...