[Autogenerated] We're looking at the desktop of arc to which is one of my
Windows Server 2022 machines in my on premises local environment.
So let me sign into the portal here and I've browsed to azure arc,
if you type arc in the azure portal,
you get a whole bunch of arc-related options.
Were just concerned with a subset of Azure arc functionality.
As you can see down here, we have Azure stack, Kubernetes SQL servers.
Postgres,
SQL there's a lot going on but we're just interested as I said in
Azure arc servers and as you can see one of my on premises machines
is already on boarded and you can see it's represented as an Azure
arc for servers resource,
that's in a resource group and tracked in my subscription and
we have the ability to apply taxonomic tags,
just like we do in Azure.
Now, the exam objective here deals with on boarding the server.
So let's go to add and let's take a look at the options here,
notice that we can add a single server or multiple servers with a
power shell script I had mentioned in the lecture portion that we
could use desired state configuration.
It's a way to onboard servers to Azure arc.
We also can use the update management service although notice that as of
this recording in early 2022 it's in public preview,
You should know that.
Generally speaking,
public preview features are not covered on certification exam
objective domains nor our public preview features normally in
scope for Microsoft support.
So it's best to use preview features only in a test dev capacity.
All right,
so let's take a look at the script for a single
server and the way we set this up.
First of all, we have to ensure we've got TCP 4432 Azure,
we need to be a local administrator on the server and if we're
dealing with proxy and that kind of stuff,
we have to keep that in mind.
connectivity I'm just going to go over the public
internet endpoint let's click next.
I'm going to put this ark server in my Arc RG Resource group.
The resource will be in east US.
The operating system is Windows.
As I said, we're going to use public endpoint we'll click next.
I'm going to add a taxonomic tag called host name arc to in this case
we'll click next and here's the actual on boarding script.
I'm going to copy this to my clipboard and then I have
VS Code installed on this server.
Let me go ahead and create the script file.
Let me save it to my desktop.
I'll call it arc onboarding dot PS one.
Yikes I'm going to have to pause the video and fix the typeface there.
That's not looking so good.
Okay, that's a little bit better.
So let's come back here to the portal and let me actually step out
of here to show you the add multiple servers,
this would be more likely what you'll look into in the real
world because you're going to onboard presumably a number of
machines rather than just singleton.
So if we go to generate script here and click next,
we specify our meta again and then when we get here
notice that there's an extra step,
we need to create a service principal that is represented in our
Azure Active Directory and that service principle needs to be assigned to the
Azure connected machine on boarding role because the idea with a multiple
servers to Azure arc is that we're going to authenticate non interactively to
Azure and bring all of those machines in our local environment into Azure in
an automatic non interactive way.
So that's a good example for you to keep in mind.
Let's come back to our PowerShell session here, let me maximize my view.
We don't need to understand everything that's going on
in the on boarding script as such,
basically it's just some simple PowerShell that's going to invoke
web request to bring down the Mississippi package.
Actually it looks like it's a one file online to we're going to do and
invoke web request to bring down the connected machine agent and then it's
just going to run the command and it has a little bit of error handling
logic in it as well as you can see,
let me open the terminal menu and let's do a run active file to install
the Azure connected machine agent on this system.
Remember that the difference between the scale script and
the single script is the single script assumes that you're
doing this interactively.
So we're going to need to do a device code sign and let me
copy this code to my clipboard and will open up shortcut
it's aka dot MS device login.
I'll paste in my device code here,
sign in with my current credentials to sign into the
Azure connected machine agent service.
I may now close this window and if we come back to the
script that should complete momentarily.
Now we can continue to use this code and just edit it.
I would maybe create a function out of it and parameter rise it so
you notice that we can change the resource group.
We probably don't need to change the Active directory
Azure Active directory tenant ID.
We may want to create a parameter for location.
We may or may not want to create a parameter for our subscription id.
Alright.
It tells us down at the bottom and the verbose output to view your
onboard and server navigate to your portal and it gives you a discrete
linked to the portal but we don't need that.
Let's come back into edge and let me refresh my view here.
So now I have my arc to machine connected.
So let's select it and let's take a look at some of the
Azure Resource Manager settings like I said,
we have taxonomic tag capability.
I just created the host name. Arc to a moment ago