dskwared's Posts

Bummer about the templates! That's how we do it currently. We have a few Windows Server templates with UEFI set as the default boot mode. However, our template is more of a skeleton, as it only c... See more...
Bummer about the templates! That's how we do it currently. We have a few Windows Server templates with UEFI set as the default boot mode. However, our template is more of a skeleton, as it only contains CPU, RAM, Disks, UEFI boot, Secure boot, etc., but contains no OS. It's just a VM shell. From there, we then deploy the guest OS via SCCM / PXE Boot. I bet it could be scripted somehow, as in, create the default VM the way you normally do. Once the shell is created, run a script against the new VM and set the boot firmware to UEFI. For example, as listed in the VMware Documentation, Enable or Disable UEFI Secure Boot for a Virtual Machine, do something like this: $vm = Get-VM TestVM $spec = New-Object VMware.Vim.VirtualMachineConfigSpec $spec.Firmware = [VMware.Vim.GuestOsDescriptorFirmwareType]::efi $vm.ExtensionData.ReconfigVM($spec) I know it's still a bit manual, but since the vCenter default can't be changed, perhaps this might speed up your workflow a bit? Cheers, Doug
Just checking... But in the VM settings, is the Guest OS version set to Windows Server 2016? Also, see VMware Knowledge Base KB59222 and VMware Compatibility Guide - Guest/Host Search for Wind... See more...
Just checking... But in the VM settings, is the Guest OS version set to Windows Server 2016? Also, see VMware Knowledge Base KB59222 and VMware Compatibility Guide - Guest/Host Search for Windows Server 2019 compatibility and limitations with ESXi 6.7.
In short, you can't go straight from 5.5 to 6.7. You'd have to upgrade the 5.5 stuff to either 6.0 or 6.5 first before going to 6.7. See the Upgrade Path tab of the Interoperability Matrix from V... See more...
In short, you can't go straight from 5.5 to 6.7. You'd have to upgrade the 5.5 stuff to either 6.0 or 6.5 first before going to 6.7. See the Upgrade Path tab of the Interoperability Matrix from VMware. As saravananyuvaraj​ mentioned, you could build out a brand-new vCenter 6.7 server and 6.7 ESXi hosts, present the same datastores to that new cluster, and unregister the VMs from the hold environment, and re-register them in the new environment.
Are you sure the -s (packet size) parameter in the vmkping command is set correctly? See this VMware Knowledge Base (KB 1003728) where -s should be set to 8972 for jumbo frames.
We've seen this issue in our environment in both 6.0 and 6.5. What we've had to do on occasion is log into a host directly and perform the the capacity increase there. After doing that, vCenter t... See more...
We've seen this issue in our environment in both 6.0 and 6.5. What we've had to do on occasion is log into a host directly and perform the the capacity increase there. After doing that, vCenter then reported the correct capacity.
If you aren't able to use host profiles due to licensing, have you taken a look at the Ultimate Deployment Appliance? It includes a small DHCP server, PXE, etc. and can customize each host with a... See more...
If you aren't able to use host profiles due to licensing, have you taken a look at the Ultimate Deployment Appliance? It includes a small DHCP server, PXE, etc. and can customize each host with a boot menu. Be advised, the appliance is a little dated, and we've had trouble getting it to work with UEFI boot mode. It all depends on how you're building your hosts.
I agree with a.p.​, I'm not aware of a method you can use to change the screen resolution on the DCUI. If you're running into a display or resolution problem, have you tried connecting to the hos... See more...
I agree with a.p.​, I'm not aware of a method you can use to change the screen resolution on the DCUI. If you're running into a display or resolution problem, have you tried connecting to the host via SSH and running the command DCUI? That will bring up a text-based version of the DCUI in the SSH window.
My understanding is that the process is quite similar, however you would need to ensure that the physical RDM disk is also zoned/mapped to the new ESXi 6.5 host for the VM to see. Also, don't for... See more...
My understanding is that the process is quite similar, however you would need to ensure that the physical RDM disk is also zoned/mapped to the new ESXi 6.5 host for the VM to see. Also, don't forget to tag that RDM disk as being perennially reserved on the ESXi 6.5 host(s) in the new environment to prevent long host reboots.
Could you convert the physical RDM disk to a virtual RDM disk? That would at least give you the ability to snapshot the RDM disk once it's converted.
We have Round Robin multipathing configured as the default (including RDM LUNs) in our environment, and I don't recall seeing any issues as a result of that configuration.
Have you tried powering off the VM directly on the ESXi host instead of the vCenter Server? Also, see if anything in this KB article helps: Unable to power off the virtual machine in an ESXi host... See more...
Have you tried powering off the VM directly on the ESXi host instead of the vCenter Server? Also, see if anything in this KB article helps: Unable to power off the virtual machine in an ESXi host (1014165) | VMware KB
Are you able to update your vCenter Server to a version equal to or greater than your ESXi host? Someone correct me if I'm wrong, but from what I understand, the ESXi host cannot be a newer versi... See more...
Are you able to update your vCenter Server to a version equal to or greater than your ESXi host? Someone correct me if I'm wrong, but from what I understand, the ESXi host cannot be a newer version than the vCenter Server.
Missing in vSphere Host Client compared to vSphere Client: The ability to a Software iSCSI Adapter in Storage > Adapters section. You can only view existing HBAs, but there's no option to add n... See more...
Missing in vSphere Host Client compared to vSphere Client: The ability to a Software iSCSI Adapter in Storage > Adapters section. You can only view existing HBAs, but there's no option to add new ones.
Ah! Thanks for the clarification!
Have a look at this thread by continuum - Latest Converter corrupts XP boot files. In there, he mentions that there may be an issue with the latest VMware Converter utility possibly corrupting th... See more...
Have a look at this thread by continuum - Latest Converter corrupts XP boot files. In there, he mentions that there may be an issue with the latest VMware Converter utility possibly corrupting the boot sector in Windows XP.
Perhaps this post by Virtuin may help you: Virtuin: Rename ESXi Hosts in vCenter (Without Losing Historical Data)
I just tried LokeshHK​'s suggestion and that seemed to work for me. However, I had to clear my browser cache and reload the page in order for the language changes to fully stick.
About how long ago was this vCenter deployed? By default, the administrator@vsphere.local password expires after 90 days. (See Edit the vCenter Single Sign-On Password Policy). Is there another s... See more...
About how long ago was this vCenter deployed? By default, the administrator@vsphere.local password expires after 90 days. (See Edit the vCenter Single Sign-On Password Policy). Is there another single sign-on user with administrative privileges that can reset it?
What build number of 6.0 are you currently running? I've run into issues before where storage disappears from a host when running ESXi 6.0 GA.
Just out of curiosity, are there any RDM LUNs attached to these hosts? I've seen this sort of thing happen if the RDM LUNs aren't set to Perennially Reserved = True.