Good day, Cloud Gurus,
and welcome back for this section,
where we're going to take a look at managing Windows Server.
Let's take a look at what we're going to cover
in this section.
First up, we'll take a look at how you can configure
PowerShell Remoting.
And in the next lesson,
we'll take a look at Implementing
Just Enough Administration,
which is an awesome PowerShell Remoting security feature.
And then we'll address
what's known as the Second Hop Problem.
We'll take a look at Deploying Windows Admin Center
and Integrating Windows Admin Center with Azure,
and then we'll do a bit of an Introduction to Azure Arc,
and we'll wrap up this section
with Monitoring Windows Server with Hybrid Technologies.
But before we jump into each of these topics
in this section,
I just want to cover off 2 introductory topics
that will help us as we work through this section.
Firstly, I want to take a look
at the history of Windows Server management,
and then we will take an introductory look
at Windows PowerShell.
Managing Windows Server has evolved over the years,
and the way we manage Windows Server these days
is almost nothing like how we managed it in years gone.
Let's take a quick look at the history
of Windows Server management,
and how we got to where we are today.
In versions of Windows Server up until Windows Server 2003,
we got the Microsoft Management Console, or MMC,
and separate utility command-line tools,
available via command prompt.
And then in 2006,
everything changed with the release of Windows PowerShell.
Windows PowerShell really enabled easy automation
on Windows Server.
And over the years,
Microsoft has continued to add functionality
to Windows PowerShell over several versions,
including the release of Windows PowerShell Remoting
in 2009.
And then with the release of Windows Server 2012,
Microsoft released Server Manager
and Windows PowerShell Version 3.
Server Manager bundled in a range of functionality
that was previously only available in older tools,
and included some new functionality
that is only available in Server Manager.
And then in 2018, Microsoft released Windows Admin Center,
which is a web-based management tool for Windows Server.
And then more recently in 2019,
Microsoft announced the public preview of Azure Arc,
an Azure based management solution for Windows Server
that brings together a range of Azure functionality.
Now, because Microsoft includes unique functionality
in each of these tools,
we will likely have to use all of these tools at some point
when managing Windows Server.
It's also worth pointing out that, more recently,
Windows PowerShell has become just PowerShell,
and is now multiplatform, supporting Linux and Mac OS.
But for the purposes of managing Windows Server
and preparing for the AZ 800 Exam,
we can use Windows PowerShell.
But some newer functionality
is only available in the newer PowerShell.
Now throughout this course so far,
we've used PowerShell for a range of administrative tasks,
and PowerShell is perhaps the most important improvement
ever made to Windows Server management.
Now, I have briefly explained each command I have run
when executing PowerShell commands in this course,
but for anyone that is relatively new to PowerShell,
I just want to break down
the anatomy of a PowerShell command.
Let's first take a look at a typical PowerShell command.
Typically, a PowerShell command
is made up of one or more cmdlets.
Cmdlets are a small piece of code
that provides functionality used to produce an object,
or a collection of objects,
and sometimes perform an action.
And cmdlets use a verb-noun syntax,
sometimes with a prefix before the noun,
like AD in this example.
And as we've seen a bit in this course,
you can also send the output of one cmdlet
to another cmdlet using the | character.
And you can customize the way a cmdlet behaves
using parameters,
which include a parameter name and a value.
Sometimes parameters are optional,
and sometimes you can specify the value of the parameter
without specifying the parameter name.
And you can use the get help cmdlet
to find out more about this.
Now obviously there's a lot more to PowerShell
than what I've covered here,
but that's all we really need to know for now.
All right.
Let's jump into the rest of the lessons in this section.
I'll see you there.