1 00:00:01,040 --> 00:00:03,220 Okay, let's get this party started. 2 00:00:03,220 --> 00:00:05,920 This is going to be a stout series of demos because 3 00:00:05,920 --> 00:00:07,410 we've got quite a bit of work to do. 4 00:00:07,410 --> 00:00:09,920 We're going to start with Storage Migration Service, 5 00:00:09,920 --> 00:00:11,840 and you're looking at the desktop. 6 00:00:11,840 --> 00:00:15,540 Actually, if I do a run and do a winver, 7 00:00:15,540 --> 00:00:18,350 it's actually a Windows Server 2019 machine. 8 00:00:18,350 --> 00:00:22,380 And I've specifically done that, so if I open up again, 9 00:00:22,380 --> 00:00:27,420 run win2019 as the host name. I've done that to show a use case of 10 00:00:27,420 --> 00:00:30,870 Storage Migration Service of taking the file shares, 11 00:00:30,870 --> 00:00:33,340 I have two here binaries and scripts, 12 00:00:33,340 --> 00:00:36,900 and we're going to move these to my mem3 virtual server, 13 00:00:36,900 --> 00:00:39,370 which is running Windows Server 2022. 14 00:00:39,370 --> 00:00:42,540 Let's say that we want to decommission this box, all right? 15 00:00:42,540 --> 00:00:45,330 So the front end we're going to use is Windows Admin Center, 16 00:00:45,330 --> 00:00:48,140 and to show how I got to this particular screen, 17 00:00:48,140 --> 00:00:50,070 let's go to All connections, 18 00:00:50,070 --> 00:00:56,240 and I've got my Windows 2019 box set up as a WAC Gateway. 19 00:00:56,240 --> 00:01:01,740 And then if I come down under my tools, I have Files & file sharing. 20 00:01:01,740 --> 00:01:07,190 And then we can enumerate the file shares specifically by moving to that tab 21 00:01:07,190 --> 00:01:11,430 where we can inspect if we want to binaries and scripts, 22 00:01:11,430 --> 00:01:14,150 which are our two file shares, okay? 23 00:01:14,150 --> 00:01:15,300 That's all well and good. 24 00:01:15,300 --> 00:01:20,100 Now as far as storage migration goes, let's go to Storage Migration Service. 25 00:01:20,100 --> 00:01:23,520 You have to remember that the extensibility of Windows Admin 26 00:01:23,520 --> 00:01:27,410 Center happens through the extensions UI. 27 00:01:27,410 --> 00:01:30,030 So if you don't see Storage Migration Service, 28 00:01:30,030 --> 00:01:33,040 we'll want to come over to Settings here in the upper right, 29 00:01:33,040 --> 00:01:35,640 and we'll want to go over to Extensions. 30 00:01:35,640 --> 00:01:38,640 And you can search the extensions gallery, 31 00:01:38,640 --> 00:01:40,770 bring that in as an installed extension. 32 00:01:40,770 --> 00:01:44,990 Let me do a search here for storage mig, and there it is. 33 00:01:44,990 --> 00:01:48,240 And you might have noticed, let me get rid of this filter, 34 00:01:48,240 --> 00:01:50,850 that the WAC interface, 35 00:01:50,850 --> 00:01:55,150 one of its hallmarks is the ability to have updates for these extensions. 36 00:01:55,150 --> 00:02:00,860 So it's a much more contemporary 21st‑century administrative surface, 37 00:02:00,860 --> 00:02:02,430 although unfortunately, 38 00:02:02,430 --> 00:02:07,310 I see that the capabilities in here generally aren't matching 39 00:02:07,310 --> 00:02:12,130 what's in the either Powershell interface natively or using a 40 00:02:12,130 --> 00:02:14,540 Microsoft Management Console. 41 00:02:14,540 --> 00:02:16,620 Anyway, get off your soapbox, Tim. 42 00:02:16,620 --> 00:02:22,310 Let's just go back to our server, and let's go back to Storage Migration Service, 43 00:02:22,310 --> 00:02:23,420 and let's do this thing. 44 00:02:23,420 --> 00:02:27,560 Storage Migration Service, all right, so here we go, 45 00:02:27,560 --> 00:02:31,870 migrate servers and file shares to Azure or Windows Server 2022 46 00:02:31,870 --> 00:02:34,710 without requiring apps or users to change anything. 47 00:02:34,710 --> 00:02:35,400 Nice. 48 00:02:35,400 --> 00:02:37,640 Let's click Install, 49 00:02:37,640 --> 00:02:42,660 and I am going to specify credentials that I know 50 00:02:42,660 --> 00:02:45,540 are good for both of my machines. 51 00:02:45,540 --> 00:02:49,740 I'll use these credentials for all connections and click Continue. 52 00:02:49,740 --> 00:02:51,440 Yes, I'll save Edge. 53 00:02:51,440 --> 00:02:52,390 I'll wait here, 54 00:02:52,390 --> 00:02:57,370 and you don't have to wait with me for WAC in conjunction with my 55 00:02:57,370 --> 00:03:01,540 local win2019 server to set up the service for us. 56 00:03:01,540 --> 00:03:02,120 Here we are. 57 00:03:02,120 --> 00:03:06,890 This is useful to read, although we can suppress ever seeing it again. 58 00:03:06,890 --> 00:03:10,500 We're going to create a job and do an inventory that gathers the 59 00:03:10,500 --> 00:03:13,540 file shares and configuration of our source, 60 00:03:13,540 --> 00:03:16,740 we're then going to do a copy, and then optionally, 61 00:03:16,740 --> 00:03:21,170 we can cut over where the new server actually takes over the identity of the 62 00:03:21,170 --> 00:03:25,340 old so that apps or users don't have to change anything. 63 00:03:25,340 --> 00:03:26,580 Let's click Close here. 64 00:03:26,580 --> 00:03:31,400 So, here we have our overview, it's giving us a running inventory. 65 00:03:31,400 --> 00:03:34,020 Now, of course, it's all 0's because we haven't done anything. 66 00:03:34,020 --> 00:03:38,770 Let's come down and go to New job, and I'm going to call this win2019‑, 67 00:03:38,770 --> 00:03:43,140 well, it doesn't like the dash, so I'll just leave that alone there. 68 00:03:43,140 --> 00:03:45,720 The source device can either be Windows Server, 69 00:03:45,720 --> 00:03:48,430 in or out of a failover cluster, Linux servers, 70 00:03:48,430 --> 00:03:49,620 or a NetApp array. 71 00:03:49,620 --> 00:03:50,670 I'm going to do Windows. 72 00:03:50,670 --> 00:03:53,140 Let's click OK. 73 00:03:53,140 --> 00:03:56,160 Now some points I want to call out on this prerequisite. 74 00:03:56,160 --> 00:04:00,610 Again, you can reach all the way back to Windows Server 2003. 75 00:04:00,610 --> 00:04:03,230 You can migrate in and out of clusters. 76 00:04:03,230 --> 00:04:05,740 Some best practices here. 77 00:04:05,740 --> 00:04:07,620 Not supported, this is important. 78 00:04:07,620 --> 00:04:11,060 Domain migrations or cutover of domain controllers, 79 00:04:11,060 --> 00:04:14,250 so we're talking about member servers only, 80 00:04:14,250 --> 00:04:14,780 okay? 81 00:04:14,780 --> 00:04:16,740 Let's click Next. 82 00:04:16,740 --> 00:04:18,370 On the enter credential step, 83 00:04:18,370 --> 00:04:22,450 it looks like a dun goofed by specifying a user principal name. 84 00:04:22,450 --> 00:04:25,150 This makes sense because if you're cutting over or 85 00:04:25,150 --> 00:04:28,040 planning to migrate from a really old server, 86 00:04:28,040 --> 00:04:30,780 maybe the UPN support isn't quite as good, 87 00:04:30,780 --> 00:04:34,640 so I'll do the old school NetBIOS domain name, 88 00:04:34,640 --> 00:04:40,540 you know, not the DNS, but the NetBIOS domain name backslash username. 89 00:04:40,540 --> 00:04:42,940 Now am I going to include administrative shares? 90 00:04:42,940 --> 00:04:46,210 No, and I'm not going to migrate from a failover cluster either, 91 00:04:46,210 --> 00:04:48,740 so let's click Next. 92 00:04:48,740 --> 00:04:52,980 All right, so we're going to use this machine obviously as our orchestrator. 93 00:04:52,980 --> 00:04:55,140 I guess I should have said that before. 94 00:04:55,140 --> 00:04:57,990 The Orchestrator server is simply the machine that you 95 00:04:57,990 --> 00:05:00,440 run the Storage Migration Service on, 96 00:05:00,440 --> 00:05:06,170 and it looks like WAC is using my win2019 box as an orchestrator, 97 00:05:06,170 --> 00:05:07,750 which is totally fine. 98 00:05:07,750 --> 00:05:10,040 Looks like there's no dependencies. 99 00:05:10,040 --> 00:05:14,610 Now I would need the Storage Migration Service installed if it weren't already, 100 00:05:14,610 --> 00:05:15,950 and that's what would happen now. 101 00:05:15,950 --> 00:05:20,110 So let's click Next, and let's do an inventory scan. 102 00:05:20,110 --> 00:05:20,860 Now, again, 103 00:05:20,860 --> 00:05:23,870 if we were on a separate machine acting as the orchestrator, 104 00:05:23,870 --> 00:05:26,880 that would be contributing the network, the CPU, 105 00:05:26,880 --> 00:05:27,710 the memory. 106 00:05:27,710 --> 00:05:30,400 I'm going to do that on win2019 itself, 107 00:05:30,400 --> 00:05:33,840 and I'm going to add in that particular device. 108 00:05:33,840 --> 00:05:37,830 We can do an Active Directory search here for win2019. 109 00:05:37,830 --> 00:05:39,740 Let me click Search. 110 00:05:39,740 --> 00:05:44,740 Here is our machine, let's bring that in. 111 00:05:44,740 --> 00:05:48,140 We'll hit Validate. 112 00:05:48,140 --> 00:05:50,940 Let's validate that machine. 113 00:05:50,940 --> 00:05:55,140 Looks like the server passed validation, let's click the link here. 114 00:05:55,140 --> 00:05:57,740 This is just letting us know metadata. 115 00:05:57,740 --> 00:06:06,000 Okay, warning on CPU, that's fine, it's a relatively low‑powered VM, so that's good to know.