Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Enterprise PowerShell Scripting Bootcamp

You're reading from   Enterprise PowerShell Scripting Bootcamp The fastest way to learn PowerShell scripting

Arrow left icon
Product type Paperback
Published in May 2017
Publisher Packt
ISBN-13 9781787288287
Length 238 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Brenton J.W. Blawat Brenton J.W. Blawat
Author Profile Icon Brenton J.W. Blawat
Brenton J.W. Blawat
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Getting Started with Enterprise PowerShell Scripting FREE CHAPTER 2. Script Structure, Comment Blocks, and Script Logging 3. Working with Answer Files 4. String Encryption and Decryption 5. Interacting with Services, Processes, Profiles, and Logged on Users 6. Evaluating Scheduled Tasks 7. Determining Disk Statistics 8. Windows Features and Installed Software Detection 9. File Scanning 10. Optimizing Script Execution Speed 11. Improving Performance by Using Regular Expressions 12. Overall Script Workflow, Termination Files, and Merging Data Results 13. Creating the Windows Server Scanning Script and Post-Execution Cleanup Index

Creating a termination function

When PowerShell scripts execute on systems, they consume memory and CPU resources. This is especially true if you are scanning directories and leveraging the Get-Content cmdlet to evaluate files. PowerShell has to load the directory listing in memory, and place the entire contents of the file in memory for processing.

One of the common concerns with deploying a PowerShell script enterprise-wide is being able to terminate the script mid-scan if necessary. While you could use the stop-process cmdlet or the taskkill.exe to terminate the PowerShell processes, you may also inadvertently terminate all running PowerShell processes on a system. Without fully executing the script, you may be leaving sensitive scan data on the system.

An alternative to killing the PowerShell processes is to create a function to check to see if a kill file exists on the system. If that kill file exists on the system, the script will gracefully terminate. This will allow the script to...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime