00-CLIENT HYPER-V: BASICS AND OVERVIEW

Transcription

1 00-CLIENT HYPER-V: BASICS AND OVERVIEW 1

2 Web location for this presentation: Click on Meeting Notes or contact me by at 2

3 SUMMARY "Desktop Hyper-V", which is part of some editions of Windows 8.1 and 10, is a program that lets you run many Windows.. or Linux operating systems and apps as "guests" inside a "virtual machine". A "virtual machine" is a no-cost computer that is created entirely by means of software. 3

4 TOPICS DEMONSTRATION OF A "WINDOWS 7" VIRTUAL MACHINE DEMONSTRATION OF AN "UBUNTU" LINUX VIRTUAL MACHINE DEMONSTRATION OF A NESTED VIRTUAL MACHINE 4

5 TOPICS (continued) VIRTUAL MACHINE TERMINOLOGY HARDWARE REQUIREMENTS FOR RUNNING "HYPER-V" HOST OPERATING SYSTEMS THAT HAVE "HYPER-V" BUNDLED 5

6 TOPICS (continued) GUEST OPERATING SYSTEMS THAT YOU CAN RUN IN HYPER-V USING A VIRTUAL MACHINE IMPORTING AND EXPORTING FREE VIRTUAL MACHINES FROM MICROSOFT 6

7 DEMONSTRATION OF "WINDOWS 7 PROFESSIONAL" RUNNING INSIDE A VIRTUAL MACHINE: 7

8 "Host" computer running Windows 10 Pro Virtual Machine Program Virtual Machine Guest Operating System Hyper-V program Virtual Machine running Windows 7 Professional Web browser running inside the virtual machine 8

9 9

10 DEMONSTRATION OF "UBUNTU" LINUX RUNNING INSIDE A VIRTUAL MACHINE: 10

11 "Host" computer running "Windows 10 Pro" Virtual Machine Program Virtual Machine Guest Operating System Hyper-V program Virtual Machine running "Ubuntu" Linux Web browser running inside the virtual machine 11

12 12

13 "Ubuntu", "Debian", and "Fedora Workstation" Linux all run reasonably well inside virtual machines. "Linux Mint", which is the most popular distribution of Linux, does not run well inside virtual machines where it generates a lot of display-related error messages. 13

14 All of the distributions of Linux that we have tried in "Hyper-V" have two unresolvable issues: Issue 1: No sound capability Issue 2: Monitor resolution problems 14

15 DEMONSTRATION OF A NESTED VIRTUAL MACHINE: 15

16 "Host" computer running Windows 10 Pro Virtual Machine Program Guest Operating System Hyper-V program Virtual Virtual Machine running Windows 10 Enterprise Evaluation Hyper-V program (nested) Virtual Machine running "Windows 10 Enterprise Evaluation (nested) 16

17 17

18 18

19 19

20 20

21 A nested "virtual machines" saves wear and tear on the Registry of a Windows host computer for when you need to test or demonstrate virtual machines often. 21

22 VIRTUAL MACHINE TERMINOLOGY: 22

23 "Virtual machines" let you run one or more additional computers inside your existing computer. Your existing real physical computer is called the "host computer", or the "parent partition". 23

24 "Virtual machines" are also called "guests" or "child partitions". An operating system that runs inside a virtual machine is called a "guest operating system". 24

25 A "virtual machine" is a set of computer files and/or folders that can simulate an entire real computer. 25

26 A "virtual machine program" is a software application that you can use to create, configure, modify, clone, back up, and run a "virtual machine". 26

27 When you use a virtual machine, the software and hardware in it is oblivious to the fact that the hardware of the virtual machine is created by the "virtual machine program". 27

28 When you play, run, or start a "virtual machine", the "virtual machine program" provides a set of software-generated computer hardware for the "virtual machine". 28

29 When play, run, or start a "virtual machine", a single window pops up. This window represents the "virtual desktop" or "virtual monitor" of your "virtual machine". 29

30 "Host" computer (= your real computer) Virtual Machine Program Virtual Machine Program Virtual Machine Guest Operating System Virtual Machine Guest Operating System 30

31 "Host" computer (= your real computer) Virtual Machine Program Virtual Machine Guest Operating System 31

32 "Host" computer (= your real computer) Virtual Machine Program Virtual Machine Program Virtual Machine Guest Operating System 32

33 "Host" computer (= your real computer) Virtual Machine Program Virtual Machine Program Virtual Machine Guest Operating System Virtual Machine 33

34 "Host" computer (= your real computer) Virtual Machine Program Virtual Machine Program Virtual Machine Guest Operating System Virtual Machine Guest Operating System 34

35 HOST SYSTEM REQUIREMENTS FOR RUNNING "HYPER-V" 35

36 "Hyper-V" is a "virtual machine program", that is bundled into Windows 8.x Pro 64-bit Windows 8.x Enterprise 64-bit Windows 10 Pro 64-bit Windows 10 Education 64-bit Windows 10 Enterprise 64-bit or Windows Server 2008/2012/

37 The "V" in "Hyper-V" stands for "viridium" which is a shade of blue green that has more blue than green In Microsoft's documentation the Hyper-V that is inside Windows.. desktop operating systems is called "Client Hyper-V" 37

38 The "Hyper-V" virtual machine program is not available on any desktop product version of Windows.. prior to Windows

39 The "Hyper-V" virtual machine program is not available on Windows 8.x (core edition) or Windows 10 Home or Windows 10 S 39

40 "HYPER-V" is a bundled part of some editions of Windows 8.x, or Windows 10 "VMWARE WORKSTATION PLAYER" AND "VIRTUALBOX" software programs that are free for noncommercial use that run in "Windows.." or "Linux.." hosts 40

41 If you are currently running "Windows 10 Home" in your computer and you insist on running "Hyper-V", here is what an upgrade to "Windows 10 Pro 64-bit" will cost from inside the online "Store" in "Windows 10 Home 64-bit": 41

42 42

43 An upgrade to "Windows 10 Pro 64-bit" will be cheaper when you buy it from a thirdparty software reseller: 43

44 44

45 Alternatively, you can run Hyper-V for free if you install the free, time-limited "Windows 10 Enterprise Evaluation 64-bit" into a spare computer or a spare hard drive for your existing computer: 45

46 My "how-to" documentation on downloading and installing the free "Windows 10 Enterprise Evaluation" is located at winhardsig/win10/win10enteval. pdf 46

47 If you are running "Windows 10 Pro", "Windows 10 Education", or "Windows 10 Enterprise" in the "Boot Camp" partition of a MacOS computer, "Hyper-V" will not work. However "VirtualBox" and "VMware Workstation Player" (which are both free for non-commercial use) runs well in the "Boot Camp" partition of a MacOS computer. 47

48 "HYPER-V" IS NOT COMPATIBLE WITH OTHER "VIRTUAL MACHINE PROGRAMS": 48

49 In a Windows 8.x or 10 host computer, the HYPER-V program is not compatible with "VIRTUALBOX" or "VMWARE WORKSTATION PLAYER": If you install HYPER-V, you will be unable to install VIRTUALBOX" or "VMWARE WORKSTATION PLAYER" and vice versa 49

50 In a Windows 8.x or 10 host computer, the HYPER-V program is not compatible with "VMWARE WORKSTATION PRO". If you install HYPER-V, you will be unable to install "VMWARE WORKSTATION PRO" and vice versa 50

51 DIFFERENCE BETWEEN "VIRTUAL MACHINES" AND "CONTAINERS": 51

52 "Virtual machines" give you an entire virtualized hardware computer created by software. "Containers" give you a virtualized partial clone of part of the "bins/libs/registry" your host operating system in order to separate one or more application programs from "seeing" each other. 52

53 Physical Real Computer 53

54 Physical Real Computer 54

55 Reference for the previous graphic: mp.org/a-beginnerfriendly-introduction-tocontainers-vms-anddocker-79a9e3e119b 55

56 "GENERATION 1" VIRTUAL MACHINES VERSUS "GENERATION 2" VIRTUAL MACHINES IN "HYPER-V": 56

57 When you create a new virtual machine in the "Hyper-V" program, you have to select between a "Generation 1" virtual machine or a "Generation 2 "virtual machine: 57

58 A "Generation 1" virtual machine has a virtual motherboard with a virtual BIOS chip, an IDE hard drive controller for the bootable virtual hard drive that has a Master Boot Record, an optional SCSI hard drive controller for data hard drives, and a virtual sound card if the guest operating system supports Secure Boot or is able to host a Remote Desktop connection 58

59 A "Generation 2" virtual machine has a virtual motherboard with a virtual UEFI chip with a "Secure Boot" module, a SCSI hard drive controller, and a virtual sound card if the guest operating system supports Secure Boot or is able to host a Remote Desktop connection 59

60 Virtual machines running in "Hyper-V" have limited virtual hardware options relative to virtual machines running in VirtualBox or VMware Player Workstation: 60

61 "Hyper-V" provides you with a virtual machine that has either a virtual IDE hard drive controller or a virtual SCSI hard drive controller, no virtual USB ports, and a virtual sound card that only works with the some but not all editions of "Windows Vista", "Windows 7", "Windows 8.1", or "Windows 10" 61

62 "HYPER-V" PROVIDES YOU WITH VIRTUAL MACHINES THAT RUN FASTER THAN OTHER "VIRTUAL MACHINE PROGRAMS" 62

63 Hyper-V runs dramatically faster relative to VirtualBox and VMware Workstation Player: Because of Microsoft's "VMBus" technology, an operating system and software apps running inside a Hyper-V virtual machine will always run faster than the same operating system and software apps running inside "Virtualbox" or "VMware Workstation Player". 63

64 64

65 For "Windows.." operating systems running inside Hyper-V as a guest operating system, the ability to communicate with the VMBus has to be built into the kernel of "Windows.." (which is true for "Windows XP", "Windows Vista", "Windows 7", "Windows 8", and "Windows 8.1") 65

66 For distros of the "GNU/Linux" operating system running inside "Hyper-V" as guest operating systems, the ability to communicate with VMBus is called "Linux Integration Services" and it is either built in by the developer of a Linux distribution or you can add it in yourself by re-compiling the Linux kernel. 66

67 Reference: 67

68

69 Because of VMbus, an operating system and software apps running inside a virtual machine inside Hyper-V will run faster than if the same operating system and software apps were installed directly onto the hardware host computer! 69

70 HYPER-V IS THE ONLY FREE "VIRTUAL MACHINE PROGRAM" THAT LETS YOU CREATE A VIRTUAL MOTHERBOARD WITH A VIRTUAL "SECURE BOOT" MODULE: 70

71 The motherboards of most Windows.. computers that have been sold after October 2012 have a "UEFI with a Secure Boot module" instead of a BIOS chip. 71

72 SECURE BOOT MODULE UEFI (= "UEFI BIOS") 72

73 For details about "Secure Boot", see inhardsig/biostouefi/biostou EFI.pdf 73

74 Hyper-V can provide a virtual motherboard that has a virtual UEFI chipset with a virtual "Secure Boot" module while "VirtualBox" and "VMware Workstation Player" are unable to do so 74

75 (However, the not-free "VMware Workstation Pro" can create a virtual motherboard that has UEFI chipset with "Secure Boot". If you use the not-free "VMware Workstation Pro" to create a virtual machine that has and UEFI with "Secure Boot", then that virtual machine will run in the free "VMware Workstation Player".) 75

76 76

77 "VirtualBox" makes virtual motherboards that have a virtual legacy BIOS chip. (For some older operating systems, "VirtualBox" lets you create a virtual motherboard with an "EFI" chip which is a predecessor of the current "UEFI" chips.) 77

78 HYPER-V CANNOT PROVIDE A VIRTUAL MACHINE WITH A VIRTUAL SATA HARD DRIVE CONTROLLER : 78

79 Hyper-V can only provide virtual SCSI or IDE hard drive controllers while "VirtualBox" and "VMware Workstation Player" can also provide virtual SATA hard drive controllers 79

80 .vhd VIRTUAL HARD DRIVE FILES VERSUS.vhdx VIRTUAL HARD DRIVE FILES 80

81 81

82 82

83 By default, "Hyper-V" stores all of your *.vhd and *.vhdx virtual hard drive files at C:\Users\Public\"Public Documents"\Hyper-V\Virtual Hard Disks\ 83

84 Like real hard drives,.vhd and.vhdx virtual hard drives sometimes get corrupted. When a.vhd or.vhdx virtual hard drives become corrupted, try to repair it with "Disk Error Checking" or "chkdsk" from inside the "guest operating system" 84

85 If this does not fix the virtual hard drive, you can use various notfree hard drive utility programs to recover the data files from the virtual hard drive. 85

86 We use the not-free "BitRecovery VHD Recovery Wizard" to retrieve data files from corrupted.vhd and.vhdx virtual hard disk files. You can test it in "trial mode" for free to see if it can recover files from the corrupted virtual hard drive prior to purchasing it. 86

87 To get a "trial copy" of "BitRecovery VHD Recovery Wizard", go to 87

88 WHERE DOES HYPER-V STORE THE OTHER CONFIGURATION FILES FOR IT'S VIRTUAL MACHINES? 88

89 Hyper-V stores the other configuration files for your virtual machines at C:\ProgramData\Microsoft\Wind ows\hyper-v\ 89

90 90

91 Most of the configuration information that pertains to a specific virtual machine is stored at C:\ProgramData\Microsoft\Wind ows\hyper-v\"virtual Machines"\ 91

92 92

93 93

94 .avhdx files =snapshot differential file =differencing disk files used for virtual machine checkpoints.vmcx files = virtual machine configuration data that is stored in binary file format 94

95 .vmrs files =Virtual machine runtime state information that is stored in binary file format. Checkpoints are stored in multiple checkpoint files. Each checkpoint creates a configuration file and runtime state file 95

96 HYPER-V PROVIDES YOU WITH AN EXPORT CAPABILITY FOR MAKING A BACKUP COPY OF A VIRTUAL MACHINE: 96

97 When making a backup copy of a virtual machine in "Hyper-V", you have to use the export command in the "Hyper-V Manager" window. Ditto for VirtualBox 97

98 If you are unable to export or move a virtual machine in Hyper-V, get into "Settings" for the virtual machine and delete the "Checkpoint subtree" and any non-existent virtual or real hard drives that are attached to the virtual machine. Then you should be able to export or move the virtual machine. 98

99 "HYPER-V" PROVIDES YOU WITH A VIRTUAL NETWORK TO CONNECT VIRTUAL MACHINES TO YOUR REAL LOCAL NETWORK 99

100 Like all "virtual machine programs", Hyper-V provides you with virtual network devices to connect your virtual machines to your real local network: 100

101 A "Generation 1" virtual machine in Hyper-V provides you with both a virtual Gigabit Ethernet switch(s) and a virtual Gigabit Ethernet adapter(s) A "Generation 2" virtual machine in Hyper-V only provides you with a virtual Gigabit Ethernet adapter(s) 101

102 A virtual machine running in Hyper-V has to connect to your real local network through a virtual network switch. A "Default Switch" is automatically created when you first install Hyper-V 102

103 "Default Switch" will automatically connect itself by means of a "virtual bridge" to the main or first real network adapter in your host computer that is connected to the router that is upstream towards your wired or wireless Internet connection. 103

104 Prior to installing "Hyper-V", your Windows.. computer looks like this with everything below the top-most row inside your Windows.. computer: 104

105 Internet existing Broadband Modem existing Router WAN side LAN side Real Ethernet or Wi-Fi Adapter in Host Computer Real Host Computer Running Windows..

106 When you install Hyper-V, it will create a "Virtual Bridge" and virtual "Default Switch" that has "Network Address Translation" (NAT) and "Dynamic Host Configuration Protocol" (DHCP): 106

107 This "Virtual Bridge" and virtual "Default Switch" has a "vethernet" virtual network card that resides in the "Network Connections" in the "Control Panel" of the host computer. However this "vethernet" does NOT connect the host computer to anything. 107

108 Internet existing Broadband Modem existing Router WAN side LAN side Real Ethernet or Wi-Fi Adapter in Host Computer Real Host Computer Running Windows.. Virtual Bridge vethernet Virtual "Default Switch" with DHCP & NAT

109

110

111 In Microsoft's documentation for the "Default Switch": the "Virtual Bridge" is not mentioned. The "vethernet" that belongs to the "Default Switch" (and shows up in the "Control Panel of the host computer) is mentioned. All three virtual network devices can be considered to be part of the "Default Switch": 111

112 Internet existing Broadband Modem existing Router WAN side LAN side Real Ethernet or Wi-Fi Adapter in Host Computer Real Host Computer Running Windows.. "Default Switch" Virtual Bridge vethernet Virtual "Default Switch" with DHCP & NAT

113 The "Virtual Bridge" part of the "Default Switch" will automatically connect to any real wired or wireless network adapter that is part of or connected to the host computer that has access to the Internet. 113

114 After you create the first virtual machine inside the"hyper-v Manager" window, your local network will look like this: 114

115 Internet existing Broadband Modem existing Router WAN side LAN side Real Ethernet or Wi-Fi Adapter in Host Computer Real Host Computer Running Windows.. Virtual vnic Machine with Guest O/S Virtual Bridge vethernet Virtual "Default Switch" with DHCP & NAT

116 If you change your real wired or wireless network adapter in the host computer to a new one, the "Virtual Bridge" part of the "Default Switch" will initially fail to connect to the Internet. After you re-boot the host computer, the "Default Bridge" will automatically re-attach itself to the new wired or wireless network adapter and the virtual machine(s) that it is connected to will then have Internet access again. 116

117 If you add an additional wired or wireless network adapter to your host computer, the "Default Switch" will also initially fail to connect to the Internet, even if you did not remove or modify the wired or wireless network adapter that the "Virtual Bridge" of the "Default Bridge" was originally connected to. After you re-boot the host computer, the "Virtual Bridge" of the "Default Switch" will reconnect itself to a Internet-connected wired or wired network adapter and the virtual machines that are connect to the "Default 117 Switch" to will have Internet access again.

118 The host computer and any and and all virtual machines that are connected to the "Default Switch" can share files bi-directionally with each other. 118

119 However, all of the virtual machines that are connected to the "Default Switch" cannot share files with any computers that are connected to the LAN side of the real router. 119

120 To share files between the virtual machines and other computers that are connected to the LAN side of the real router, you have to create one or more "External network switches" from inside the "Virtual Switch Manager" of the "Hyper-V Manager" 120

121 Unlike the "Default Switch", any external virtual "Network Switch" that you create in the "Virtual Switch Manager" has to be connected to a specific real wired or wireless network adapter (that resides in the host computer). 121

122 An external virtual "Network Switch" can connect to the same real network adapter that the "Default Switch" is already automatically connected to. 122

123 If you remove and change out the real wired or wireless network adapter that a virtual external "Network Switch" is connected to, the external "Network Switch" will fail to connect upstream towards the Internet until you re-configure the external "Network Switch" from inside the "Virtual Switch Manager" and reboot the host computer. 123

124 The following diagram shows how a host computer and virtual machines connect via virtual vnic network cards to an external "Network Switch": (This diagram does not show the "Default Switch".) 124

125 125

126 Reference for the previous graphic: 126

127 For each virtual machine running in "Hyper-V", you can only access the virtual machine's "vnic" virtual network card from inside the virtual machine by going to "Network Connection" or "Device Manager" 127

128 For your real, physical host computer, you can also access the virtual machine's "vnic" virtual network card(s) from inside the virtual machine by going to "Network Connections" or "Device Manager" 128

129 When you initially install "Hyper-V" into a host computer, you get a "vethernet" card in "Network Connections" that belongs to the "Default Switch". When you use the "Virtual Switch Manager" to create an external "Virtual Switch", you will get a new vnic card in "Network Connections" in "Network Connections". 129

130 Each and every external virtual switch that you create in the "Virtual Switch Manager" will put an additional vnic network card into "Network Connections" in the host computer. 130

131 Reference for the previous graphic: 131

132 USING A VIRTUAL MACHINE RUNNING IN "HYPER-V" IN WINDOWS 8.x OR 10: 132

133 Step 1: START THE "HYPER-V MANAGER" Step 2: USE THE LEFT MOUSE BUTTON TO DOUBLE-CLICK ON THE VIRTUAL MACHINE THAT YOU WANT TO RUN 133

134 Step 3: A VIRTUAL MACHINE WINDOW WILL BE DISPLAYED. THIS WILL BE THE VIRTUAL DESKTOP (= VIRTUAL MONITOR) OF THE VIRTUAL MACHINE Step 4: CLICK ON A "START" BUTTON 134

135 Step 5: IF A "CONNECT TO.." DIALOG BOX IS DISPLAYED DO NOT CANCEL IT SINCE DOING SO WILL INACTIVE THE VIRTUAL MACHINE'S VIRTUAL SOUND CARD: SELECT THE DESIRED SIZE FOR THE "VIRTUAL DESKTOP" WINDOW 135

136 Step 6: (IF A "CONNECT TO.." DIALOG BOX IS DISPLAYED:) CLICK ON "SHOW OPTIONS", CLICK ON THE "LOCAL RESOURCES" TAB, CLICK ON SETTINGS. DECIDE WHETHER YOU WANT THE HOST COMPUTER TO PROVIDE PLAYBACK AND RECORD (=MICROPHONE) 136 AUDIO

137 Step 7: (IF A "CONNECT TO.." DIALOG BOX IS DISPLAYED:) CLICK ON "SHOW OPTIONS", CLICK ON THE "LOCAL RESOURCES" TAB, CLICK ON SETTINGS. DECIDE WHETHER YOU WANT THE HOST COMPUTER TO PROVIDE PLAYBACK AND RECORD (=MICROPHONE) 137 AUDIO

138 Step 8: (IF A "CONNECT TO.." DIALOG BOX IS DISPLAYED:) IN THE "LOCAL DEVICES AND RESOURCES" SECTION, DECIDE IF THE VIRTUAL MACHINE SHOULD BE CONNECTED TO THE PRINTERS THAT THE HOST COMPUTER IS CONNECTED TO 138

139 Step 9: (IF A "CONNECT TO.." DIALOG BOX IS DISPLAYED:) IN THE "LOCAL DEVICES AND RESOURCES" SECTION, DECIDE IF THE VIRTUAL MACHINE USE THE "CLIPBOARD" OF THE HOST COMPUTER. 139

140 Step 10: (IF A "CONNECT TO.." DIALOG BOX IS DISPLAYED:) CLICK ON THE "MORE.." BUTTON 140

141 Step 11: (IF A "CONNECT TO.." DIALOG BOX IS DISPLAYED:) CLICK ON THE "+" TO THE LEFT OF "DRIVES" AND SELECT THE "DRIVES" THAT YOU WISH TO CONNECT TO THE VIRTUAL MACHINE 141

142 Step 12: (IF A "CONNECT TO.." DIALOG BOX IS DISPLAYED:) CLICK ON THE "OK" BUTTON 142

143 Step 13: CLICK ON THE "CONNECT" BUTTON 143

144 If a window belongs to a virtual machine, it will stay inside the "desktop window" of the virtual machine when you attempt to move it out of the virtual machine. 144

145 Which windows belong to the virtual machine and what windows belong to your physical host computer? 145

146 If a window belongs to a virtual machine, it will stay inside the "desktop window" of the virtual machine when you attempt to move it out of the virtual machine. 146

147 If a window belongs to the host operating system, it will let you move it out of and act like it is on top of the virtual machine. 147

148 What should you do if the pointer of your mouse gets stuck inside a Hyper-V virtual machine? 148

149 If your mouse cursor gets stuck inside the "desktop window" of a virtual machine, you can free it by using the keyboard and pressing Ctrl + Alt + Left arrow 149

150 150

151 If your mouse cursor is not inside the window of the virtual machine, you keyboard keystrokes will not be directed to the virtual machine: A virtual machine's window will be much easier to see when it is set to "full screen": To set a virtual machine windows to "full screen", click on "View", then click on "Full Screen.." 151

152 How do you move and copy files and folders between the real hard drives of the host computer and the virtual hard drives of a virtual machine? 152

153 Two ways to copy or move files between the host computer and a virtual machine: Method 1: Cut or copy (Ctrl+x or Ctrl c) and paste (Ctrl+v) between the host computer and the virtual machine if the virtual machine has "Enhanced session" enabled 153

154 (Two ways to copy or move files between the host computer and a virtual machine:) Method 2: File sharing with conventional SMB or homegroups networking (SMB = server message block) 154

155 GETTING AUDIO TO WORK IN A VIRTUAL MACHINE IN "HYPER- V" IS MUCH HARDER THAN IN COMPETITIVE "VIRTUAL MACHINE PROGRAMS" 155

156 "Hyper-V" provides you with a virtual machine with a virtual sound card that only works with the some but not all editions of "Windows Vista", "Windows 7", "Windows 8.1", or "Windows 10" but you have to "jump through hoops" to make the virtual sound card work: 156

157 In contrast, "VirtualBox" and "VMware Workstation Player" provide all virtual machines with 2 models of virtual sound cards. 157

158 For "Hyper-V" virtual machines running older versions of "Windows.." prior to "Windows 7" or the "..Home" versions of Windows 8.1 and 10 or "Windows 10 S", there is no virtual audio capability 158

159 In contrast, VirtualBox and VMware Workstation Player provides a virtual sound card that sends speaker audio and microphone audio from the virtual machine to the host's sound card 159

160 In VirtualBox and VMware Workstation Player, you can buy and install a separate real USB sound card into any virtual machine but you cannot do so for a virtual machine in Hyper-V since virtual machines in Hyper-V do not have virtual USB ports 160

161 You cannot activate "Enhanced session" or the virtual hardware features inside the "Settings.." screen of a virtual machine 161

162 During the startup of a virtual machine running the following editions of "Windows.." or from the "View" pull-down menu of the top menu bar of a virtual machine, you can turn on "Enhanced session mode", which will provide a virtual "Remote audio" sound card for the following guest operating systems: 162

163 163

164 Guest Operating Systems capable of running in "Enhanced session" mode: "Windows 8.1 Pro" (in a Generation 2 virtual machine), "Windows 8.1 Enterprise" (in a Generation 2 virtual machine) "Windows 10 Pro" (in a Generation 1 or 2 virtual machine) "Windows 10 Enterprise" (in a Generation 1 or 2 virtual machine), or "Windows 10 Education" (in a Generation 1 or 2 virtual machine) 164

165 When you turn on "Enhanced session", the virtual machine will force you to log into "Windows.." every time that you boot up the virtual machine, even if you have configured "Windows.." to log in without asked you for a username and password by running "netplwiz" or "control userpasswords2" 165

166 (For most Windows Vista, 7, 8, and 10 computers, you can run "netplwiz" to make Windows log you in automatically without challenging you for a Windows user account password by following the instructions at 19/how-to-make-your-windows-8- computer-logon-automatically/) 166

167 (For most Windows 2000, Vista, 7, 8, and 10 computers, you can run "control userpasswords2" to make Windows log you in automatically without challenging you for a Windows user account password by following the instructions at Q/loginbypass/loginbypass.php) 167

168 When you are running in "Enhanced session" mode, you cannot change the screen resolution of the display window of the virtual machine: To change the screen resolution: get out of "Enhanced session" from the "View" pull-down menu, change the screen resolution, then get back into "Enhanced Session" mode. 168

169 Whenever you go out of "Enhanced Session" mode, the virtual machine will make you log into your Windows "user account". Whenever you go back into "Enhanced session" mode, the virtual machine will make you log into your Windows "user account" 169

170 You can get into "Enhanced session" for both Generation 1 or Generation 2 virtual machines 170

171 For Hyper-V virtual machines running some versions of "Windows..", you can provide a "pass through" sound card by making a "Remote Desktop Connection" from the host computer to the virtual machine if the virtual machine is running one of the following guest operating systems: 171

172 "Windows Vista Business", "Windows Vista Enterprise", "Windows Vista Ultimate", "Windows 7 Professional", "Windows 7 Enterprise", "Windows 7 Ultimate", "Windows 8.1 Pro", "Windows 8.1 Enterprise", "Windows 10 Pro", "Windows 10 Education" or "Windows 10 Enterprise" 172

173 For Hyper-V virtual machines running the following versions of "Windows..", the use of a "pass through" sound card by making a "Remote Desktop Connection" from the host computer to the virtual machine is the only way to provide a virtual sound card since these operating systems are not capable of "Enhanced session": 173

174 "Windows Vista Business", "Windows Vista Enterprise", "Windows Vista Ultimate", "Windows 7 Professional", "Windows 7 Enterprise", "Windows 7 Ultimate", 174

175 In other words, for the following guest operating systems running inside Hyper-V virtual machines: "Windows 8.1 Pro", "Windows 8.1 Enterprise", "Windows 10 Pro", "Windows 10 Education" or "Windows 10 Enterprise", you can provide a virtual "Remote audio" sound card by either accessing the virtual machine via "Remote Access" or by turning on "Enhanced mode" 175

176 If you go to "Settings" for a virtual machine and you install the virtual "RemoteFX 3D Video Adapter", then "Enhanced Session" will not work for the virtual machine, regardless of the information in the previous listings. 176

177 In other words, for the following guest operating systems, if you provide the virtual machine with a virtual "RemoteFX 3D Video Adapter", then "Enhanced Session" will not work and you have to use "Remote Desktop" connection to provide the virtual machine with a "Remote Audio" sound card: "Windows 8.1 Pro", "Windows 8.1 Enterprise", "Windows 10 Pro", "Windows 10 Education" "Windows 10 Enterprise", 177

178 Most gamers who use virtual machines inside "Hyper-V" recommend that you use a high-end graphics adapter so that it is "passed on" from the host computer to a virtual machine since the virtual "RemoteFX 3D Video Adapter" is not available when the sound capabilities of "Enhanced session" is enabled. 178

179 "Hyper-V" has zero sound support for Linux operating systems: This makes "Hyper-V" unusable for running Linux operating systems for most of us. In contrast "VirtualBox" and "VMware Workstation Player" have great sound capability for Linux operating systems. 179

180 Microsoft's documentation on "Enhanced Session" in Hyper-V is located at machine-with-vmconnect 180

181 If a virtual machine is capable of running in "Enhanced Session" mode a "Connect to.." dialog box is supposed to be displayed whenever you first turn on a virtual machine that has been in the "Off" state. The "Connect to.." dialog box is not displayed if and when you or the operating system reboots the virtual machine. 181

182 182

183 The "Connect to.." dialog box is not displayed if the virtual machine in incapable of running in "Enhanced session" mode. 183

184 The "Connect to" box lets you set the screen resolution of the virtual machine. Once the computer boots up in "Enhanced session" mode, you will be unable to set the screen resolution of the virtual machine from within the guest operating system (unless you temporarily exit out of "Enhanced session" mode. 184

185 185

186 The "Connect to.." box is the only place o o where you can configure and attach to the virtual machine the following: The sound card of the host computer can be attached as "Remote audio" Playback and/or Record (mic) virtual devices. Any real internal hard drives, external hard drives, SSDs, SD cards, and flash drives that are currently connected to the host computer. 186

187 187

188 The "Use all my monitors" checkbox only accepts a checkmark if you have more than one monitor attached to the host computer and these monitors are not set to "Extend" instead of "Duplicate". If you then place a checkmark for "Use all my monitors", the virtual machine starts up in "Full Screen" mode in all of your monitors. 188

189 189

190 The "Show Options" pull-down button of the "Connect to.." box exposes a "Save my settings for future connections to this virtual machine" check box: Do not put a checkmark in this check box. 190

191 191

192 192

193 193

194 Repeat: Do not put a checkmark in this check box. Putting a checkmark in this check box will prevent the "Connect to.." box from displaying during future boot-ups of the virtual machine, making it impossible for you to reconfigure, remove, or add on the "local resources" that "Enhanced session" is capable of connecting to a virtual machine. 194

195 If you do get a "Connect to.." dialog box to configure "Enhanced session" when you are starting up a virtual machine (that is running a version of Windows.. is capable of "Enhanced session"), the fix is located at ums/en-us/dad8fd6a c57-b0c9-9d98ec81ace2/how-to-change-hyperv- 2012r2-enhanced-session-modeoptions?forum=virtualserver 195

196 Additional information on resolving this annoyance can be found at om/forums/windows/en- US/3bf785d3-1fa3-457a-b8b6- b4a14d8c64b6/where-areconnections-to-hyperv-vm- saved?forum=winserverhyperv 196

197 Not using the "Save my settings for future connections to this virtual machine" check box because it causes problems means that you have to re-attach the virtual sound card's microphone audio capability and reattach any real internal hard drives, external hard drives, SSDs, SD cards, and flash drives, each and every time that you start up a virtual machine from the "Off" state. 197

198 The "Show Options" pull-down button of the "Connect to.." box also exposes a "Local Resources" tab for the "Connect to.." dialog box. Click on the "Local Resources" tab to configure the virtual hardware devices that are offered by "Enhanced session" mode: 198

199 Click on "Settings" in the "Remote Audio" section to turn on or off the following: To provide a "pass through" virtual sound card to the virtual machine: Select "Play on this computer" to provide playback "Remote Audio" for the virtual machine. Select "Record from this computer" to provide "record" (= microphone) "Remote Audio" for the virtual machine. 199

200 200

201 201

202 202

203 203

204 204

205 205

206 In the "Local devices and printers" section of the "Local Resources" tab, put a checkmark for "Printers" if you want to the virtual machine to be able to print to the host computer's printers. Doing so does not disconnect the printers from the host computer so that you will still be able to continue to print from documents and photos that you open in the host computer. 206

207 In the "Local devices and printers" section of the "Local Resources" tab, put a checkmark for "Clipboard" if you want to be able to cut, copy, and paste bi-directionally between the virtual machine and the host computer 207

208 208

209 In the "Local devices and printers" section of the "Local Resources" tab, click on the "More..", to select real internal hard drives, external hard drives, SSDs, SD cards, and flash drives that you wish to access from inside the guest operating system of the virtual machine. 209

210 210

211 211

212 If you provide the virtual machine with access to a real internal hard drive, an external hard drive, a SSD, a SD card, or a flash drive, you can still access the same device from within File Explorer and browse windows in the host computer. In other words, you are sharing these host devices with the virtual machine without disconnecting them from the host computer. 212

213 213

214 For running "Windows 2000" and earlier versions of "Windows.." inside a virtual machin, use "Virtualbox" or "VMware Workstation Player instead of Hyper-V since Hyper-V will usually fail to allow these older operating systems to install into a virtual machine. 214

215 IF THE "DEFAULT SWITCH" AND/OR OTHER "VIRTUAL (NETWORK) SWITCHES" FAIL TO CONNECT TO THE INTERNET: 215

216 If the "Default Switch" or other "virtual (network) switches" fail to let all of your virtual machines connect to the Internet: Go to "Programs and Features" in the "Control Panel". Go to "Turn Windows features on or off ". Remove the black-colored fill for the checkbox for "Hyper-V". 216

217 (If the "Default Switch" or other "virtual (network) switches" fail to let all of your virtual machines connect to the Internet:) Click on OK. Reboot the computer. Go to "Programs and Features" in the "Control Panel". Go to "Turn Windows features on or off ". 217

218 (If the "Default Switch" or other "virtual (network) switches" fail to let all of your virtual machines connect to the Internet:) Put in a checkmark for "Hyper-V". Click on "OK". Reboot the computer. The failed virtual network switches will probably start working again. (You will not lose or delete any existing virtual machines.) 218

219 RE-BOOTING A VIRTUAL MACHINE'S GUEST OPERATING SYSTEM TAKES THE VIRTUAL MACHINE OUT OF "ENHANCED SESSION MODE": 219

220 For some unknown reason, if you reboot a virtual machine that is running in "Enhanced Session" mode, it will start up without "Enhanced Session" mode. When this happens, you can put the virtual machine back into "Enhanced Session" mode by clicking on "View" in the top menu bar of the virtual machine and then clicking on "Enhanced Session" in the pull-down menu. 220

221 BACKING UP A VIRTUAL MACHINE: 221

222 You can make a reliable "export" of a virtual machine from inside the "Hyper-V Manager The exported files and folders should be stored in an offline, external hard drive 222

223 If at a later point in time, the virtual machine fails, you delete the virtual machine Then you can import the "export" in order to restore the virtual machine back to the way that it was on the date on which you did the export 223

224 Then you can import the "export" in order to restore the virtual machine back to the way that it was on the date on which you did the export After importing the virtual machine, you can run the virtual machine and run the guest operating systems procedure for updating the virtual machine 224

225 MOVING A VIRTUAL MACHINE: 225

226 Method 1: Export the virtual machine to an external hard drive. Then import the exported files into the new computer or the different hard drive. This method preserves the UUID of the virtual motherboard so it works for "Windows 22610".

227 Method 2: Disconnect but do not delete all of the virtual machine's virtual hard drives. Export the virtual machine to an external hard drive. Import the virtual machine a it's new computer or to a different hard drive on the same computer. 227

228 (Method 2 (continued):) Use File Explorer to copy or move the virtual hard drive(s) to a new location. Inside "Settings" for the virtual machine, re-connect the virtual hard drive(s) to the virtual machine. Run the virtual machine to make sure that it is working right. 228

229 Method 2 (continued) Inside "Settings" for the virtual, attach the copy the virtual hard drive(s) to the new virtual machine. Method 2 also preserves the UUID of the virtual motherboard so it works for Windows

230 Method 3: Create a new virtual machine with the same name and attributes at the new computer or the different hard drive. Do not attach installation media.iso file or DVD/CD to the new virtual machine. Copy the virtual hard drive(s) to the new location. 230

231 Method 3 (continued): This method does not preserve the UUID of the virtual motherboard so you have to use Microsoft's mechanism for changing motherboards inside "Activation" inside "Settings" if you are moving a "Windows 10" virtual machine. 231

232 Method 3 (continued): When you use "Method 3" with a "Windows.." operating system, you sometimes have to do a "Startup Repair" by booting up the virtual machine with a installation media.iso file or DVD disc. 232

233 Method 3 (continued): If you make a "burn" a DVD from Windows 10 Fall Creators Update installation.iso files, you will need "double layer DVD-R or RW discs. The version 1709 "Fall Creators Update".ISO files are all too large to burn onto the cheaper "single layer" DVD-R or RW discs. 233

234 Method 4: If you wish to move the virtual machine to a hard drive or partition or folder on the current host computer, you can use the "Move" function inside the "Hyper-V Manager" 234

235 IMPORT AND EXPORT OF HYPER-V VIRTUAL MACHINES: 235

236 When you export a virtual machine, you create a folder that has configuration files that define the virtual motherboard and other virtual devices that are part of the virtual machine 236

237 This exported folder is your back up of the virtual machine at a specific point in time You can back up a.vhd or.vhdx virtual hard drive file separately by using "File Explorer"/"Windows Explorer" to copy it to an external hard drive 237

238 The other files of your virtual machine cannot be copied by means of "File Explorer"/"Windows Explorer" because doing so will result in useless files. The export process is the only want to back up these other files. 238

239 If you have a lot of data in your.vhd or.vhdx virtual machine files, you should disconnect all or most of the.vhd or.vhdx file and export all of the other files from inside the "Hyper-V Manager" window 239

240 If you disconnect all or most of the.vhd or.vhdx file and export just all of the other files, then you later import the virtual machine into the same or different computer, you will then have to locate and re-attach the.vhd or.vhdx files in the "Settings" screen after the import process. 240

241 If you get an exported virtual machine from Microsoft, it will be given to you as a.zip file To use the.zip file, create a new folder, usually with the same name as the name of the.zip file but without the.zip extension. Then unzip the contents of the.zip file into the new folder. 241

242 You can get time-limited virtual machines that have been created by Microsoft as importable file sets at en-us/microsoft-edge/tools/vms/ 242