1
00:00:01,540 --> 00:00:06,270
Lastly, we have migrating IIS and Hyper‑V Workloads to Windows

2
00:00:06,270 --> 00:00:12,020
Server 2022. First let's take up the issue of our IIS websites.

3
00:00:12,020 --> 00:00:16,720
Now, understand in this module, I'm not concerned with rehosting

4
00:00:16,720 --> 00:00:19,740
an IIS web application to Azure.

5
00:00:19,740 --> 00:00:23,070
Instead, we have say, a brand spanking new server running

6
00:00:23,070 --> 00:00:27,530
Windows Server 2022, and we want to move an existing IIS

7
00:00:27,530 --> 00:00:30,240
website from an older server to it.

8
00:00:30,240 --> 00:00:33,570
What Microsoft recommends here, and this is your exam alert, is to do

9
00:00:33,570 --> 00:00:36,690
a synchronization using the Web Deployment Tool,

10
00:00:36,690 --> 00:00:42,320
the msdeploy.exe, which you can install on your source and destination

11
00:00:42,320 --> 00:00:46,560
servers. And when you run msdeploy from the command prompt,

12
00:00:46,560 --> 00:00:50,940
there's a number of verbs that you can choose here. It's really cool, and

13
00:00:50,940 --> 00:00:54,830
actually, this msdeploy tool can be helpful in Azure as well.

14
00:00:54,830 --> 00:00:55,490
For example,

15
00:00:55,490 --> 00:00:58,240
if you're interested in setting up a web front end for your

16
00:00:58,240 --> 00:01:02,840
application and you've got X number of virtual machines,

17
00:01:02,840 --> 00:01:07,740
they will definitely need their site content and IIS synchronized.

18
00:01:07,740 --> 00:01:12,240
Well, scripting this out to perform regular, bidirectional syncs can be

19
00:01:12,240 --> 00:01:15,840
a very handy tool to have in your tool belt.

20
00:01:15,840 --> 00:01:19,720
The downside is that it is, in fact, a compiled executable, so you

21
00:01:19,720 --> 00:01:24,260
don't have the standardized syntax that we have with PowerShell. So

22
00:01:24,260 --> 00:01:29,120
here we can see we're using msdeploy with the sync verb, just simply

23
00:01:29,120 --> 00:01:34,320
specifying the friendly website name and IIS Manager on the source and

24
00:01:34,320 --> 00:01:36,340
destination computers.

25
00:01:36,340 --> 00:01:40,750
And here, we're using the redirection operator, that greater than symbol, to

26
00:01:40,750 --> 00:01:45,840
create a log file so we can see the results. Simple as that.

27
00:01:45,840 --> 00:01:46,450
Likewise,

28
00:01:46,450 --> 00:01:52,060
a relatively simple process is migrating Hyper‑V to Windows Server 2022.

29
00:01:52,060 --> 00:01:55,740
Now, the slide says hosts. It's not so much the host you're

30
00:01:55,740 --> 00:01:58,800
concerned with, I mean you're going to install the Hyper‑V role

31
00:01:58,800 --> 00:02:01,370
on your Windows Server 2022 machine,

32
00:02:01,370 --> 00:02:06,330
you're concerned about the VMs. And here, the recommendation from Microsoft if

33
00:02:06,330 --> 00:02:11,670
you're not using failover clustering is to live migrate those VMs outside of

34
00:02:11,670 --> 00:02:15,760
failover clustering. And to simulate live migration,

35
00:02:15,760 --> 00:02:20,720
you've got the Hyper‑V PowerShell command Move‑V1, where we're

36
00:02:20,720 --> 00:02:24,940
just specifying the logical label name of the VM,

37
00:02:24,940 --> 00:02:29,500
the destination Hyper‑V host, that you do want to include storage, and

38
00:02:29,500 --> 00:02:36,000
then, where do you want to store the VHD and configuration? Let's get into our second and last demo.