1 00:00:01,040 --> 00:00:03,220 What is Hyper‑V enhanced session mode? 2 00:00:03,220 --> 00:00:07,400 Well, this is simply the capability of accessing your Hyper‑V host, 3 00:00:07,400 --> 00:00:07,980 that is, 4 00:00:07,980 --> 00:00:12,500 the server that's running the Hyper‑V hypervisor, and which is hosting 5 00:00:12,500 --> 00:00:17,050 one or more virtual machines. And you can access from the perspective 6 00:00:17,050 --> 00:00:19,740 of the VM the Hyper‑V host's resources. 7 00:00:19,740 --> 00:00:24,830 Maybe you need to RDP into a VM and pull files from the host's file 8 00:00:24,830 --> 00:00:27,590 system. Or maybe you want to use the clipboard, 9 00:00:27,590 --> 00:00:31,990 the Windows clipboard, to copy and paste text or even binary 10 00:00:31,990 --> 00:00:34,790 data between the host and the virtual machine. 11 00:00:34,790 --> 00:00:36,950 That's what enhanced session mode is. 12 00:00:36,950 --> 00:00:41,670 You can mount fixed and removable disks from the host inside the VM. 13 00:00:41,670 --> 00:00:45,630 You can connect and print to printers that are connected to the hardware host. 14 00:00:45,630 --> 00:00:49,300 The limitation to enhanced session mode is that you have to use the 15 00:00:49,300 --> 00:00:53,240 VMConnect tool. You can't use another RDP client. 16 00:00:53,240 --> 00:00:55,020 You have to use the Hyper‑V one. 17 00:00:55,020 --> 00:00:58,910 Now, the good news is that we get VMConnect when you do an RSAT 18 00:00:58,910 --> 00:01:02,280 installation on Windows Client, so you will have it. And you can see in 19 00:01:02,280 --> 00:01:05,660 the connection flow there's local devices and resources, 20 00:01:05,660 --> 00:01:09,210 printer and clipboard, and if you click More, you can hook up to 21 00:01:09,210 --> 00:01:12,840 smart cards and other plug‑and‑play devices. 22 00:01:12,840 --> 00:01:18,090 Now with regard to Hyper‑V via memory, there is the concept of dynamic memory. 23 00:01:18,090 --> 00:01:21,100 Now this is, well, first of all, to take a step back, 24 00:01:21,100 --> 00:01:25,050 remember that when we create a virtual machine, we allocate it virtual 25 00:01:25,050 --> 00:01:28,520 resources that are actually coming from the Hyper‑V host. 26 00:01:28,520 --> 00:01:32,040 So if your Hyper‑V host has 32 GB of RAM. 27 00:01:32,040 --> 00:01:34,550 and then you're going to have N number of VMs, 28 00:01:34,550 --> 00:01:37,760 you're going to need to be careful about allocating RAM to 29 00:01:37,760 --> 00:01:40,700 the VMs to conserve RAM on the host. 30 00:01:40,700 --> 00:01:45,810 Dynamic memory allows you to specify a range that Hyper‑V host will 31 00:01:45,810 --> 00:01:49,010 choose dynamically as the VM is doing its work. 32 00:01:49,010 --> 00:01:52,240 It's a more efficient way to allocate host memory to VMs. 33 00:01:52,240 --> 00:01:54,840 Monitoring is something you should do anyway, 34 00:01:54,840 --> 00:01:58,590 but you'll want to monitor your VMs to set in the Hyper‑V 35 00:01:58,590 --> 00:02:00,840 memory settings a buffer percentage. 36 00:02:00,840 --> 00:02:01,490 In other words, 37 00:02:01,490 --> 00:02:04,920 how much of the allocated RAM that you've given to the VM 38 00:02:04,920 --> 00:02:08,010 should it always hold onto as a buffer? Again, 39 00:02:08,010 --> 00:02:10,760 you need to answer that question, and the way to do 40 00:02:10,760 --> 00:02:13,030 that is monitoring utilization, 41 00:02:13,030 --> 00:02:17,200 which you can do from the perspective of the Hyper‑V host or from the guest OS 42 00:02:17,200 --> 00:02:22,050 and the VM. You can implement quality of service in Hyper‑V in a number of ways, 43 00:02:22,050 --> 00:02:26,920 and quality of service simply means where you have VMs that may need dedicated 44 00:02:26,920 --> 00:02:30,200 extra capabilities or extra resources. 45 00:02:30,200 --> 00:02:34,090 So you can specify a memory weight percentage as well to 46 00:02:34,090 --> 00:02:38,100 prioritize host RAM allocation to certain VMs. 47 00:02:38,100 --> 00:02:38,420 Again, 48 00:02:38,420 --> 00:02:41,970 monitoring, you'll want to monitor in your VMs and the apps that are 49 00:02:41,970 --> 00:02:44,940 running on those VMs to guard against memory leaks. 50 00:02:44,940 --> 00:02:48,810 You want to make sure that you've got good alignment between the VM host 51 00:02:48,810 --> 00:02:53,720 and the virtual machine guests. We've got Hyper‑V integration services 52 00:02:53,720 --> 00:02:56,240 that you'll want to enable and keep up to date. 53 00:02:56,240 --> 00:02:56,860 And lastly, 54 00:02:56,860 --> 00:02:59,610 there is the question, maybe dynamic memory isn't a 55 00:02:59,610 --> 00:03:01,480 good fit for a particular VM. 56 00:03:01,480 --> 00:03:03,340 It's not a one‑size‑fits‑all. 57 00:03:03,340 --> 00:03:07,480 You may have a VM that's operating as a mail server or a database server where 58 00:03:07,480 --> 00:03:10,570 you want to give it a fixed amount of RAM, and that's it. 59 00:03:10,570 --> 00:03:19,000 The VM should have 100% of that RAM allocation 100% of the time. Again, you answer these questions through monitoring.