Book Image

Learn PowerShell Core 6.0

By : David das Neves, Jan-Hendrik Peters
Book Image

Learn PowerShell Core 6.0

By: David das Neves, Jan-Hendrik Peters

Overview of this book

Beginning with an overview of the different versions of PowerShell, Learn PowerShell Core 6.0 introduces you to VSCode and then dives into helping you understand the basic techniques in PowerShell scripting. You will cover advanced coding techniques, learn how to write reusable code as well as store and load data with PowerShell. This book will help you understand PowerShell security and Just Enough Administration, enabling you to create your own PowerShell repository. The last set of chapters will guide you in setting up, configuring, and working with Release Pipelines in VSCode and VSTS, and help you understand PowerShell DSC. In addition to this, you will learn how to use PowerShell with Windows, Azure, Microsoft Online Services, SCCM, and SQL Server. The final chapter will provide you with some use cases and pro tips. By the end of this book, you will be able to create professional reusable code using security insight and knowledge of working with PowerShell Core 6.0 and its most important capabilities.
Table of Contents (26 chapters)
Title Page
Dedication
Packt Upsell
Contributors
Preface
Index

Push


The standard mode of operation that is enabled by default is the push mode. While in push mode, the LCM awaits configuration documents to be pushed to its node. To initiate a push, the Start-DscConfigurationcmdlet can be used. CIM remoting is used to connect to all target nodes, and the configuration document is pushed.

Note

If your configuration documents are larger than WSMAN:\localhost\MaxEnvelopeSizekb, you will inadvertently run into issues. Try increasing the envelope size in this case.

By default, the configuration is started on a background job and will run entirely on the target nodes. Regardless of the refresh mode, the configuration always follows the same path:

  1. A new configuration document arrives.
  2. Generate a dependency tree and check the resource for incompatible settings.
  3. Check that all used resource modules exist.
  4. For each resource in the dependency tree, first test whether the resource is already in the desired state.
  5. For each failed test, enter a set method in order to correct...