WEBVTT 00:00:00.000 --> 00:00:04.000 Welcome back to vSphere 8 in the real world. Let's discuss deploying a VM. 00:00:04.000 --> 00:00:12.000 So there's different ways you can deploy VMs. The first thing you can do is just create a VM from scratch. 00:00:12.000 --> 00:00:18.000 You can right-click and say new VM and just define everything about that VM you want to be. 00:00:18.000 --> 00:00:25.000 You can tell them how many CPUs and how much RAM and what operating system you want to use and what port group you want the VM to be on. 00:00:25.000 --> 00:00:30.000 All of those settings you can do. That's completely from scratch going through this wizard. 00:00:30.000 --> 00:00:39.000 It's not a huge pain, but it does take time. If I needed to do 100 VMs that way, it would take you quite a while to do that. 00:00:39.000 --> 00:00:47.000 You can also deploy from a template, which means I've already gone in and I went to the first part of creating the virtual machine. 00:00:48.000 --> 00:00:55.000 Right-click, new VM, and I chose all the different options and all the customizations I wanted to do. 00:00:55.000 --> 00:01:01.000 I don't need a USB controller, so I removed that. I changed the number of virtual CPUs I want. 00:01:01.000 --> 00:01:06.000 I added a second hard drive if that's what I need to do. All the different things, all the customizations I want. 00:01:06.000 --> 00:01:14.000 Then I completed that deployment. I logged into it. I installed an operating system, so I installed Windows. 00:01:14.000 --> 00:01:19.000 I got all the Windows updates up to date. I installed my applications on there. I did all that stuff. 00:01:19.000 --> 00:01:24.000 This whole thing took me, with the updates and everything, took me two and a half hours to get all this done. 00:01:24.000 --> 00:01:32.000 Now I need another one. I can go through and do all those same steps again, and it can take me another two and a half hours. 00:01:32.000 --> 00:01:36.000 I have to do this for 10 virtual machines, so it takes me three days to deploy these. 00:01:36.000 --> 00:01:44.000 Or the thing I could do is, that first one that took me two and a half hours, I can save it by converting it to a template. 00:01:44.000 --> 00:01:52.000 After I convert it to a template, I can just right-click on that template, and I can say I want to deploy a VM from that template. 00:01:52.000 --> 00:01:56.000 It'll ask me a couple of questions, like what name do I want to name it. 00:01:56.000 --> 00:02:03.000 I can say if I need to do any customizations. I can have a customization file already ready for it, and I can just deploy from that. 00:02:03.000 --> 00:02:09.000 That would take me maybe a minute or a few seconds, and I can right-click and do it again and do it again. 00:02:09.000 --> 00:02:15.000 When all those are done, they all have their operating systems configured. They already have their applications deployed. 00:02:15.000 --> 00:02:18.000 I didn't have to go through and customize all the hardware. 00:02:18.000 --> 00:02:23.000 I didn't have to add more virtual CPUs or remove the USB controller or do any of those things. 00:02:23.000 --> 00:02:25.000 All that stuff was done because it was already in the template. 00:02:26.000 --> 00:02:33.000 A template is a preconfigured virtual machine that has an operating system and maybe applications and all ready to go, 00:02:33.000 --> 00:02:37.000 so you can deploy a VM in minutes versus hours. 00:02:37.000 --> 00:02:44.000 Every once in a while, you might want to convert your template back to a VM, power it on, patch it, power it off, 00:02:44.000 --> 00:02:50.000 and convert it back to a template, so when you deploy your next set of VMs from there, they're patched and current and ready to go. 00:02:50.000 --> 00:02:52.000 You might want to maintain those templates. It's something to consider. 00:02:55.000 --> 00:02:58.000 You can actually also deploy a VM from a VM. 00:02:58.000 --> 00:03:05.000 It doesn't have to be a template because all a template is is a virtual machine with its VMX file out of a slightly different extension, 00:03:05.000 --> 00:03:07.000 VMTX instead of VMX. 00:03:07.000 --> 00:03:13.000 I can actually have a virtual machine, and it can actually be running, and I can clone a VM from it. 00:03:13.000 --> 00:03:17.000 When I'm done, it will be a completely new virtual machine. 00:03:17.000 --> 00:03:19.000 It will have a different MAC address. 00:03:19.000 --> 00:03:23.000 If you went through your customization with it, you have a different GUID and everything, 00:03:23.000 --> 00:03:28.000 brand-new VM that will boot up and be ready to go with all the same applications, 00:03:28.000 --> 00:03:36.000 all the same files that were on the hard drive, patching up to the moment of the source VMs patching, all of that. 00:03:36.000 --> 00:03:40.000 You can also clone, as we mentioned before, clone a template. 00:03:41.000 --> 00:03:46.000 When they talk about a golden image, a golden image can be your template, 00:03:46.000 --> 00:03:52.000 or a golden image could be a virtual machine that Horizon uses as that master. 00:03:52.000 --> 00:03:56.000 So a golden image can be referred to from different meanings. 00:03:56.000 --> 00:04:02.000 If you're talking about templates specifically, though, then it's going to be that machine that has the VMTX file. 00:04:02.000 --> 00:04:06.000 So templates are a golden VM, as we said. 00:04:06.000 --> 00:04:09.000 A golden image is kind of a term that's kind of used in a lot of different ways, 00:04:09.000 --> 00:04:16.000 but a template is that golden image VM, meaning it's the standard that has all the configuration. 00:04:16.000 --> 00:04:18.000 It has all the applications. 00:04:18.000 --> 00:04:21.000 We may have done some patching on it already. 00:04:21.000 --> 00:04:24.000 Hopefully, we've maintained that patching on that VM. 00:04:24.000 --> 00:04:27.000 So when we deploy new ones, they're all set, ready to go. 00:04:28.000 --> 00:04:32.000 Everything that was in that template, the operating system, the applications, 00:04:32.000 --> 00:04:38.000 if I put shortcuts into a folder someplace, if I put files on the hard drive someplace, 00:04:38.000 --> 00:04:40.000 all that same stuff is there. 00:04:40.000 --> 00:04:45.000 If a user's logged into it on the template, that same user account will be logged into that one as well. 00:04:45.000 --> 00:04:46.000 All right. 00:04:46.000 --> 00:04:49.000 So all the settings come with that template. 00:04:49.000 --> 00:04:53.000 So vSphere 8 configuration limits for a virtual machine. 00:04:53.000 --> 00:04:58.000 So vSphere 8 configuration limits for a virtual machine. 00:04:58.000 --> 00:05:02.000 Virtual machine CPUs per VM, 768. 00:05:02.000 --> 00:05:04.000 Hopefully, you'll need a lot more than that. 00:05:04.000 --> 00:05:06.000 RAM, 24 terabytes. 00:05:06.000 --> 00:05:08.000 SCSI adapters, up to 4. 00:05:08.000 --> 00:05:12.000 Max virtual disk size, 62 terabytes. 00:05:12.000 --> 00:05:15.000 Max virtual NICs per VM, 10. 00:05:15.000 --> 00:05:21.000 It's been limited to 10 since 3.5 and probably even before 3.5. 00:05:21.000 --> 00:05:24.000 10 NICs per VM is the max. 00:05:24.000 --> 00:05:29.000 In a virtual machine, you don't really often need that many, you know, network adapters on a VM. 00:05:29.000 --> 00:05:34.000 But there are some times when you wish you could get more and sometimes a lot more. 00:05:34.000 --> 00:05:36.000 Hyper-V can let you get a lot more. 00:05:36.000 --> 00:05:39.000 So it's odd to me that VMware has always stuck with 10. 00:05:39.000 --> 00:05:43.000 But virtual NICs per VM, 10. 00:05:43.000 --> 00:05:45.000 Persistent memory per VM, 6 terabytes. 00:05:45.000 --> 00:05:49.000 So persistent memory, as we mentioned in a previous lesson, 00:05:49.000 --> 00:05:56.000 persistent memory is kind of like a hard disk that the system can treat as memory. 00:05:56.000 --> 00:06:02.000 But it can actually be set up with an operating system and applications and everything on this persistent memory. 00:06:02.000 --> 00:06:08.000 So when you power on the VM, all this information, like the operating system applications and things like that, are already there. 00:06:08.000 --> 00:06:17.000 So in environments where you need very fast boot times and very fast performance from a virtual machine, 00:06:17.000 --> 00:06:24.000 where you want to be even faster than, say, reading from, you know, a hard disk, you can use persistent memory. 00:06:24.000 --> 00:06:26.000 So it's a special kind. 00:06:26.000 --> 00:06:32.000 It goes into a slot like a NVMe drive or a flash drive, but it's a different kind of disk. 00:06:32.000 --> 00:06:38.000 It's, again, it's called persistent memory, and it will let you boot up systems much faster than, like, 00:06:38.000 --> 00:06:43.000 loading Windows from a hard drive would. 00:06:43.000 --> 00:06:48.000 So if you want to create and deploy VMs, you can use the VM wizard, right? 00:06:48.000 --> 00:06:53.000 All you're going to do is right-click on your, you know, either your cluster or on a host, you know, 00:06:53.000 --> 00:07:00.000 somewhere in your vCenter there, and say you want to create a new virtual machine, right? 00:07:01.000 --> 00:07:03.000 You can choose where you want to place it. 00:07:03.000 --> 00:07:08.000 If you want to put it into a cluster, if you want to put it into a resource pool, if you want it to land on a specific host, 00:07:08.000 --> 00:07:10.000 you can choose all those options, right? 00:07:10.000 --> 00:07:14.000 You can also choose your activity dropdown menu and say new virtual machine from there. 00:07:14.000 --> 00:07:17.000 Basically, right-clicking in the activity menu are kind of the same, 00:07:17.000 --> 00:07:23.000 just different ways of getting to that same menu option. 00:07:23.000 --> 00:07:30.000 So creating and deploying VMs, when you want to create a new VM, you have some things you need to consider. 00:07:30.000 --> 00:07:32.000 Do you want to deploy from a premade template? 00:07:32.000 --> 00:07:34.000 Do you want to clone from a VM? 00:07:34.000 --> 00:07:37.000 So you can actually do that. 00:07:37.000 --> 00:07:42.000 You can clone from a template to a template, and you can convert a template to a virtual machine. 00:07:42.000 --> 00:07:46.000 So if you have a VM, or I'm sorry, a template you want to patch and update, 00:07:46.000 --> 00:07:53.000 you can convert it back to a virtual machine and then patch and update it and then convert it back to a template. 00:07:53.000 --> 00:07:55.000 You can't start a template. 00:07:55.000 --> 00:07:57.000 You can't power on a template. 00:07:57.000 --> 00:08:00.000 That's why you need to convert it back to a VM. 00:08:00.000 --> 00:08:04.000 So when you go to deploy it, first you need to determine where you want to place it. 00:08:04.000 --> 00:08:06.000 Then you have to give it a name. 00:08:06.000 --> 00:08:08.000 So, you know, what are you going to call it? 00:08:08.000 --> 00:08:11.000 And then you have to determine where you want to place it. 00:08:11.000 --> 00:08:17.000 So from there you can say, I just want to place it into this cluster, for example. 00:08:17.000 --> 00:08:21.000 And once you start going through that wizard, it'll say, okay, what cluster, from what cluster, 00:08:21.000 --> 00:08:24.000 what host in the cluster do you want to put it into, right? 00:08:24.000 --> 00:08:31.000 So there I chose a cluster, and now it's asking me what host on there, what compute resource do I want to use. 00:08:31.000 --> 00:08:37.000 So for storage, you can choose what type of storage you're going to use. 00:08:37.000 --> 00:08:40.000 That's going to be dependent upon the storage the VM is going to need, right? 00:08:40.000 --> 00:08:48.000 If your VM is going to be running a SQL database, then you might need some really fast storage for that SQL database. 00:08:48.000 --> 00:08:57.000 You might create a virtual disk for that and put that virtual disk on a different data store than where you put the C drive disk 00:08:57.000 --> 00:08:59.000 or where the disk is running your operating system. 00:08:59.000 --> 00:09:07.000 Now, some of the things to consider is what you're choosing here in this wizard at first is what's the home folder for that virtual machine. 00:09:07.000 --> 00:09:10.000 So this is where you're going to be putting the VMX file. 00:09:10.000 --> 00:09:12.000 This is where your swap's going to go. 00:09:12.000 --> 00:09:16.000 This is where all those files that define what the VM is are going to go. 00:09:16.000 --> 00:09:19.000 And by default, the VMDKs go there, too. 00:09:19.000 --> 00:09:22.000 But you can choose to put these VMDKs someplace else. 00:09:22.000 --> 00:09:27.000 If you decide to storage vMotion in the VM, what you're changing is this home folder, right? 00:09:27.000 --> 00:09:31.000 So you're changing where, like, the VMX file and all those things are going. 00:09:31.000 --> 00:09:40.000 You can choose to put the VMDK files, again, during storage vMotion someplace else, right? 00:09:40.000 --> 00:09:45.000 So here we're choosing a data store for that home folder. 00:09:45.000 --> 00:09:51.000 So compatibility, what version of ESXi do you want to make this compatible with? 00:09:51.000 --> 00:09:54.000 Now, maybe we're running 8 on the host that you selected. 00:09:54.000 --> 00:09:59.000 And if you were to say, okay, I want to make it compatible with 8, I'm running 8, let's make it compatible with 8, 00:09:59.000 --> 00:10:02.000 then it can't run on anything older than 8. 00:10:02.000 --> 00:10:08.000 But if I know in my environment I have some 7 update 3 and I have some 8, 00:10:08.000 --> 00:10:10.000 so I haven't upgraded all the hosts to 8 yet, 00:10:10.000 --> 00:10:15.000 or I haven't replaced all the old 7 update 3 hosts with new 8 hosts yet. 00:10:15.000 --> 00:10:17.000 So I have both running in my environment, 00:10:17.000 --> 00:10:23.000 and I might need to move this VM from the 8 that I selected to the 7 update 3. 00:10:23.000 --> 00:10:25.000 Then here I can't choose 8. 00:10:25.000 --> 00:10:28.000 I need to choose 7 update 3 at the newest. 00:10:28.000 --> 00:10:31.000 So choose what version of ESXi you want to make it compatible with. 00:10:31.000 --> 00:10:35.000 If you know all your hosts are the latest, greatest, newest 8. 00:10:35.000 --> 00:10:41.000 By the way, it won't show you anything here newer than what you have for the host you selected, right? 00:10:41.000 --> 00:10:48.000 So if you're running, you know, 8.0 update 1, but update 3 is out, 00:10:48.000 --> 00:10:53.000 it won't show you 8.3 here because, first of all, 8.1 won't even know about it, right? 00:10:53.000 --> 00:10:58.000 So if vCenter is not running update 3, you're not going to see update 3 as an option. 00:10:58.000 --> 00:11:03.000 So what version of ESXi do you want to choose? 00:11:03.000 --> 00:11:05.000 What guest OS do you want to use? 00:11:05.000 --> 00:11:06.000 And this is actually pretty important. 00:11:06.000 --> 00:11:10.000 You might think it's not really that big a deal, but actually it really does matter. 00:11:10.000 --> 00:11:14.000 If you choose a Linux OS and you try installing Windows, you might see a lot of errors, 00:11:14.000 --> 00:11:16.000 vice versa, okay? 00:11:16.000 --> 00:11:18.000 So if you're running Linux, it'll say, okay, what kind of Linux? 00:11:18.000 --> 00:11:19.000 I'm running Alma Linux. 00:11:19.000 --> 00:11:20.000 I'm running Red Hat. 00:11:20.000 --> 00:11:21.000 What version of Red Hat? 00:11:21.000 --> 00:11:26.000 It'll have 7 and 8 and 9 and all the different versions of Red Hat in there. 00:11:26.000 --> 00:11:30.000 If you're running, say, if I'm running Windows Server, Windows Server 2016, 00:11:30.000 --> 00:11:34.000 Windows 2012, 2024, what version of Windows Server do you want to run? 00:11:34.000 --> 00:11:37.000 So that's the options you'll need to choose there, 00:11:37.000 --> 00:11:39.000 the family and the version of the OS you're trying to run. 00:11:39.000 --> 00:11:43.000 Then customizing the hardware. 00:11:43.000 --> 00:11:46.000 From here I can choose how many virtual CPUs I want to have, 00:11:46.000 --> 00:11:49.000 how much RAM I want to have. 00:11:50.000 --> 00:11:52.000 The hard disk size. 00:11:52.000 --> 00:11:56.000 So this first disk here, this would probably be on a Windows box, my C drive, 00:11:56.000 --> 00:11:58.000 where I'm going to install my operating system. 00:11:58.000 --> 00:12:01.000 I can also say I want to add additional components. 00:12:01.000 --> 00:12:03.000 I want to add another hard drive. 00:12:03.000 --> 00:12:05.000 I want a D drive and I want to make it X size. 00:12:05.000 --> 00:12:09.000 You can choose another network adapter. 00:12:09.000 --> 00:12:12.000 For the network adapter that's already in there, I can choose, for example, 00:12:12.000 --> 00:12:14.000 the driver I want to install on it. 00:12:14.000 --> 00:12:16.000 Do I want to use a VMXnet 3? 00:12:16.000 --> 00:12:18.000 Do I want to use an E1000 driver? 00:12:18.000 --> 00:12:20.000 There's different driver options. 00:12:20.000 --> 00:12:25.000 So it will emulate or virtualize a different NIC, 00:12:25.000 --> 00:12:28.000 and so an E1000 driver inside your OS would work. 00:12:28.000 --> 00:12:32.000 If you have a VM that you're not going to be running the VMware tools on, 00:12:32.000 --> 00:12:35.000 then you probably want to choose the E1000. 00:12:35.000 --> 00:12:38.000 The E1000 is going to be the best performing virtual NIC other than the 00:12:38.000 --> 00:12:40.000 VMXnet 3. 00:12:40.000 --> 00:12:42.000 If you're going to be installing VMware tools, 00:12:42.000 --> 00:12:46.000 then you'll get the driver for the VMXnet 3 at the same time, 00:12:46.000 --> 00:12:49.000 and so that will be the best performing adapter for you. 00:12:49.000 --> 00:12:52.000 Linux systems can usually use the E1000, 00:12:52.000 --> 00:12:55.000 and you don't have to install VMware tools on most Linux systems. 00:12:55.000 --> 00:12:57.000 The host kind of already has them, 00:12:57.000 --> 00:13:02.000 or the distribution oftentimes already has the drivers in there, 00:13:02.000 --> 00:13:06.000 but you'll use the E1000 network adapter because it has an Intel E1000 00:13:06.000 --> 00:13:11.000 driver in there already. 00:13:12.000 --> 00:13:13.000 So what can be configured? 00:13:13.000 --> 00:13:18.000 CPU cores, memory, hard disk size, how many hard disks you want to use, 00:13:18.000 --> 00:13:21.000 what kind of SCSI controller you want, what network adapter, 00:13:21.000 --> 00:13:22.000 as we mentioned before. 00:13:22.000 --> 00:13:26.000 The CD-ROM drive, you can mount an ISO onto the CD-ROM drive at this time. 00:13:26.000 --> 00:13:29.000 Your video card, how much video memory do you want it to have, 00:13:29.000 --> 00:13:31.000 how many video cards do you want to have, 00:13:31.000 --> 00:13:33.000 what kind of display settings you want on there. 00:13:33.000 --> 00:13:37.000 So a lot of different things like that can be configured. 00:13:37.000 --> 00:13:39.000 So here's CPU. 00:13:39.000 --> 00:13:44.000 So what we can do on the CPU is we can set the CPU topology. 00:13:44.000 --> 00:13:47.000 What that basically is talking about is I can actually say on the CPU, 00:13:47.000 --> 00:13:52.000 I want a CPU with – I want two CPUs and two cores each. 00:13:52.000 --> 00:13:54.000 So it would kind of be like four CPUs, right? 00:13:54.000 --> 00:13:57.000 Four cores that can do processing for me. 00:13:57.000 --> 00:13:58.000 But it would look like it's two sockets. 00:13:58.000 --> 00:14:01.000 Or I can say I want one socket with four cores, all right? 00:14:01.000 --> 00:14:05.000 So if you've got software that is licensed per socket, 00:14:05.000 --> 00:14:07.000 you might want to choose per socket. 00:14:07.000 --> 00:14:10.000 If you don't, then you might want to choose multiple sockets 00:14:10.000 --> 00:14:12.000 and then cores in there. 00:14:12.000 --> 00:14:15.000 And then it will actually distribute the workload for that machine, 00:14:15.000 --> 00:14:18.000 saying, oh, this is supposed to be one socket, 00:14:18.000 --> 00:14:20.000 and put these threads on one physical socket 00:14:20.000 --> 00:14:24.000 and the other socket with two cores will go on two other sockets, 00:14:24.000 --> 00:14:26.000 two threads to the other socket. 00:14:26.000 --> 00:14:27.000 It will break them up that way. 00:14:27.000 --> 00:14:29.000 We can also set up things like reservations. 00:14:29.000 --> 00:14:34.000 We can set a minimum amount of CPU that has to always be held 00:14:34.000 --> 00:14:36.000 in reserve just for this VM. 00:14:36.000 --> 00:14:38.000 We can also put limits, 00:14:38.000 --> 00:14:41.000 saying you can't use more than a certain amount of megahertz 00:14:41.000 --> 00:14:42.000 on this processor. 00:14:42.000 --> 00:14:45.000 We can also do hardware virtualization. 00:14:45.000 --> 00:14:47.000 What we can basically do is we can go in 00:14:47.000 --> 00:14:50.000 and allow performance counters to pass through. 00:14:50.000 --> 00:14:53.000 We can also say we want the VT, virtual technology, 00:14:53.000 --> 00:14:57.000 extensions from the CPU, passed to the VM. 00:14:57.000 --> 00:14:59.000 You'd want to do something like that if we're doing 00:14:59.000 --> 00:15:03.000 virtualization nesting, meaning I'm running ESXi on my host 00:15:03.000 --> 00:15:06.000 and I want an ESXi virtual machine inside of there, 00:15:06.000 --> 00:15:09.000 that's going to then again run virtual machines. 00:15:09.000 --> 00:15:13.000 So you need the VT extensions passed through from the host 00:15:13.000 --> 00:15:18.000 to the guest OS. 00:15:18.000 --> 00:15:20.000 And here's that topology, right, 00:15:20.000 --> 00:15:22.000 where we can specify things in there, 00:15:22.000 --> 00:15:24.000 like do we want to allow hot plug in there, 00:15:24.000 --> 00:15:26.000 how many CPUs we want to have, how many cores per socket 00:15:26.000 --> 00:15:30.000 do we want to configure, things like that. 00:15:30.000 --> 00:15:32.000 So memory, I can specify how much RAM, 00:15:32.000 --> 00:15:40.000 minimum 256 megabytes for Windows, maximum 2,128 gigs. 00:15:40.000 --> 00:15:42.000 So for the dropdown menu, we can go through, 00:15:42.000 --> 00:15:44.000 we can configure how much RAM we want to have, 00:15:44.000 --> 00:15:46.000 and then we can set, again, reservations, 00:15:46.000 --> 00:15:49.000 how much RAM is absolutely set aside just for this host. 00:15:49.000 --> 00:15:52.000 Maybe I can figure out on a VM 12 gigs of RAM 00:15:52.000 --> 00:15:56.000 for this Windows box, but I want to reserve 2 gigs. 00:15:56.000 --> 00:15:58.000 I want to make sure it always has these 2 gigs for it 00:15:58.000 --> 00:15:59.000 no matter what. 00:15:59.000 --> 00:16:02.000 If you're not over-provisioning your RAM, 00:16:02.000 --> 00:16:04.000 then you won't have contention that's going to make this 00:16:04.000 --> 00:16:06.000 even take effect, and the reservation won't matter 00:16:06.000 --> 00:16:09.000 because they'll all have all that they're allocated for, 00:16:09.000 --> 00:16:11.000 all they're configured for. 00:16:11.000 --> 00:16:14.000 This only matters if you're starting to really heavily 00:16:14.000 --> 00:16:16.000 over-allocate RAM to your VMs, 00:16:16.000 --> 00:16:18.000 then reservations might start to become important. 00:16:18.000 --> 00:16:20.000 So will things like shares. 00:16:20.000 --> 00:16:22.000 Shares and limits. 00:16:22.000 --> 00:16:26.000 Limits will say this is the max amount of physical RAM, 00:16:26.000 --> 00:16:28.000 so you probably never actually do this, 00:16:28.000 --> 00:16:31.000 but let's say you configured it for 12 gigs 00:16:31.000 --> 00:16:32.000 and you give it a limit of 8, 00:16:32.000 --> 00:16:34.000 it can actually never use more than 8. 00:16:34.000 --> 00:16:37.000 The VM thinks, the OS thinks it has 12. 00:16:37.000 --> 00:16:39.000 It's going to try and write from 8 up to 12. 00:16:39.000 --> 00:16:42.000 Those 4 gigs have to always be paged. 00:16:42.000 --> 00:16:44.000 All right, so be careful with your limits. 00:16:44.000 --> 00:16:49.000 And shares say if we have contention to CPU or to RAM 00:16:49.000 --> 00:16:53.000 or to our storage, how much of that resource do I get? 00:16:53.000 --> 00:16:57.000 VMs that all have the same number of shares 00:16:57.000 --> 00:16:59.000 will have the same amount of access. 00:16:59.000 --> 00:17:02.000 VMs that have more will have more access 00:17:02.000 --> 00:17:04.000 based upon how many more shares they have. 00:17:04.000 --> 00:17:05.000 If you have twice as many shares, 00:17:05.000 --> 00:17:07.000 you have twice as much access. 00:17:07.000 --> 00:17:08.000 All right? 00:17:08.000 --> 00:17:09.000 If you have half the number of shares, 00:17:09.000 --> 00:17:11.000 you have half the access. 00:17:11.000 --> 00:17:13.000 And hotplug just simply means, 00:17:13.000 --> 00:17:17.000 can we add RAM to the VM on the fly 00:17:17.000 --> 00:17:21.000 without shutting down the OS? 00:17:21.000 --> 00:17:22.000 Here's our hard disk. 00:17:22.000 --> 00:17:24.000 So we can go in there and say the size. 00:17:24.000 --> 00:17:27.000 We can customize what size we want it to be. 00:17:27.000 --> 00:17:31.000 We can also assign storage policies that have things like, 00:17:31.000 --> 00:17:33.000 you know, are we going to use encryption or not 00:17:33.000 --> 00:17:34.000 and things like that, right? 00:17:34.000 --> 00:17:36.000 So whatever our storage policy is defined 00:17:36.000 --> 00:17:41.000 will be passed on and inherited to that disk. 00:17:41.000 --> 00:17:44.000 We can specify the location of the hard disk. 00:17:44.000 --> 00:17:46.000 Okay, that's kind of an important one. 00:17:46.000 --> 00:17:48.000 By default, whatever the home folder is 00:17:48.000 --> 00:17:50.000 for that virtual machine, 00:17:50.000 --> 00:17:51.000 that's where the hard disk is going to go. 00:17:51.000 --> 00:17:53.000 If I create a new hard disk, that's where it's going to go. 00:17:53.000 --> 00:17:58.000 I can say I want this hard disk stored someplace else. 00:17:58.000 --> 00:18:00.000 And that is a pretty important thing because, again, 00:18:00.000 --> 00:18:03.000 I might have some storage that has a bunch of spinning disks 00:18:03.000 --> 00:18:05.000 and performance is just fine, 00:18:05.000 --> 00:18:09.000 and that's where I put my C drive for my operating system. 00:18:09.000 --> 00:18:12.000 But I have this flash storage that's really fast, 00:18:12.000 --> 00:18:14.000 but it's also really expensive, 00:18:14.000 --> 00:18:16.000 and I only put applications on it 00:18:16.000 --> 00:18:18.000 that need that level of performance. 00:18:18.000 --> 00:18:22.000 So I might put my D drive with my SQL database 00:18:22.000 --> 00:18:24.000 over on that flash storage, right, 00:18:24.000 --> 00:18:26.000 so that way I get better performance, 00:18:26.000 --> 00:18:28.000 but I'm not wasting that performance 00:18:28.000 --> 00:18:30.000 on my operating system, for example. 00:18:30.000 --> 00:18:31.000 Also, provisioning. 00:18:31.000 --> 00:18:34.000 Do I want to do thick provisioning or thin? 00:18:34.000 --> 00:18:40.000 Thick eager zeroed, thick lazy zeroed, or thin? 00:18:40.000 --> 00:18:43.000 And then, of course, we have sharing. 00:18:43.000 --> 00:18:44.000 We have shares. We have limits. 00:18:44.000 --> 00:18:50.000 We have IOP limits on there, okay? 00:18:50.000 --> 00:18:55.000 Hard disk mode, is it independent or dependent? 00:18:55.000 --> 00:18:58.000 So independent, we have independent persistent. 00:18:58.000 --> 00:19:02.000 Disk configuration remains after a power cycling, right, 00:19:02.000 --> 00:19:03.000 non-persistent. 00:19:03.000 --> 00:19:06.000 So basically, if it's independent, I can run it, 00:19:06.000 --> 00:19:08.000 make a bunch of changes, shut it down, 00:19:08.000 --> 00:19:10.000 and the configuration, all the changes are gone, right? 00:19:10.000 --> 00:19:13.000 Dependent means I keep all my changes. 00:19:13.000 --> 00:19:14.000 Virtual device, no. 00:19:14.000 --> 00:19:16.000 So basically, is this going to be a SCSI disk? 00:19:16.000 --> 00:19:20.000 Will the guest OS see it as a SCSI disk, as an IDE disk, 00:19:20.000 --> 00:19:24.000 or as a SATA disk? 00:19:24.000 --> 00:19:28.000 And then for SCSI controllers, so I can choose a SCSI disk. 00:19:28.000 --> 00:19:32.000 A SCSI disk is going to be a SCSI controller to connect to. 00:19:32.000 --> 00:19:34.000 So the different types we have available, 00:19:34.000 --> 00:19:39.000 we have bus logic parallel, LSI logic parallel, LSI logic SAS, 00:19:39.000 --> 00:19:41.000 and VMware ParaVirtual. 00:19:41.000 --> 00:19:42.000 So the VMware ParaVirtual, 00:19:43.000 --> 00:19:46.000 that is going to require VMware tools, 00:19:46.000 --> 00:19:48.000 and that is going to be like a really high-performing virtual 00:19:48.000 --> 00:19:49.000 adapter. 00:19:49.000 --> 00:19:51.000 All the ones that are like VMware-specific are going to be 00:19:51.000 --> 00:19:55.000 high-performing adapters. 00:19:55.000 --> 00:19:58.000 SCSI bus sharing, so we can say we want to allow none, 00:19:58.000 --> 00:19:59.000 virtual or physical. 00:19:59.000 --> 00:20:03.000 So basically, none means we're not allowing it. 00:20:03.000 --> 00:20:05.000 Physical means that we can actually connect to physical 00:20:05.000 --> 00:20:09.000 devices, and virtual means it virtualized through the SCSI 00:20:09.000 --> 00:20:13.000 virtualization. 00:20:13.000 --> 00:20:15.000 Stay at the network. 00:20:15.000 --> 00:20:17.000 So this is one of the more important things. 00:20:17.000 --> 00:20:18.000 All this is pretty important. 00:20:18.000 --> 00:20:22.000 If you mess up your disk adapters, 00:20:22.000 --> 00:20:24.000 it's going to be really difficult to fix that. 00:20:24.000 --> 00:20:26.000 But networking is one of the things I see the most often. 00:20:26.000 --> 00:20:28.000 People have to go back and change, 00:20:28.000 --> 00:20:30.000 because they've made a wrong selection. 00:20:30.000 --> 00:20:33.000 So do you want the network adapter connected to power on? 00:20:33.000 --> 00:20:35.000 Most of the time that's set to yes, 00:20:35.000 --> 00:20:37.000 but sometimes we do set that to no, 00:20:37.000 --> 00:20:42.000 because we're staging VMs that are going to replace other VMs, 00:20:42.000 --> 00:20:44.000 and we don't want there to be an IP address conflict or something 00:20:44.000 --> 00:20:45.000 like that. 00:20:45.000 --> 00:20:46.000 Or it's running a service, 00:20:46.000 --> 00:20:50.000 and we don't want the service to be seen by the network, 00:20:50.000 --> 00:20:53.000 and so I don't connect the network adapter. 00:20:53.000 --> 00:20:55.000 So what it would look like to the VM is if the cable is 00:20:55.000 --> 00:20:56.000 unplugged. 00:20:56.000 --> 00:20:57.000 That's what it looks like from the VM. 00:20:57.000 --> 00:20:59.000 So do you want to set power on or not? 00:20:59.000 --> 00:21:03.000 The adapter type, there is the VMX.3, 00:21:03.000 --> 00:21:06.000 and you can also choose an E1000. 00:21:06.000 --> 00:21:12.000 There's also the PVRDMA, 00:21:12.000 --> 00:21:21.000 basically allows for the VDRMA to be communicated over between VMs 00:21:21.000 --> 00:21:23.000 or to the physical network. 00:21:23.000 --> 00:21:26.000 So we can do this whole RDMA thing over our networking. 00:21:26.000 --> 00:21:32.000 PCI passthrough means that the VM actually takes control of the 00:21:33.000 --> 00:21:34.000 PCI device. 00:21:34.000 --> 00:21:35.000 It actually owns that network card. 00:21:35.000 --> 00:21:38.000 That network card is no longer available to the host to use for the 00:21:38.000 --> 00:21:39.000 other VMs. 00:21:39.000 --> 00:21:41.000 It's owned by that virtual machine. 00:21:41.000 --> 00:21:43.000 MAC address, static or automatic. 00:21:43.000 --> 00:21:46.000 So static means you are going to type in a MAC address, 00:21:46.000 --> 00:21:49.000 whereas automatic means it's going to automatically configure one and 00:21:49.000 --> 00:21:51.000 put it in the VMX file. 00:21:51.000 --> 00:21:54.000 Static, you're going to type it in and it gets put in the VMX file. 00:21:54.000 --> 00:21:55.000 You might do static. 00:21:55.000 --> 00:21:57.000 It's obviously going to be really rare. 00:21:57.000 --> 00:22:01.000 It used to be a little tiny bit more common when applications were 00:22:01.000 --> 00:22:04.000 sometimes licensed by the MAC address. 00:22:04.000 --> 00:22:08.000 And so if I'm moving the application from a physical box to a VM and I 00:22:08.000 --> 00:22:12.000 want to keep my license, I have to keep that MAC address. 00:22:12.000 --> 00:22:15.000 And so that's one of the more often times that's how I would see that 00:22:15.000 --> 00:22:16.000 used. 00:22:16.000 --> 00:22:19.000 It's almost never used anymore. 00:22:19.000 --> 00:22:23.000 CD-ROM drive, probably the most common thing you're going to select 00:22:23.000 --> 00:22:27.000 here is what ISO you want the CD-ROM drive to use. 00:22:28.000 --> 00:22:32.000 The CD-ROM drive could use the CD-ROM drive that's in the host. 00:22:32.000 --> 00:22:35.000 So if you have a CD in the CD-ROM drive in the host, 00:22:35.000 --> 00:22:37.000 most hosts don't have CD-ROM drives anymore. 00:22:37.000 --> 00:22:40.000 You could also say if you're, you know, the client device, 00:22:40.000 --> 00:22:42.000 so if you're connected to the vSphere client 00:22:42.000 --> 00:22:44.000 and you have a CD-ROM drive on your computer, 00:22:44.000 --> 00:22:46.000 you could actually pass that to the host. 00:22:46.000 --> 00:22:50.000 But nowadays, it's almost always going to be an ISO that you are 00:22:50.000 --> 00:22:52.000 mounting on that CD-ROM drive. 00:22:52.000 --> 00:22:55.000 And then if you want to say if you want that connected also or not. 00:22:55.000 --> 00:22:56.000 All right. 00:22:56.000 --> 00:23:00.000 And you can specify, you know, if that is IDE or SATA, 00:23:00.000 --> 00:23:03.000 how is it connected to the virtual machine. 00:23:05.000 --> 00:23:08.000 So video card, number of displays that you want, 00:23:08.000 --> 00:23:10.000 how much video memory do you want? 00:23:10.000 --> 00:23:12.000 Now, you can put in video memory in here. 00:23:12.000 --> 00:23:13.000 You can put a little bit. 00:23:13.000 --> 00:23:14.000 You can put more. 00:23:14.000 --> 00:23:16.000 If you're trying to do more displays, 00:23:16.000 --> 00:23:19.000 that means you need more video memory for better performance. 00:23:19.000 --> 00:23:20.000 Keep that in mind. 00:23:20.000 --> 00:23:24.000 If you have a video adapter that supports, you know, 3D pass through, 00:23:24.000 --> 00:23:28.000 then you can also enable 3D graphics pass through to the virtual machine. 00:23:30.000 --> 00:23:35.000 Multiple displays is probably more common on VMs that are being used for VDI. 00:23:35.000 --> 00:23:38.000 For, you know, servers, it's not used hardly ever. 00:23:41.000 --> 00:23:42.000 So you've gone through. 00:23:42.000 --> 00:23:45.000 You've made a lot of selections, right? 00:23:45.000 --> 00:23:47.000 You have configured the CPU. 00:23:47.000 --> 00:23:48.000 You configured memory. 00:23:48.000 --> 00:23:50.000 You gave it one or more hard drives. 00:23:50.000 --> 00:23:52.000 You configured one or more network adapters 00:23:52.000 --> 00:23:54.000 and a bunch of different things. 00:23:54.000 --> 00:23:56.000 You could also in there remove things. 00:23:56.000 --> 00:23:59.000 So a lot of VMs have USB controllers on them. 00:23:59.000 --> 00:24:03.000 You don't usually need USB controllers on most virtual machines. 00:24:03.000 --> 00:24:06.000 You can go there and remove the devices you don't need, things like that. 00:24:06.000 --> 00:24:10.000 You've made all those different options, you know, selections, 00:24:10.000 --> 00:24:11.000 and you can click finish. 00:24:13.000 --> 00:24:15.000 And when you click finish, it's going to go through. 00:24:15.000 --> 00:24:17.000 You'll see a task running at the bottom. 00:24:17.000 --> 00:24:18.000 It takes a moment. 00:24:18.000 --> 00:24:20.000 It doesn't take too long. 00:24:20.000 --> 00:24:26.000 And when it's all done, then you will see the VM in your vCenter. 00:24:26.000 --> 00:24:30.000 You can click on it, click the little triangle play icon to power it on. 00:24:30.000 --> 00:24:33.000 When you first power it on, it won't have an operating system, 00:24:33.000 --> 00:24:37.000 but if you mounted an ISO in it, it can boot to a, you know, 00:24:37.000 --> 00:24:39.000 a Windows ISO or a Linux ISO or whatever, you know, 00:24:39.000 --> 00:24:44.000 operating system you have in that CD-ROM drive that the ISO device is for, 00:24:44.000 --> 00:24:46.000 and you can start your installation from there, right? 00:24:46.000 --> 00:24:48.000 So you can launch the console. 00:24:48.000 --> 00:24:49.000 You see where it says power off. 00:24:49.000 --> 00:24:54.000 That will show you a little thumbnail of what would be on the monitor if 00:24:54.000 --> 00:24:57.000 this was a physical machine, and you can click in there, 00:24:57.000 --> 00:25:00.000 or you can say you want to launch a remote console, 00:25:00.000 --> 00:25:02.000 launch it to a web browser in a separate tab, 00:25:02.000 --> 00:25:06.000 and you can start going through your guest OS installation from that. 00:25:09.000 --> 00:25:10.000 So here we go. 00:25:10.000 --> 00:25:11.000 We see that we've gone through, 00:25:11.000 --> 00:25:14.000 and we've installed Ubuntu on this virtual machine. 00:25:14.000 --> 00:25:16.000 Now that we've discussed deploying virtual machines, 00:25:16.000 --> 00:25:19.000 let's go to our lab environment and deploy some virtual machines. 00:25:19.000 --> 00:25:24.000 So here in this lab environment, this is VMware's hands-on lab environment, 00:25:24.000 --> 00:25:26.000 so it's hol.vmware.com, 00:25:26.000 --> 00:25:31.000 and I just took their one-on-one introduction to VMware Lab to show you, 00:25:31.000 --> 00:25:33.000 here we have some virtual machines. 00:25:33.000 --> 00:25:39.000 Now we can go in and let's go ahead and just create a new virtual machine. 00:25:39.000 --> 00:25:42.000 We don't have an ISO in this environment to walk through the installation, 00:25:42.000 --> 00:25:45.000 but we can walk through actually creating the VM. 00:25:45.000 --> 00:25:48.000 And I'll show you one way to do it by creating a new VM, 00:25:48.000 --> 00:25:50.000 let's say a new virtual machine. 00:25:50.000 --> 00:25:53.000 And we're going to say, okay, yes, as we want to do, 00:25:53.000 --> 00:25:55.000 we want to create a virtual machine. 00:25:55.000 --> 00:25:58.000 And we're going to give the VM a name. 00:25:58.000 --> 00:26:02.000 Let's go ahead and call this lab01. 00:26:02.000 --> 00:26:08.000 And we've got to choose the compute resource we want to put this in, 00:26:08.000 --> 00:26:11.000 so I'm going to go ahead and choose a host to put this on. 00:26:12.000 --> 00:26:15.000 And then it wants to know what storage we want to put the VM on, 00:26:15.000 --> 00:26:18.000 so I'm going to go ahead and just choose this iSCSI storage here. 00:26:18.000 --> 00:26:21.000 It does also support NFS, either one would be fine. 00:26:24.000 --> 00:26:26.000 The compatibility mode, 00:26:26.000 --> 00:26:29.000 so if all of my hosts in my environment are running 8, 00:26:29.000 --> 00:26:31.000 then I can go ahead and choose 8 or later, 00:26:31.000 --> 00:26:33.000 or I could go in and say, well, 00:26:33.000 --> 00:26:37.000 actually I have some 7.0 update 2 in my environment, 00:26:37.000 --> 00:26:39.000 so I want to choose compatibility with that. 00:26:39.000 --> 00:26:42.000 Here we have all 8, so I'm going to go ahead and say 8. 00:26:42.000 --> 00:26:44.000 What OS are we going to install? 00:26:44.000 --> 00:26:47.000 If we're running Windows, we would say, obviously, Windows, 00:26:47.000 --> 00:26:50.000 and choose what version of Windows we're installing. 00:26:50.000 --> 00:26:52.000 We have 2022 and 19. 00:26:52.000 --> 00:26:55.000 We could choose a Windows desktop operating system. 00:26:55.000 --> 00:26:58.000 If we're running some version of Linux, we would say Linux, 00:26:58.000 --> 00:27:00.000 and then choose a distribution. 00:27:00.000 --> 00:27:04.000 As you can see, there's a lot of different distributions, Alma Linux, 00:27:04.000 --> 00:27:06.000 Rocky Linux, a bunch of RHEL. 00:27:07.000 --> 00:27:09.000 There's a bunch of different things in there we could choose from, 00:27:09.000 --> 00:27:10.000 some Debian. 00:27:10.000 --> 00:27:13.000 You can also just choose a generic version based upon the version of 00:27:13.000 --> 00:27:16.000 the kernel that you're running, or you're running Ubuntu. 00:27:18.000 --> 00:27:20.000 It doesn't really matter for this example, 00:27:20.000 --> 00:27:22.000 because we don't actually have an ISO to install, 00:27:22.000 --> 00:27:24.000 so we can just say we're going to run Windows. 00:27:24.000 --> 00:27:29.000 Now, what this kind of does matter for is basically the defaults. 00:27:31.000 --> 00:27:33.000 If I were to choose Windows, 00:27:33.000 --> 00:27:36.000 then VMware has some default suggestions for, like, 00:27:36.000 --> 00:27:40.000 the minimum amount of virtual CPU, the minimum amount of RAM, 00:27:40.000 --> 00:27:42.000 hard disk space. 00:27:42.000 --> 00:27:48.000 And then also, VMware knows if I'm running Windows Server 2022, 00:27:48.000 --> 00:27:50.000 this supports certain features. 00:27:50.000 --> 00:27:54.000 Like, can I hot add CPU, or am I able to hot add RAM, 00:27:54.000 --> 00:27:56.000 hot add virtual disk, right? 00:27:56.000 --> 00:28:00.000 If I chose a version of Linux, then it might say, okay, 00:28:00.000 --> 00:28:01.000 well, what version of Linux? 00:28:01.000 --> 00:28:06.000 Well, I'm running a really old version of RHEL that, you know, 00:28:06.000 --> 00:28:09.000 doesn't support a bunch of virtualization features, 00:28:09.000 --> 00:28:13.000 or I'm running a newer version of RHEL that does support these 00:28:13.000 --> 00:28:15.000 different virtualization features, right? 00:28:15.000 --> 00:28:17.000 So, what OS you choose is actually pretty important, 00:28:17.000 --> 00:28:21.000 because VMware will say, oh, based upon what you chose, 00:28:21.000 --> 00:28:23.000 it's going to be your guest operating system. 00:28:23.000 --> 00:28:25.000 We know these features are supported. 00:28:25.000 --> 00:28:28.000 We know this is recommended minimum hardware and things like that. 00:28:28.000 --> 00:28:31.000 The minimum hardware isn't as important because you can always easily 00:28:31.000 --> 00:28:35.000 overwrite that, but VMware knowing what features are supported by the 00:28:35.000 --> 00:28:38.000 operating system or what features are not supported by the operating 00:28:38.000 --> 00:28:40.000 system are actually pretty important. 00:28:40.000 --> 00:28:44.000 All right, so I'm going to say Windows Server here, say next. 00:28:44.000 --> 00:28:49.000 And here they're saying this is really the bare minimum. 00:28:49.000 --> 00:28:51.000 So, here we're saying that the minimum, 00:28:51.000 --> 00:28:54.000 that the hardest size we chose is greater than the data store that 00:28:54.000 --> 00:28:55.000 we've selected. 00:28:55.000 --> 00:29:04.000 What we could do is we can scroll down and see how it says this thick 00:29:04.000 --> 00:29:05.000 provision lazy zeroed. 00:29:05.000 --> 00:29:09.000 If we thin provision this, we can still create that disk of that size, 00:29:09.000 --> 00:29:11.000 and then we can move this VM to a different data store later. 00:29:11.000 --> 00:29:16.000 So, we resolved the lack of disk space issue by thin provisioning that 00:29:16.000 --> 00:29:21.000 virtual disk. 00:29:22.000 --> 00:29:27.000 And I can say how many virtual CPUs I want, right? 00:29:27.000 --> 00:29:30.000 We can go in, specify the number of CPU. 00:29:30.000 --> 00:29:33.000 We can say if we want, you know, any kind of reservations or limits, 00:29:33.000 --> 00:29:37.000 that kind of stuff on this. 00:29:37.000 --> 00:29:40.000 We can also go in how much RAM, 4 gigs. 00:29:40.000 --> 00:29:44.000 If we needed more, we could say we wanted more. 00:29:44.000 --> 00:29:48.000 The network driver, we can specify the network card. 00:29:48.000 --> 00:29:52.000 We can specify if we want the adapter to connect that power on. 00:29:52.000 --> 00:29:54.000 Connect that power on basically means, like, 00:29:54.000 --> 00:29:58.000 the adapter is plugged into an interface on a switch, right? 00:29:58.000 --> 00:30:00.000 We want that to be connected. 00:30:00.000 --> 00:30:03.000 Or if we unplug this, it'd be like unplugging the cable. 00:30:03.000 --> 00:30:07.000 The NIC is still there, but the cable will show as unplugged. 00:30:07.000 --> 00:30:12.000 We can also choose what kind of NIC we want to virtualize. 00:30:12.000 --> 00:30:15.000 We can say we want to use a VMXFET3, which is, like, the best performing. 00:30:15.000 --> 00:30:18.000 The problem is that we won't be able to use the adapter 00:30:18.000 --> 00:30:20.000 until we install VMware tools, right? 00:30:20.000 --> 00:30:23.000 If we need this VM to come online right away, connect to the network, 00:30:23.000 --> 00:30:26.000 get a DHCP address, run certain scripts and files, 00:30:26.000 --> 00:30:28.000 then we'll want to use the E1000, 00:30:28.000 --> 00:30:32.000 and we might need to upgrade that to the VMXFET3 at a later date. 00:30:32.000 --> 00:30:37.000 We can also say what virtual network we want to connect to, 00:30:37.000 --> 00:30:40.000 and we have a few different ones here already. 00:30:40.000 --> 00:30:42.000 By default right now we're just saying VM network, 00:30:42.000 --> 00:30:44.000 and that's fine for this demo. 00:30:44.000 --> 00:30:47.000 Maybe we wanted to connect to a different distributed virtual switch 00:30:47.000 --> 00:30:50.000 because we needed to connect to a certain VLAN that's, you know, on that one. 00:30:50.000 --> 00:30:56.000 We could choose that. 00:30:56.000 --> 00:30:58.000 You could also specify the SCSI controller. 00:30:58.000 --> 00:31:02.000 The LFI logic's fastest by default for Windows, 00:31:02.000 --> 00:31:03.000 but there are other options. 00:31:03.000 --> 00:31:05.000 We wanted to choose one of the other options. 00:31:05.000 --> 00:31:09.000 Again, VMware ParaVirtual would need to have VMware tools installed on there for that. 00:31:09.000 --> 00:31:13.000 That is an option also. 00:31:13.000 --> 00:31:15.000 Do we want a USB controller? 00:31:15.000 --> 00:31:18.000 Now, in some situations, if we're like, we're not going to need this, 00:31:18.000 --> 00:31:20.000 we're not going to need that, you might want to go in 00:31:20.000 --> 00:31:22.000 and just do something like maybe just, like, remove that device. 00:31:22.000 --> 00:31:26.000 Like, we don't need USB on this virtual machine for any reason. 00:31:26.000 --> 00:31:29.000 I know I don't need it, so I'm just going to go ahead and delete that, right? 00:31:29.000 --> 00:31:33.000 So, once we've gone through, oh, one kind of last thing. 00:31:33.000 --> 00:31:36.000 If we did have an ISO for an operating system we wanted to boot from, 00:31:36.000 --> 00:31:40.000 we could say we wanted to boot from an ISO, 00:31:40.000 --> 00:31:44.000 and then we would have to go to the data store that has that ISO uploaded to it, 00:31:44.000 --> 00:31:47.000 select it, and then when this machine powered on, 00:31:47.000 --> 00:31:51.000 it would boot to that ISO for installing the operating system. 00:31:51.000 --> 00:31:55.000 But for here, we can just say we want to use the client device. 00:31:55.000 --> 00:31:59.000 So, that would mean the device that this browser is from, 00:31:59.000 --> 00:32:01.000 or we can also say the host device. 00:32:01.000 --> 00:32:05.000 So, the ESXi host itself, if they have a CD-ROM drive in it, 00:32:05.000 --> 00:32:08.000 and there's a disk in there, it's going to connect to that CD-ROM drive. 00:32:08.000 --> 00:32:12.000 The downside of this option is that when this is connected, 00:32:12.000 --> 00:32:15.000 if this is powered on and that box connected is checked, 00:32:15.000 --> 00:32:20.000 then we're connected to this local ESXi host CD-ROM device, 00:32:20.000 --> 00:32:25.000 and I can't vMotion this VM off of this device if that is selected 00:32:25.000 --> 00:32:27.000 and that box is checked. 00:32:27.000 --> 00:32:31.000 Now, if that box is unchecked, I'll get a warning telling me 00:32:31.000 --> 00:32:34.000 that I have that configured but that I'm not connected. 00:32:34.000 --> 00:32:38.000 If it's connected, I'll get an error and vMotion would fail. 00:32:38.000 --> 00:32:43.000 We can go ahead and say next here, and then these are all the options. 00:32:43.000 --> 00:32:45.000 Yep, that's what I want to do. 00:32:45.000 --> 00:32:46.000 I'm good there. 00:32:46.000 --> 00:32:51.000 Say finish. 00:32:51.000 --> 00:32:53.000 And we will see that work went in, 00:32:53.000 --> 00:32:55.000 and we created that virtual machine. 00:32:55.000 --> 00:32:56.000 It's completed. 00:32:56.000 --> 00:32:59.000 So, then I could go in, if I had that option selected, 00:32:59.000 --> 00:33:02.000 that ISO in there, and right-click on that and power it on. 00:33:03.000 --> 00:33:11.000 Now, another thing I could do is I can also create a VM from another VM, 00:33:11.000 --> 00:33:13.000 or I can create a VM from a template. 00:33:13.000 --> 00:33:15.000 So, what I'm going to do here is I'm going to right-click on this 00:33:15.000 --> 00:33:16.000 Windows 10 machine. 00:33:16.000 --> 00:33:17.000 Notice it's even running. 00:33:17.000 --> 00:33:18.000 It's up and running. 00:33:18.000 --> 00:33:21.000 It's not necessarily the best way of doing this, 00:33:21.000 --> 00:33:25.000 but with a VM that's up and running even, right-click on it, 00:33:25.000 --> 00:33:29.000 and I can say I want to clone, either clone to a virtual machine 00:33:29.000 --> 00:33:31.000 or clone to a template. 00:33:31.000 --> 00:33:32.000 Just for this example, I'm going to say I'll go ahead 00:33:32.000 --> 00:33:34.000 and clone to a virtual machine. 00:33:34.000 --> 00:33:37.000 Give this machine a name. 00:33:37.000 --> 00:33:38.000 Choose where I want to put it. 00:33:38.000 --> 00:33:41.000 I'll say next. 00:33:41.000 --> 00:33:47.000 I've got to choose my compute resource again. 00:33:47.000 --> 00:33:54.000 Select the storage for this guy. 00:33:54.000 --> 00:33:55.000 And do I want to change anything? 00:33:55.000 --> 00:33:58.000 Do I want to customize the operating system? 00:33:58.000 --> 00:34:02.000 In an actual real scenario, doing a Windows machine like this, 00:34:02.000 --> 00:34:05.000 we want to customize the OS. 00:34:05.000 --> 00:34:09.000 We'd want to run like a sysprep on there so that it creates a new GUID. 00:34:09.000 --> 00:34:12.000 We're going to change the computer's name, all that kind of stuff, right? 00:34:12.000 --> 00:34:16.000 Do you want to customize the machine's hardware so I can check that box? 00:34:16.000 --> 00:34:18.000 And when I got to this next option, it'll ask me, 00:34:18.000 --> 00:34:21.000 do I want to change, you know, the number of virtual CPUs? 00:34:21.000 --> 00:34:23.000 Do I want to add more RAM or anything like that? 00:34:23.000 --> 00:34:25.000 Do I want to add a device? 00:34:25.000 --> 00:34:27.000 Do I want this one here to have an additional hard drive 00:34:27.000 --> 00:34:29.000 or something like that, right? 00:34:29.000 --> 00:34:33.000 If I don't need to customize any of that, then I wouldn't check that box. 00:34:33.000 --> 00:34:38.000 I would just say next, and it would go through its sysprep. 00:34:38.000 --> 00:34:39.000 I'm going to say finish here. 00:34:39.000 --> 00:34:44.000 When it powers on, it would go through and just kind of sysprep it for me. 00:34:44.000 --> 00:34:47.000 So now you can see it's cloning that virtual machine. 00:34:47.000 --> 00:34:48.000 Let's give this a few minutes. 00:34:48.000 --> 00:34:52.000 It takes a couple minutes for this to go through the whole process of cloning. 00:34:52.000 --> 00:34:54.000 All right, so the clone is completed. 00:34:54.000 --> 00:34:58.000 That job is completed, and I have that new virtual machine here. 00:34:58.000 --> 00:35:05.000 So another option I would have had or could have is when I right-click on this VM, 00:35:05.000 --> 00:35:06.000 it would also say I want to clone it. 00:35:06.000 --> 00:35:08.000 Instead of cloning it to a virtual machine, 00:35:08.000 --> 00:35:11.000 I could choose to clone it to a template, right? 00:35:11.000 --> 00:35:15.000 But when you clone it to a template, you can't edit that template. 00:35:15.000 --> 00:35:19.000 So maybe in this situation the reason why I cloned it to a virtual machine is I 00:35:19.000 --> 00:35:21.000 want to go in and I want to make changes. 00:35:21.000 --> 00:35:22.000 I want to power it up. 00:35:22.000 --> 00:35:23.000 I want to go into there. 00:35:23.000 --> 00:35:25.000 I want to install a piece of software. 00:35:25.000 --> 00:35:26.000 I want to uninstall some software. 00:35:26.000 --> 00:35:28.000 I want to copy some files over to it. 00:35:28.000 --> 00:35:32.000 I want to customize the first time you log into it, something like that. 00:35:32.000 --> 00:35:33.000 I made some changes. 00:35:33.000 --> 00:35:40.000 Maybe I just want to go in here, edit settings, and I'm going to add a new device. 00:35:40.000 --> 00:35:42.000 I want to add a hard disk to it. 00:35:42.000 --> 00:35:43.000 Let's say I want to go in. 00:35:43.000 --> 00:35:50.000 You've got a thin provision that's just kind of unlimited on space, on my storage. 00:35:50.000 --> 00:36:01.000 And maybe I want to also add another network card to this guy maybe, right? 00:36:02.000 --> 00:36:04.000 Network adapter. 00:36:04.000 --> 00:36:08.000 In reality, multi-home computers are a really bad idea, not a good practice. 00:36:08.000 --> 00:36:11.000 But let's just say for the example, I need to connect this guy to a couple 00:36:11.000 --> 00:36:12.000 different networks. 00:36:12.000 --> 00:36:16.000 So I'm going to connect it to, you know, this network as well. 00:36:16.000 --> 00:36:20.000 So I've customized this machine, you know, to the extent that I can. 00:36:20.000 --> 00:36:22.000 I'm going to go in here and I'm going to add a new device. 00:36:22.000 --> 00:36:24.000 I'm going to go in here and I'm going to add a new device. 00:36:24.000 --> 00:36:26.000 I'm going to go in here and I'm going to add a new device. 00:36:27.000 --> 00:36:32.000 So I've customized this machine, you know, to the extent that I need. 00:36:32.000 --> 00:36:34.000 I'm going to go ahead and do a CLK to that. 00:36:34.000 --> 00:36:38.000 And now that I've cloned this machine, I customized it over here. 00:36:38.000 --> 00:36:41.000 Maybe I powered it on and I installed some software that I need. 00:36:41.000 --> 00:36:45.000 All the machines that I create from this machine forward, 00:36:45.000 --> 00:36:46.000 I need to have this software. 00:36:46.000 --> 00:36:50.000 And I plan on making this be kind of like the gold standard 00:36:50.000 --> 00:36:52.000 for my virtual machines going forward. 00:36:52.000 --> 00:36:53.000 I ran Windows updates on it. 00:36:53.000 --> 00:36:55.000 It's all current up to date. 00:36:55.000 --> 00:36:59.000 And now I just want to save this virtual machine so that it doesn't 00:36:59.000 --> 00:37:01.000 accidentally get changed later. 00:37:01.000 --> 00:37:07.000 I can right-click on here and I can say templates. 00:37:07.000 --> 00:37:10.000 And I can convert it to a template. 00:37:10.000 --> 00:37:15.000 And really all I'm kind of doing is just changing the name of the VMX file. 00:37:15.000 --> 00:37:16.000 So now it's a template. 00:37:16.000 --> 00:37:20.000 And you know, like, well, if it became a template, where'd my Lab02 go? 00:37:20.000 --> 00:37:25.000 If I go over to here, now from here I see I have my template. 00:37:25.000 --> 00:37:30.000 You notice the icon is different from the VM versus for the template. 00:37:30.000 --> 00:37:33.000 And now I can create all the VMs I want to from this template. 00:37:33.000 --> 00:37:38.000 I can right-click on a template and I can say I want a new virtual 00:37:38.000 --> 00:37:41.000 machine from this template. 00:37:41.000 --> 00:37:46.000 We can go in, Lab03. 00:37:46.000 --> 00:37:47.000 We'll say next. 00:37:47.000 --> 00:37:55.000 Let's choose our compute resource. 00:37:55.000 --> 00:37:59.000 Choose our storage. 00:37:59.000 --> 00:38:01.000 Do we want to customize the operating system again? 00:38:01.000 --> 00:38:04.000 In reality, we would. 00:38:04.000 --> 00:38:06.000 Say next. 00:38:06.000 --> 00:38:10.000 And we'll finish that. 00:38:10.000 --> 00:38:16.000 And now we're creating a virtual machine from that template that I just 00:38:16.000 --> 00:38:21.000 created for my VM called Lab03. 00:38:21.000 --> 00:38:24.000 So as you can see while this is cloning, 00:38:24.000 --> 00:38:27.000 that you can create brand-new VMs just from scratch. 00:38:27.000 --> 00:38:29.000 All we need to do is simply go in. 00:38:29.000 --> 00:38:31.000 We can say where we want to put them. 00:38:31.000 --> 00:38:32.000 Right-click. 00:38:32.000 --> 00:38:35.000 And we want to create a new virtual machine. 00:38:35.000 --> 00:38:41.000 We can also clone existing virtual machines. 00:38:41.000 --> 00:38:43.000 And just say we want to clone it to a virtual machine. 00:38:43.000 --> 00:38:46.000 We can clone it straight to a template if we wanted to create a template. 00:38:46.000 --> 00:38:52.000 And we can also create virtual machines from our existing templates. 00:38:52.000 --> 00:38:55.000 So those are some different ways that you can create 00:38:55.000 --> 00:38:59.000 and deploy new virtual machines in a VMware vSphere 8 environment.