HELP: PowerShell 5.1 / 5.0 What’s New (and More) – Part 3 Modules

In the last installment of this Windows PowerShell HELP series, you learnt about the new cmdlets introduced in both PS 5.0 and 5.1. But where do they actually come from?

A module is essentially a data repository which groups all relevant cmdlets, functions and commands under one roof. Since PS 3.0, the mere act of running a cmdlet will cause Windows PowerShell to load the corresponding module without administrative intervention. To make this work, modules must be placed in a location listed in $env:PSModulepath. Because of this automatic module loading feature, an administrator does not always need to know exactly in which module a particular command resides[1]. By changing the $PSModuleAutoLoadingPreference preference variable, you can enable, disable and configure automatic importing of modules.

For a default Windows Server 2012 R2 (PS 4.0) installation, a total of 63 modules are available for use. The addition …

Continue reading “HELP: PowerShell 5.1 / 5.0 What’s New (and More) – Part 3 Modules”