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! 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
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Windows PowerShell Scripting

You're reading from   Mastering Windows PowerShell Scripting Master the art of automating and managing your Windows environment using PowerShell

Arrow left icon
Product type Paperback
Published in Apr 2015
Publisher
ISBN-13 9781782173557
Length 282 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 (16) Chapters Close

Preface 1. Variables, Arrays, and Hashes FREE CHAPTER 2. Data Parsing and Manipulation 3. Comparison Operators 4. Functions, Switches, and Loops Structures 5. Regular Expressions 6. Error and Exception Handling and Testing Code 7. Session-based Remote Management 8. Managing Files, Folders, and Registry Items 9. File, Folder, and Registry Attributes, ACLs, and Properties 10. Windows Management Instrumentation 11. XML Manipulation 12. Managing Microsoft Systems with PowerShell 13. Automation of the Environment 14. Script Creation Best Practices and Conclusion Index

Chapter 7. Session-based Remote Management

When you are developing your scripts, you may run into situations where you need to configure remote systems. While a lot of command-line programs provide the ability to execute remote commands, PowerShell provides Common Information Model (CIM) cmdlets allowing the scripts to be executed on remote systems over a session. The CIM cmdlet brokers the communications which provides improved performance and reliability while executing a group of commands on multiple remote systems.

Microsoft's implementation of the CIM cmdlets was derived from the need to communicate with both Windows and non Windows systems from a singular command base. Microsoft initially created Web Services for Management (WS-Man), which allows communications to non Windows systems. This was problematic due to the protocol being SOAP-based and made it difficult to quickly create PowerShell scripts to communicate with these systems.

With the release of PowerShell 2...

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