So far, we've been working with modules
that are pre‑installed on a Windows 10
machine, and you've got a good handle on
the nuts and bolts of how PowerShell deals
with modules when they're installed. Now
it's time to really dig into exploring and
working with new PowerShell modules that
aren't installed on our machines by
default. First up, we need to spend a few
minutes covering package management and
repositories. We'll talk through the key
components of this framework that you
should know about as you go forward in
your journey with PowerShell. The
installation and management of modules are
built on top of the package management
framework, and you'll need to interface
with repositories because, well, that's
the locations that you'll be looking in to
find new modules and code. From there,
we'll be back into the hands‑on, starting
with finding and installing modules. Once
you've got a module installed, the author
will no doubt release updates to the
module over time, so you'll need to know
how to update a module that's already been
installed. When you're finished working
with a module, whether that be in your
current PowerShell session or if you want
a fully uninstall it from your computer,
there's a process to follow for doing
that, and I'll walk you through each of
those when we cover removing and
uninstalling modules. To wrap up, I want
to show you the process of installing a
module on a computer that does not have
network connectivity to a repository, such
as the PowerShell Gallery. There are
plenty of companies that limit outbound
internet access, and there are situations
where machines just don't have any
internet access at all, but you still need
to install the module on those machines to achieve a particular task. Let's dive in.