1
00:00:01,240 --> 00:00:04,790
[Autogenerated] We're looking at the desktop of arc to which is one of my

2
00:00:04,790 --> 00:00:09,630
Windows Server 2022 machines in my on premises local environment.

3
00:00:09,630 --> 00:00:13,500
So let me sign into the portal here and I've browsed to azure arc,

4
00:00:13,500 --> 00:00:16,100
if you type arc in the azure portal,

5
00:00:16,100 --> 00:00:18,930
you get a whole bunch of arc-related options.

6
00:00:18,930 --> 00:00:22,730
Were just concerned with a subset of Azure arc functionality.

7
00:00:22,730 --> 00:00:27,850
As you can see down here, we have Azure stack, Kubernetes SQL servers.

8
00:00:27,850 --> 00:00:28,990
Postgres,

9
00:00:28,990 --> 00:00:33,260
SQL there's a lot going on but we're just interested as I said in

10
00:00:33,260 --> 00:00:37,470
Azure arc servers and as you can see one of my on premises machines

11
00:00:37,470 --> 00:00:41,790
is already on boarded and you can see it's represented as an Azure

12
00:00:41,790 --> 00:00:43,540
arc for servers resource,

13
00:00:43,540 --> 00:00:47,390
that's in a resource group and tracked in my subscription and

14
00:00:47,390 --> 00:00:50,240
we have the ability to apply taxonomic tags,

15
00:00:50,240 --> 00:00:51,670
just like we do in Azure.

16
00:00:51,670 --> 00:00:54,780
Now, the exam objective here deals with on boarding the server.

17
00:00:54,780 --> 00:00:58,500
So let's go to add and let's take a look at the options here,

18
00:00:58,500 --> 00:01:02,340
notice that we can add a single server or multiple servers with a

19
00:01:02,340 --> 00:01:05,820
power shell script I had mentioned in the lecture portion that we

20
00:01:05,820 --> 00:01:08,340
could use desired state configuration.

21
00:01:08,340 --> 00:01:11,230
It's a way to onboard servers to Azure arc.

22
00:01:11,230 --> 00:01:15,460
We also can use the update management service although notice that as of

23
00:01:15,460 --> 00:01:18,830
this recording in early 2022 it's in public preview,

24
00:01:18,830 --> 00:01:19,570
You should know that.

25
00:01:19,570 --> 00:01:20,680
Generally speaking,

26
00:01:20,680 --> 00:01:24,490
public preview features are not covered on certification exam

27
00:01:24,490 --> 00:01:28,290
objective domains nor our public preview features normally in

28
00:01:28,290 --> 00:01:29,960
scope for Microsoft support.

29
00:01:29,960 --> 00:01:34,450
So it's best to use preview features only in a test dev capacity.

30
00:01:34,450 --> 00:01:34,880
All right,

31
00:01:34,880 --> 00:01:37,310
so let's take a look at the script for a single

32
00:01:37,310 --> 00:01:39,470
server and the way we set this up.

33
00:01:39,470 --> 00:01:44,430
First of all, we have to ensure we've got TCP 4432 Azure,

34
00:01:44,430 --> 00:01:48,340
we need to be a local administrator on the server and if we're

35
00:01:48,340 --> 00:01:50,820
dealing with proxy and that kind of stuff,

36
00:01:50,820 --> 00:01:52,100
we have to keep that in mind.

37
00:01:52,100 --> 00:01:54,580
connectivity I'm just going to go over the public

38
00:01:54,580 --> 00:01:56,410
internet endpoint let's click next.

39
00:01:56,410 --> 00:02:00,520
I'm going to put this ark server in my Arc RG Resource group.

40
00:02:00,520 --> 00:02:02,640
The resource will be in east US.

41
00:02:02,640 --> 00:02:04,540
The operating system is Windows.

42
00:02:04,540 --> 00:02:07,830
As I said, we're going to use public endpoint we'll click next.

43
00:02:07,830 --> 00:02:13,480
I'm going to add a taxonomic tag called host name arc to in this case

44
00:02:13,480 --> 00:02:16,790
we'll click next and here's the actual on boarding script.

45
00:02:16,790 --> 00:02:19,740
I'm going to copy this to my clipboard and then I have

46
00:02:19,740 --> 00:02:22,070
VS Code installed on this server.

47
00:02:22,070 --> 00:02:24,580
Let me go ahead and create the script file.

48
00:02:24,580 --> 00:02:26,630
Let me save it to my desktop.

49
00:02:26,630 --> 00:02:30,090
I'll call it arc onboarding dot PS one.

50
00:02:30,090 --> 00:02:33,730
Yikes I'm going to have to pause the video and fix the typeface there.

51
00:02:33,730 --> 00:02:35,080
That's not looking so good.

52
00:02:35,080 --> 00:02:36,660
Okay, that's a little bit better.

53
00:02:36,660 --> 00:02:41,300
So let's come back here to the portal and let me actually step out

54
00:02:41,300 --> 00:02:44,140
of here to show you the add multiple servers,

55
00:02:44,140 --> 00:02:47,160
this would be more likely what you'll look into in the real

56
00:02:47,160 --> 00:02:50,290
world because you're going to onboard presumably a number of

57
00:02:50,290 --> 00:02:52,670
machines rather than just singleton.

58
00:02:52,670 --> 00:02:56,310
So if we go to generate script here and click next,

59
00:02:56,310 --> 00:02:59,750
we specify our meta again and then when we get here

60
00:02:59,750 --> 00:03:01,600
notice that there's an extra step,

61
00:03:01,600 --> 00:03:05,520
we need to create a service principal that is represented in our

62
00:03:05,520 --> 00:03:09,860
Azure Active Directory and that service principle needs to be assigned to the

63
00:03:09,860 --> 00:03:14,830
Azure connected machine on boarding role because the idea with a multiple

64
00:03:14,830 --> 00:03:19,400
servers to Azure arc is that we're going to authenticate non interactively to

65
00:03:19,400 --> 00:03:24,130
Azure and bring all of those machines in our local environment into Azure in

66
00:03:24,130 --> 00:03:26,740
an automatic non interactive way.

67
00:03:26,740 --> 00:03:29,630
So that's a good example for you to keep in mind.

68
00:03:29,630 --> 00:03:33,830
Let's come back to our PowerShell session here, let me maximize my view.

69
00:03:33,830 --> 00:03:36,780
We don't need to understand everything that's going on

70
00:03:36,780 --> 00:03:39,480
in the on boarding script as such,

71
00:03:39,480 --> 00:03:43,190
basically it's just some simple PowerShell that's going to invoke

72
00:03:43,190 --> 00:03:46,130
web request to bring down the Mississippi package.

73
00:03:46,130 --> 00:03:50,230
Actually it looks like it's a one file online to we're going to do and

74
00:03:50,230 --> 00:03:55,000
invoke web request to bring down the connected machine agent and then it's

75
00:03:55,000 --> 00:03:58,700
just going to run the command and it has a little bit of error handling

76
00:03:58,700 --> 00:04:00,700
logic in it as well as you can see,

77
00:04:00,700 --> 00:04:05,530
let me open the terminal menu and let's do a run active file to install

78
00:04:05,530 --> 00:04:08,900
the Azure connected machine agent on this system.

79
00:04:08,900 --> 00:04:12,120
Remember that the difference between the scale script and

80
00:04:12,120 --> 00:04:14,790
the single script is the single script assumes that you're

81
00:04:14,790 --> 00:04:16,220
doing this interactively.

82
00:04:16,220 --> 00:04:19,480
So we're going to need to do a device code sign and let me

83
00:04:19,480 --> 00:04:23,500
copy this code to my clipboard and will open up shortcut

84
00:04:23,500 --> 00:04:27,640
it's aka dot MS device login.

85
00:04:27,640 --> 00:04:29,780
I'll paste in my device code here,

86
00:04:29,780 --> 00:04:33,060
sign in with my current credentials to sign into the

87
00:04:33,060 --> 00:04:35,900
Azure connected machine agent service.

88
00:04:35,900 --> 00:04:38,570
I may now close this window and if we come back to the

89
00:04:38,570 --> 00:04:40,760
script that should complete momentarily.

90
00:04:40,760 --> 00:04:43,990
Now we can continue to use this code and just edit it.

91
00:04:43,990 --> 00:04:47,630
I would maybe create a function out of it and parameter rise it so

92
00:04:47,630 --> 00:04:50,270
you notice that we can change the resource group.

93
00:04:50,270 --> 00:04:53,350
We probably don't need to change the Active directory

94
00:04:53,350 --> 00:04:55,510
Azure Active directory tenant ID.

95
00:04:55,510 --> 00:04:58,310
We may want to create a parameter for location.

96
00:04:58,310 --> 00:05:02,560
We may or may not want to create a parameter for our subscription id.

97
00:05:02,560 --> 00:05:02,890
Alright.

98
00:05:02,890 --> 00:05:06,090
It tells us down at the bottom and the verbose output to view your

99
00:05:06,090 --> 00:05:09,920
onboard and server navigate to your portal and it gives you a discrete

100
00:05:09,920 --> 00:05:11,940
linked to the portal but we don't need that.

101
00:05:11,940 --> 00:05:16,170
Let's come back into edge and let me refresh my view here.

102
00:05:16,170 --> 00:05:18,970
So now I have my arc to machine connected.

103
00:05:18,970 --> 00:05:21,930
So let's select it and let's take a look at some of the

104
00:05:21,930 --> 00:05:24,620
Azure Resource Manager settings like I said,

105
00:05:24,620 --> 00:05:27,330
we have taxonomic tag capability.

106
00:05:27,330 --> 00:05:32,000
I just created the host name. Arc to a moment ago