Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
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

PowerShell script 3 - the termination files

There may come a time where you will need to terminate the execution of the Windows server scanning script. This could be due to the script consuming too many resources, or the script taking too long to execute. One of the most efficient ways to quickly and gracefully terminate a script is leveraging a termination file. When a termination file is placed on the system, the script will stop its current action, and gracefully exit the script.

The two methods to deploy the termination file in an environment are either locally on the server, or by leveraging remote commands. When you leverage deployment tools, you may have to create a script that runs locally on the system. If you want to create the termination file locally on a system, you can leverage the new-item cmdlet with the -path parameter set to "c:\temp\KILL_SERVER_SCAN.NOW". You then specify the -ItemType parameter with the argument of File. After execution, the termination file...

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
Banner background image