1
00:00:01,140 --> 00:00:02,780
Now what took me a long,

2
00:00:02,780 --> 00:00:06,220
long time was to discover that the scan command is hidden

3
00:00:06,220 --> 00:00:08,630
depending on your resolution actually.

4
00:00:08,630 --> 00:00:13,640
See, I select this and validate runs your initial prereq check,

5
00:00:13,640 --> 00:00:17,170
but I'm like why are there no shares showing up down here?

6
00:00:17,170 --> 00:00:18,330
Well, you know what it is?

7
00:00:18,330 --> 00:00:22,300
Select the server, and hidden here, Start scan.

8
00:00:22,300 --> 00:00:26,640
That took way too long for me to figure out, it really did.

9
00:00:26,640 --> 00:00:29,940
After the scan, which didn't take long in my case,

10
00:00:29,940 --> 00:00:33,350
I have my scripts and binaries folders listed down below,

11
00:00:33,350 --> 00:00:36,650
and we can see some metadata in terms of how we're sharing them,

12
00:00:36,650 --> 00:00:40,790
what the size is, succeeded failed, file enumeration,

13
00:00:40,790 --> 00:00:42,140
and if we click one,

14
00:00:42,140 --> 00:00:46,260
it just gives us all the specific meta that we would want to know,

15
00:00:46,260 --> 00:00:47,630
and actually let me show you this,

16
00:00:47,630 --> 00:00:51,240
if I go and take a look at say the binaries shared folder,

17
00:00:51,240 --> 00:00:52,930
I just want to go over to security,

18
00:00:52,930 --> 00:00:57,280
I just want you to see that I have some non‑default DACL,

19
00:00:57,280 --> 00:01:03,110
or discretionary access control list, entries here and these could be local or,

20
00:01:03,110 --> 00:01:04,960
in my case, they're domain groups.

21
00:01:04,960 --> 00:01:08,300
I've got an automation team, and we would presumably,

22
00:01:08,300 --> 00:01:13,940
I think you'd agree, want that to migrate along with the file share and its data.

23
00:01:13,940 --> 00:01:16,870
If we plan on actually cutting over the server,

24
00:01:16,870 --> 00:01:21,540
we have to be apprised as far as IP addressing as you can see,

25
00:01:21,540 --> 00:01:25,640
as well as the volume structure and layout on that machine.

26
00:01:25,640 --> 00:01:25,960
Good.

27
00:01:25,960 --> 00:01:28,560
So there is our enumeration here.

28
00:01:28,560 --> 00:01:30,890
We've got three shares, this MTA.

29
00:01:30,890 --> 00:01:33,740
What's this MTA one?

30
00:01:33,740 --> 00:01:35,840
MTATempStore.

31
00:01:35,840 --> 00:01:38,260
Yeah, well that one, unfortunately, is skipped.

32
00:01:38,260 --> 00:01:39,280
We don't need that.

33
00:01:39,280 --> 00:01:40,910
I just want my user share.

34
00:01:40,910 --> 00:01:46,190
So let's click Next, enter credentials for the destination device.

35
00:01:46,190 --> 00:01:49,100
Again it brings in the default I had before,

36
00:01:49,100 --> 00:01:54,140
so I'm going to need to modify this into old school format here.

37
00:01:54,140 --> 00:01:55,740
Let's click Next.

38
00:01:55,740 --> 00:01:59,450
The destination is going to be my mem1 server.

39
00:01:59,450 --> 00:02:04,060
So let me do Use an existing server, and then we're going to browse for that.

40
00:02:04,060 --> 00:02:08,060
But what I want you to see here just as a possibility is that we could

41
00:02:08,060 --> 00:02:12,640
create a new Azure VM to migrate directly into Azure.

42
00:02:12,640 --> 00:02:14,110
Don't transfer files.

43
00:02:14,110 --> 00:02:15,840
Well, no, we don't want that.

44
00:02:15,840 --> 00:02:18,670
So you can either go directly into Azure,

45
00:02:18,670 --> 00:02:23,200
there is a nice shortcut path for that, or if you're going to stay local,

46
00:02:23,200 --> 00:02:26,140
use an existing mem1.

47
00:02:26,140 --> 00:02:31,930
Let's browse, mem1, search, there is the server,

48
00:02:31,930 --> 00:02:35,300
let's bring that in, Scan,

49
00:02:35,300 --> 00:02:40,280
and let's make sure that that Windows Server 2022 member server has what it

50
00:02:40,280 --> 00:02:45,940
takes as it were to receive the file share data from our source.

51
00:02:45,940 --> 00:02:46,450
Nuts!

52
00:02:46,450 --> 00:02:50,220
You know something, I don't even think that mem1 is online.

53
00:02:50,220 --> 00:02:51,890
Let me click Browse again.

54
00:02:51,890 --> 00:02:56,940
I actually want Windows Server, it's actually mem3.

55
00:02:56,940 --> 00:02:58,340
Whoops.

56
00:02:58,340 --> 00:03:06,040
So let's resolve mem3, and let's add that in and let's do a scan there.

57
00:03:06,040 --> 00:03:10,520
Okay, so here we can see that mem3 just has a single system volume.

58
00:03:10,520 --> 00:03:15,100
We definitely have enough space 165 MB.

59
00:03:15,100 --> 00:03:18,580
Notice that we've got compatibility with Azure File Sync,

60
00:03:18,580 --> 00:03:20,170
which we'll do later in this demo.

61
00:03:20,170 --> 00:03:22,840
I'm going to stay local here, in this case.

62
00:03:22,840 --> 00:03:24,650
Select the shares to transfer.

63
00:03:24,650 --> 00:03:27,050
I'm going to deselect that MTA.

64
00:03:27,050 --> 00:03:30,640
I just want to include binaries and scripts here.

65
00:03:30,640 --> 00:03:32,030
Okay, looking good so far.

66
00:03:32,030 --> 00:03:35,040
Let's click Next.

67
00:03:35,040 --> 00:03:38,440
Here we're asked to adjust our meta, metadata.

68
00:03:38,440 --> 00:03:38,970
Basically,

69
00:03:38,970 --> 00:03:44,150
we can have the storage migration service do a checksum to make sure that

70
00:03:44,150 --> 00:03:48,210
the copied files are exactly the same as the source.

71
00:03:48,210 --> 00:03:50,540
That's a good idea in practice.

72
00:03:50,540 --> 00:03:53,210
We can set a maximum job duration.

73
00:03:53,210 --> 00:03:57,030
In terms of local users and groups, those will be replicated.

74
00:03:57,030 --> 00:04:00,040
How do you want to handle name collisions,

75
00:04:00,040 --> 00:04:03,940
and then we've got retry and delay logic as well.

76
00:04:03,940 --> 00:04:06,640
So let's click Next.

77
00:04:06,640 --> 00:04:09,330
Alright, so another related Windows service,

78
00:04:09,330 --> 00:04:12,450
Storage Migration Service is the engine that you're

79
00:04:12,450 --> 00:04:14,540
going to need on your orchestrator.

80
00:04:14,540 --> 00:04:17,600
The destination machine is going to need the storage

81
00:04:17,600 --> 00:04:21,660
migration service proxy and that's just what happened here

82
00:04:21,660 --> 00:04:24,450
on the Install required features step.

83
00:04:24,450 --> 00:04:26,740
Let's click Next.

84
00:04:26,740 --> 00:04:31,540
Let's validate our Windows 2019 source machine.

85
00:04:31,540 --> 00:04:32,760
Got a warning on that.

86
00:04:32,760 --> 00:04:33,610
What was that?

87
00:04:33,610 --> 00:04:37,850
Well, the CPU I'm fine with, as long as I don't get any errors,

88
00:04:37,850 --> 00:04:38,890
I think I'm fine.

89
00:04:38,890 --> 00:04:40,440
Okay.

90
00:04:40,440 --> 00:04:41,510
Review our settings.

91
00:04:41,510 --> 00:04:43,640
Okay, we can proceed here.

92
00:04:43,640 --> 00:04:44,930
It looks like we're ready to go.

93
00:04:44,930 --> 00:04:50,610
So we've got 23 files to go from Windows 2019 over to mem3.

94
00:04:50,610 --> 00:04:52,830
Let's go ahead and start the transfer.

95
00:04:52,830 --> 00:04:55,200
Alright, it appears to have succeeded,

96
00:04:55,200 --> 00:04:58,270
but I have to say this is a bit inscrutable that

97
00:04:58,270 --> 00:05:01,660
the progress is 99.99% complete.

98
00:05:01,660 --> 00:05:04,440
Now we can come down further here in the report,

99
00:05:04,440 --> 00:05:08,440
actually up on top and look at transfer detail,

100
00:05:08,440 --> 00:05:11,170
source, processed, files, okay, we're good,

101
00:05:11,170 --> 00:05:16,630
SMB details, there is our two boulders that were completely migrated.

102
00:05:16,630 --> 00:05:18,540
So far, so good.

103
00:05:18,540 --> 00:05:22,920
And now we have a very important question about cutting over to the new server.

104
00:05:22,920 --> 00:05:26,640
How do we want to handle this in terms of credentials?

105
00:05:26,640 --> 00:05:30,190
I spent some time reformatting my cred so I'm certainly going to

106
00:05:30,190 --> 00:05:32,950
use those stored credentials on this page,

107
00:05:32,950 --> 00:05:35,640
so let's click Next.

108
00:05:35,640 --> 00:05:39,350
Now on the left, we have our source network adapter and,

109
00:05:39,350 --> 00:05:42,750
it's as any good server should be, statically assigned,

110
00:05:42,750 --> 00:05:45,240
or at least, a DHCP reservation.

111
00:05:45,240 --> 00:05:50,020
I'm going to cut over that information to the destination because,

112
00:05:50,020 --> 00:05:55,040
again, the idea is that we don't want to disrupt connectivity here.

113
00:05:55,040 --> 00:05:59,920
Subnet, I believe, means subnet mask, that's pretty unfortunately named,

114
00:05:59,920 --> 00:06:05,300
and then my gateway is going to be in my environment 10.1.10.1.

115
00:06:05,300 --> 00:06:09,440
Now we're going to want to rename the source computer to avoid a conflict.

116
00:06:09,440 --> 00:06:12,740
We can do either random or we can choose a name.

117
00:06:12,740 --> 00:06:16,340
I'm going to do 2019old.

118
00:06:16,340 --> 00:06:19,150
Is that within the NetBIOS 15‑character limit?

119
00:06:19,150 --> 00:06:19,780
Yes, it is.

120
00:06:19,780 --> 00:06:26,690
Our destination network adapter on my server is this one here via Ethernet.

121
00:06:26,690 --> 00:06:27,770
Okay, looking good.

122
00:06:27,770 --> 00:06:30,340
Let's click Next.

123
00:06:30,340 --> 00:06:31,770
Configuring the mapping.

124
00:06:31,770 --> 00:06:32,740
Alright.

125
00:06:32,740 --> 00:06:37,280
What is our cut over timeout, and what are our Active Directory credentials?

126
00:06:37,280 --> 00:06:40,060
Source credentials will be used if not provided.

127
00:06:40,060 --> 00:06:40,690
That's fine.

128
00:06:40,690 --> 00:06:42,940
So let me click Next.

129
00:06:42,940 --> 00:06:45,220
Again, we want to do a validation here.

130
00:06:45,220 --> 00:06:49,890
While we're waiting, the original name of the source server is Win2019,

131
00:06:49,890 --> 00:06:53,540
the new host name will be win2019old.

132
00:06:53,540 --> 00:06:54,720
Now this is important.

133
00:06:54,720 --> 00:06:55,210
Remember,

134
00:06:55,210 --> 00:06:58,420
that we're subsuming or taking over the original server

135
00:06:58,420 --> 00:07:03,160
name and it's a bit unfortunate because my mem3timw.info

136
00:07:03,160 --> 00:07:09,960
is a Windows server 2022 box, and it's going to be known from now on as win2019,

137
00:07:09,960 --> 00:07:11,490
which again, it's unfortunate.

138
00:07:11,490 --> 00:07:14,680
So make sure you're not hardcoding anything like a

139
00:07:14,680 --> 00:07:17,340
version in your server host name.

140
00:07:17,340 --> 00:07:19,020
That's fine, in this example, though.

141
00:07:19,020 --> 00:07:22,240
So let's start the cut over here by clicking Next,

142
00:07:22,240 --> 00:07:27,840
and then selecting our row, Start cutover.

143
00:07:27,840 --> 00:07:29,040
There we go.

144
00:07:29,040 --> 00:07:33,340
Storage migration will create a temporary account here

145
00:07:33,340 --> 00:07:35,310
and then delete that temporary account.

146
00:07:35,310 --> 00:07:40,000
It's going to need to reboot the machines as well. So we'll let that happen.