Figure 8. 8 By default, assigning a permission to an object will propagate that permission to all child objects. leaving resource pools as the only viable option to group vM i host, Figure 8. 9 Folder obiects cannot be added to an individual esXi Figure 8.10 As objects in the inventory, resource pools are potential levels of infrastructure management. Figure 8.11 The vSphere Client provides a breakdown of where roles are currently in use. Figure 8.12 Certificate Manager provides a number of operations for managing certificates in your vSphere 6 environment. Figure 8.13 The vCenter Server default roles offer much more flexibility than an individual eSXi host offers. Figure 8.14 VCenter Servers logs are visible from within the log Browser section of the vSphere Web client. Chapter g Figure 9.1 VMware ESXi provides both generic and virtualization- optimized hardware for VMs. Figure 9.2 The file browser in the vSphere Web client shows only a single vmDK file. Figure 9.3 There are actually two vMDK files for every virtual hard disk in a vm, even though the vSphere Web client shows only a single file Figure 9.4 You can launch the New Virtual Machine Wizard from the context menu of a vCenter datacenter, virtual datacenter, an ESXi cluster, or an individual esXi host. Figure 9.5 Options for creating a new virtual machine when using the vSphere Web client Figure 9.6 The logical folder structure selected here does not correspond to where the vM files (for example, VMX and vmare located on the selected datastore. Figure g. You can use storage service levels to help automate vM storage placement decisions when you create a new VM
Figure 8.8 By default, assigning a permission to an object will propagate that permission to all child objects. Figure 8.9 Folder objects cannot be added to an individual ESXi host, leaving resource pools as the only viable option to group VMs. Figure 8.10 As objects in the inventory, resource pools are potential levels of infrastructure management. Figure 8.11 The vSphere Client provides a breakdown of where roles are currently in use. Figure 8.12 Certificate Manager provides a number of operations for managing certificates in your vSphere 6 environment. Figure 8.13 The vCenter Server default roles offer much more flexibility than an individual ESXi host offers. Figure 8.14 vCenter Server’s logs are visible from within the Log Browser section of the vSphere Web Client. Chapter 9 Figure 9.1 VMware ESXi provides both generic and virtualizationoptimized hardware for VMs. Figure 9.2 The file browser in the vSphere Web Client shows only a single VMDK file. Figure 9.3 There are actually two VMDK files for every virtual hard disk in a VM, even though the vSphere Web Client shows only a single file. Figure 9.4 You can launch the New Virtual Machine Wizard from the context menu of a vCenter datacenter, virtual datacenter, an ESXi cluster, or an individual ESXi host. Figure 9.5 Options for creating a new virtual machine when using the vSphere Web Client Figure 9.6 The logical folder structure selected here does not correspond to where the VM files (for example, VMX and VMDK) are located on the selected datastore. Figure 9.7 You can use storage service levels to help automate VM storage placement decisions when you create a new VM
Figure 9.8 When using VM storage policies, select a compatible datastore to ensure that the VM's storage needs are properly satisfied. Figure 9.9 Based on guest OS selection, the vSphere Web client provides some basic guidelines on the amount of memory you should configure for the VM. Figure 9.10 You can configure a vM with up to 10 network adapters, of the same or different types, that reside on the same or different networks as needed. Figure 9.11 A virtual disk is configured automatically when you create a new virtual machine. You can also add additional virtual disks by using the new device option. Figure 9.12 vSphere 6 offers a number of different Disk Provisioning options when you're creating new virtual disks. Figure 9.13 You can configure the virtual disk on a number of different SCSI adapters and SCSI IDs, and you can configure it as an independent disk. Figure 9.14 Reviewing the configuration of the New virtual Machine Wizard ensures the correct settings for the vM and prevents mistakes that require deleting and re-creating the vM. Figure 9.15 The display name assigned to a vm is used in a variety of places Figure 9.16 vSphere automatically appends a number to the filename for additional virtual hard disks Figure 9 17 VMs can access optical disks physically located on the vSphere Web client system, located on the ESXi host, or stored as an ISO image Figure 9.18 Use the Upload button to upload iSo images for use when installing guest OSs. Figure 9.19 Changing the hardware acceleration feature of a windows guest oS is a common and helpful adjustment for improving mouse performance Figure 9.20 As of v Sphere 5.1, you can no longer configure properties in VMware Tools by interacting with the icon in the system tray
Figure 9.8 When using VM storage policies, select a compatible datastore to ensure that the VM’s storage needs are properly satisfied. Figure 9.9 Based on guest OS selection, the vSphere Web Client provides some basic guidelines on the amount of memory you should configure for the VM. Figure 9.10 You can configure a VM with up to 10 network adapters, of the same or different types, that reside on the same or different networks as needed. Figure 9.11 A virtual disk is configured automatically when you create a new virtual machine. You can also add additional virtual disks by using the New device option. Figure 9.12 vSphere 6 offers a number of different Disk Provisioning options when you’re creating new virtual disks. Figure 9.13 You can configure the virtual disk on a number of different SCSI adapters and SCSI IDs, and you can configure it as an independent disk. Figure 9.14 Reviewing the configuration of the New Virtual Machine Wizard ensures the correct settings for the VM and prevents mistakes that require deleting and re-creating the VM. Figure 9.15 The display name assigned to a VM is used in a variety of places. Figure 9.16 vSphere automatically appends a number to the filename for additional virtual hard disks. Figure 9.17 VMs can access optical disks physically located on the vSphere Web Client system, located on the ESXi host, or stored as an ISO image. Figure 9.18 Use the Upload button to upload ISO images for use when installing guest OSs. Figure 9.19 Changing the hardware acceleration feature of a Windows guest OS is a common and helpful adjustment for improving mouse performance. Figure 9.20 As of vSphere 5.1, you can no longer configure properties in VMware Tools by interacting with the icon in the system tray
Figure 9.21 You can view details about VMware Tools, DNS name, IP address, and so forth from the Summary tab of a vm object. Figure 9. 22 You invoke the Register Virtual Machine Wizard by right- clicking the datastore and selecting Register VM Figure 9.23 The Power submenu allows you to power on, power off, suspend, or reset a vM as well as interact with the guest OS if VMware Tools is installed. Figure 9.24 Users can add some types of hardware while the vM powered on. If virtual hardware cannot be added while the vm is powered on, the operation will fail. Figure 9.25 To add a new network adapter, you must select the adapter type, the network, and whether it should be connected at power-on. Figure 9.26 The ability to add memory to a vm that is already powered on is restricted to VMs with memory hot-add enabled. Figure 9.27 With CPU hot-plug enabled, more virtual CPU sockets can be configured, but the number of cores per CPu cannot be altered. Figure 9.28 Providing names and descriptions for snapshots is an easy way to manage multiple historical snapshots. Figure 9.29 When a snapshot is taken, some additional files are created on the vm's datastore Figure 9.30 The Snapshot Manager can revert to a previous snapshot, but all data written since that snapshot was taken and that hasn't been backed up elsewhere will be lost. Figure 9.31 This VM running Windows Server 2012 has had some data placed into two temporary folders. Figure 9.32 The same VM, after reverting to a snapshot taken before the temporary folders were created, no longer has any record of the da Chapter10 Figure 10.1 If the Sysprep files are not extracted and stored on the VCenter Server system, you might not be able to customize the guest OS when you clone a VM
Figure 9.21 You can view details about VMware Tools, DNS name, IP address, and so forth from the Summary tab of a VM object. Figure 9.22 You invoke the Register Virtual Machine Wizard by rightclicking the datastore and selecting Register VM. Figure 9.23 The Power submenu allows you to power on, power off, suspend, or reset a VM as well as interact with the guest OS if VMware Tools is installed. Figure 9.24 Users can add some types of hardware while the VM is powered on. If virtual hardware cannot be added while the VM is powered on, the operation will fail. Figure 9.25 To add a new network adapter, you must select the adapter type, the network, and whether it should be connected at power-on. Figure 9.26 The ability to add memory to a VM that is already powered on is restricted to VMs with memory hot-add enabled. Figure 9.27 With CPU hot-plug enabled, more virtual CPU sockets can be configured, but the number of cores per CPU cannot be altered. Figure 9.28 Providing names and descriptions for snapshots is an easy way to manage multiple historical snapshots. Figure 9.29 When a snapshot is taken, some additional files are created on the VM’s datastore. Figure 9.30 The Snapshot Manager can revert to a previous snapshot, but all data written since that snapshot was taken and that hasn’t been backed up elsewhere will be lost. Figure 9.31 This VM running Windows Server 2012 has had some data placed into two temporary folders. Figure 9.32 The same VM, after reverting to a snapshot taken before the temporary folders were created, no longer has any record of the data. Chapter 10 Figure 10.1 If the Sysprep files are not extracted and stored on the vCenter Server system, you might not be able to customize the guest OS when you clone a VM
Figure 10.2 The Customization Specification Manager is readily accessible from the home page of the vSphere Web client in the Management tab Figure 10.3 The Guest Customization Wizard offers four options for naming a cloned VM. Figure 10.4 Click this button to customize the network interface settings. Figure 10.5 The Edit Network dialog box has an option to prompt the user for an address Figure 10.6 The Clone Existing Virtual Machine izard offers several options for customizing the guest OS. Figure 10.7 Your guest oS customizations as a specification are saved for later use, even if created in the middle of the vm cloning wizard Figure 10. 8 The cloning task in the vSphere Web client provides feedback on the current status of the vM cloning operation. Figure 10.9 Users can either convert a vm to a template or clone the VM to a template. Figure 10.10 VCenter Server offers four options for storing a template's virtual disks Figure 10.11 Select a datastore for a new vM based on the vMotion, DRS, HA, and other constraints of your organization. Figure 10.12 VCenter Server uses a wizard to deploy templates from OVE Figure 10.13 Source networks defined in the ovF template are mapped to port groups and dv port groups in vCenter Server. Figure 10.14 vSphere administrators have different options for controlling how new VMs are deployed from ovF templates and assigned an IP address. Figure 10.15 The Deploy ovF Template wizard provides a warning if properties have invalid values assigned Figure 10.16 This VM exported as an ovf template shows the different components of the template
Figure 10.2 The Customization Specification Manager is readily accessible from the home page of the vSphere Web Client in the Management tab. Figure 10.3 The Guest Customization Wizard offers four options for naming a cloned VM. Figure 10.4 Click this button to customize the network interface settings. Figure 10.5 The Edit Network dialog box has an option to prompt the user for an address. Figure 10.6 The Clone Existing Virtual Machine Wizard offers several options for customizing the guest OS. Figure 10.7 Your guest OS customizations as a specification are saved for later use, even if created in the middle of the VM cloning wizard. Figure 10.8 The cloning task in the vSphere Web Client provides feedback on the current status of the VM cloning operation. Figure 10.9 Users can either convert a VM to a template or clone the VM to a template. Figure 10.10 vCenter Server offers four options for storing a template’s virtual disks. Figure 10.11 Select a datastore for a new VM based on the vMotion, DRS, HA, and other constraints of your organization. Figure 10.12 vCenter Server uses a wizard to deploy templates from OVF. Figure 10.13 Source networks defined in the OVF template are mapped to port groups and dvPort groups in vCenter Server. Figure 10.14 vSphere administrators have different options for controlling how new VMs are deployed from OVF templates and assigned an IP address. Figure 10.15 The Deploy OVF Template Wizard provides a warning if properties have invalid values assigned. Figure 10.16 This VM exported as an OVF template shows the different components of the template
Figure 10. 17 Content Libraries can be useful when managing templates and images for multiple site locations. Figure 10. 18 You will want to ensure that these default resource allocation settings are appropriate for your specific environment. Figure 10. 19 The Edit vapp dialog box is where you can make any changes that need to be made to a vapps configuration. Figure 10.20 There are different options for assigning IP addresses to Ms inside a vapp dHCP or granular settings via the ove environment can be configured. Figure 10.21 If you want to use the Transient (also called OvE Environment)or DHCP options, you must enable them in this dialog box Figure 10.22 The vSphere Web client displays the metadata in the Summary tab of a vApp object. Figure 10.23 Using Guest Shutdown instead of power Off will provide application and os consistency and help avoid corruption in the guest oS instance. Figure 10.24 The Actions menu for a vApp offers options to change the power state for all vMs within the e vapp Chapter 11 Figure 11.1 Reservations, limits, and shares offer more fine-grained control over resource allocation Figure 11.2 The memory configuration settings for a VM indicate the amount of ram the vm thinks "it has Figure 11.3 vSphere supports the use of reservations, shares, and limits for controlling memory allocation. Figure 11.4 This memory reservation guarantees 1, 024 MB of raM for the VM Figure 11.5 The memory reservation reduces the potential need for VMkernel swap space by the size of the reservation. Figure 11.6 Shares establish relative priority based on the number of shares assigned out of the total shares allocated
Figure 10.17 Content Libraries can be useful when managing templates and images for multiple site locations. Figure 10.18 You will want to ensure that these default resource allocation settings are appropriate for your specific environment. Figure 10.19 The Edit vApp dialog box is where you can make any changes that need to be made to a vApp’s configuration. Figure 10.20 There are different options for assigning IP addresses to VMs inside a vApp. DHCP or granular settings via the OVF environment can be configured. Figure 10.21 If you want to use the Transient (also called OVF Environment) or DHCP options, you must enable them in this dialog box. Figure 10.22 The vSphere Web Client displays the metadata in the Summary tab of a vApp object. Figure 10.23 Using Guest Shutdown instead of Power Off will provide application and OS consistency and help avoid corruption in the guest OS instance. Figure 10.24 The Actions menu for a vApp offers options to change the power state for all VMs within the vApp. Chapter 11 Figure 11.1 Reservations, limits, and shares offer more fine-grained control over resource allocation. Figure 11.2 The memory configuration settings for a VM indicate the amount of RAM the VM “thinks” it has. Figure 11.3 vSphere supports the use of reservations, shares, and limits for controlling memory allocation. Figure 11.4 This memory reservation guarantees 1,024 MB of RAM for the VM. Figure 11.5 The memory reservation reduces the potential need for VMkernel swap space by the size of the reservation. Figure 11.6 Shares establish relative priority based on the number of shares assigned out of the total shares allocated