1
00:00:01,040 --> 00:00:02,230
We're back from a reboot.

2
00:00:02,230 --> 00:00:02,680
Actually,

3
00:00:02,680 --> 00:00:05,240
you'll find that both the source and destination

4
00:00:05,240 --> 00:00:07,940
machines will reboot several times,

5
00:00:07,940 --> 00:00:10,980
and there's actually a lot going on under the hood with Storage

6
00:00:10,980 --> 00:00:13,500
Migration Service in terms of the servers.

7
00:00:13,500 --> 00:00:18,610
Because of the rename of both machines, they're going to need to unjoin,

8
00:00:18,610 --> 00:00:21,950
rejoin the domain, there's temp accounts being created.

9
00:00:21,950 --> 00:00:24,850
I would suggest you read the Microsoft Docs article,

10
00:00:24,850 --> 00:00:27,880
How cutover works in Storage Migration Service,

11
00:00:27,880 --> 00:00:30,040
to learn about those details.

12
00:00:30,040 --> 00:00:34,720
But I've signed back into my old Windows Server 2019 machine.

13
00:00:34,720 --> 00:00:38,470
And we can see in WAC, win2019old.timw.info.

14
00:00:38,470 --> 00:00:43,340
I've gone back into Storage Migration Service,

15
00:00:43,340 --> 00:00:46,950
and we now can see that we're showing that the job,

16
00:00:46,950 --> 00:00:50,140
the cutover, has succeeded, and so we're all set to go,

17
00:00:50,140 --> 00:00:54,590
and we can verify this by making a connection to our new server,

18
00:00:54,590 --> 00:00:59,840
which is win2019.timw.info.

19
00:00:59,840 --> 00:01:02,080
And as a matter of fact, here we are right now.

20
00:01:02,080 --> 00:01:08,550
I'm on the machine formerly known as mem3.tim w.info, now known as win2019.

21
00:01:08,550 --> 00:01:12,760
I can demonstrate that just by doing a hostname, win2019.

22
00:01:12,760 --> 00:01:14,540
And if we do a winver,

23
00:01:14,540 --> 00:01:17,910
I guess I could have done that from the PowerShell prompt as well,

24
00:01:17,910 --> 00:01:21,040
this is a Windows Server 2022 box.

25
00:01:21,040 --> 00:01:27,440
And lastly, if I do \\win 2019, we can see our file shares.

26
00:01:27,440 --> 00:01:32,560
And if we go to the local file system, we've got our scripts and binaries.

27
00:01:32,560 --> 00:01:36,390
And if we go and take a look at the access‑control list,

28
00:01:36,390 --> 00:01:38,490
those have been successfully migrated.

29
00:01:38,490 --> 00:01:40,110
Pretty clean, pretty useful.

30
00:01:40,110 --> 00:01:41,440
I think you'd agree.

31
00:01:41,440 --> 00:01:45,320
Without further ado, let's now shift to Azure File Sync.

32
00:01:45,320 --> 00:01:49,930
And so the use case here is you've got one or more local file servers,

33
00:01:49,930 --> 00:01:54,940
and you just have this mass of shared folders with or without DFS.

34
00:01:54,940 --> 00:01:57,170
How can you provide cloud tiering?

35
00:01:57,170 --> 00:01:59,750
How can you provide greater business continuity,

36
00:01:59,750 --> 00:02:01,720
disaster recovery, high availability?

37
00:02:01,720 --> 00:02:04,250
How can you easily do cloud backup?

38
00:02:04,250 --> 00:02:05,490
So that's what we're going to set up.

39
00:02:05,490 --> 00:02:07,840
I'm going to do this directly from this server.

40
00:02:07,840 --> 00:02:09,980
We'll go up into Azure, and as I mentioned,

41
00:02:09,980 --> 00:02:12,160
the first thing you'll want to do is create an

42
00:02:12,160 --> 00:02:13,970
instance of a Storage Sync Service.

43
00:02:13,970 --> 00:02:15,360
I've already created one.

44
00:02:15,360 --> 00:02:18,600
Notice that they are in fact regional resources.

45
00:02:18,600 --> 00:02:22,140
Ps‑storage‑sync, let's come in here,

46
00:02:22,140 --> 00:02:25,400
and let's go ahead and register a server first of all.

47
00:02:25,400 --> 00:02:29,340
We'll go to Registered servers and download the Azure File Sync

48
00:02:29,340 --> 00:02:32,740
agent from the Microsoft Download Center.

49
00:02:32,740 --> 00:02:34,250
Let me click Download.

50
00:02:34,250 --> 00:02:39,410
And let's see here, notice that it supports not only Server 2022,

51
00:02:39,410 --> 00:02:44,080
but there's an msi for 2019, 2016, and even 2012R2.

52
00:02:44,080 --> 00:02:50,090
Remember that one of the use cases of Azure File Sync is to help you move

53
00:02:50,090 --> 00:02:54,240
forward to decommission those old legacy file servers.

54
00:02:54,240 --> 00:02:58,330
So I'm going to open this msi, and we'll just run through this installer.

55
00:02:58,330 --> 00:03:01,310
Just a Next, Next, Finish kind of operation here.

56
00:03:01,310 --> 00:03:04,080
I'll accept the terms of the License Agreement.

57
00:03:04,080 --> 00:03:07,670
We'll install the Azure File Sync agent and the default directory.

58
00:03:07,670 --> 00:03:09,740
No proxy in my environment.

59
00:03:09,740 --> 00:03:15,210
I do, indeed, want to automatically update the agent with Windows Update,

60
00:03:15,210 --> 00:03:18,840
so I'll select that and click Next.

61
00:03:18,840 --> 00:03:19,810
All right, that's finished.

62
00:03:19,810 --> 00:03:20,920
Let's click Finish,

63
00:03:20,920 --> 00:03:24,660
and you'll find that the agent has just a minimal graphical

64
00:03:24,660 --> 00:03:27,760
interface in addition to the service, the Windows service,

65
00:03:27,760 --> 00:03:29,640
that runs in the background.

66
00:03:29,640 --> 00:03:32,340
Let's click OK here and get signed in.

67
00:03:32,340 --> 00:03:36,190
We're going to sign into not a sovereign cloud, but the public cloud.

68
00:03:36,190 --> 00:03:39,240
I'm not a Cloud Solution Provider.

69
00:03:39,240 --> 00:03:40,320
Let's sign in here.

70
00:03:40,320 --> 00:03:41,230
Oh boy!

71
00:03:41,230 --> 00:03:44,110
Looks like we've got a reliance on Internet Explorer.

72
00:03:44,110 --> 00:03:45,640
I can't believe that.

73
00:03:45,640 --> 00:03:49,350
So let me quickly take care of that by opening up Server Manager.

74
00:03:49,350 --> 00:03:51,140
You know what I'm going to do.

75
00:03:51,140 --> 00:03:54,160
And we'll go to Local Server, and we'll turn on that I,

76
00:03:54,160 --> 00:03:57,720
we'll turn off, rather, the IE, Internet Explorer,

77
00:03:57,720 --> 00:03:59,850
Enhanced Security Configuration.

78
00:03:59,850 --> 00:04:00,940
Yikes!

79
00:04:00,940 --> 00:04:03,240
Okay, let's try that again.

80
00:04:03,240 --> 00:04:08,840
And it's not liking it, so let's close out of the agent and let's start it again.

81
00:04:08,840 --> 00:04:09,350
Okay,

82
00:04:09,350 --> 00:04:14,310
so we'll sign in with my Azure AD account that has

83
00:04:14,310 --> 00:04:19,140
enough privileges to do this operation.

84
00:04:19,140 --> 00:04:22,560
I use Azure MFA, or multi‑factor authentication,

85
00:04:22,560 --> 00:04:25,940
so I'll want to take care of that.

86
00:04:25,940 --> 00:04:27,610
Once you've handled authentication,

87
00:04:27,610 --> 00:04:31,740
we need to map in and register with our Storage Sync Service.

88
00:04:31,740 --> 00:04:34,840
So I'll select my Subscription from the list,

89
00:04:34,840 --> 00:04:39,890
my Resource Group, and then ultimately the ps‑storage‑sync Storage Sync Service.

90
00:04:39,890 --> 00:04:41,540
Let's click Register.

91
00:04:41,540 --> 00:04:42,480
Handshake this in.

92
00:04:42,480 --> 00:04:52,000
Again, there's no reliance on an ExpressRoute circuit or a site‑to‑site VPN. We're going over TCP 443.