RickVerstegen's Accepted Solutions

Check VMware Knowledge Base to see if that will help you. Rick
Try upgrading from CLI: How To: Upgrade VMware vSphere ESXi 6.5 to 6.7 via CLI – nokitel Rick
Hi suhag79 1. Edit the Storage Policy under Health and Performance and click OK. 2. This will bring the Object back to compliance. Rick Please consider marking this answer "correct" or... See more...
Hi suhag79 1. Edit the Storage Policy under Health and Performance and click OK. 2. This will bring the Object back to compliance. Rick Please consider marking this answer "correct" or "helpful" if you think your query have been answered correctly.
I guess you do it with Powershell by using this command: Get-VM | Get-VMResourceConfiguration | where {$_.MemLimitGB -ne '-1'} Rick
If you created a snapshot or backup before the HW upgrade you can revert back otherwise you need to build a brand new one. By the way, can you check if KB4284880 is installed within the guest OS... See more...
If you created a snapshot or backup before the HW upgrade you can revert back otherwise you need to build a brand new one. By the way, can you check if KB4284880 is installed within the guest OS? There is a similar thread about this topic on technet: Server 2016 Hot Add CPU in VMware gets BSOD "UNSUPPORTED PROCESSOR" Rick
Hi ricky73​, You can try the following steps: 1. Download and install the OVFTool 2. Run the command ovftool <path of .ovf file> <path for converted .vmx file> You will get a VMX file. Edit... See more...
Hi ricky73​, You can try the following steps: 1. Download and install the OVFTool 2. Run the command ovftool <path of .ovf file> <path for converted .vmx file> You will get a VMX file. Edit the hardware version in it, change it to a version that is compatible with your hardware for example vmx-07. Once done, save the .VMX file. 3. Then you need to convert the VMX back to OVF. Run the command ovftool <path of .vmx file> <path for converted .ovf file> 4. After this is done try to deploy the OVF again. Rick Please consider marking this answer "correct" or "helpful" if you think your query have been answered correctly.
Hi ComNetworkCDS​, Are you able to power on the machine from the vSphere Client connected to the ESXi host? Also check if the VMware vCenter workflow manager service is running on vCenter. ... See more...
Hi ComNetworkCDS​, Are you able to power on the machine from the vSphere Client connected to the ESXi host? Also check if the VMware vCenter workflow manager service is running on vCenter. Rick Please consider marking this answer "correct" or "helpful" if you think your query have been answered correctly.
Hello MRAntonio​, Yes, these licenses would be valid. Check and read the link below: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsphere/vmware-vsphere-essent... See more...
Hello MRAntonio​, Yes, these licenses would be valid. Check and read the link below: https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsphere/vmware-vsphere-essentials-kits-datash… Regards, Rick
Hi as900w​, The total resource requirements for the powered-on virtual machines is comprised of two components, CPU and memory. The total host resources available for virtual machines is calcu... See more...
Hi as900w​, The total resource requirements for the powered-on virtual machines is comprised of two components, CPU and memory. The total host resources available for virtual machines is calculated by adding the hosts' CPU and memory resources. The Current CPU Failover Capacity is computed by subtracting the total CPU resource requirements from the total host CPU resources and dividing the result by the total host CPU resources. The Current Memory Failover Capacity is calculated similarly. Example: The cluster is comprised of four hosts, each with a different amount of available CPU and memory resources. The first host has 8Ghz of available CPU resources and 24 GB of available memory, while Host 2 + 3 have 10Ghz of available CPU resources and 16GB of memory. Host 4 has 7Ghz of CPU resources and 12GB of available memory. There are 4 powered-on virtual machine in the cluster with differing CPU and memory requirements. VM1 need 2Ghz of CPU resources and 4GB of memory, while VM2 needs 3Ghz and 2GB, VM3 needs 1Ghz and 1GB, VM4 needs 3Ghz and 6GB. The Configured Failover Capacity for CPU and Memory are both set to 25%. The total resource requirements for the powered-on virtual machines is 9GHz and 13GB. The total host resources available for virtual machines is 35GHz and 68GB. Based on this, the Current CPU Failover Capacity is 74% ((35GHz - 9GHz)/35GHz). Similarly, the Current Memory Failover Capacity is 80% ((68GB-13GB)/68GB). Because the cluster's Configured Failover Capacity is set to 25%, 49% of the cluster's total CPU resources and 55% of the cluster's memory resources are still available to power on additional virtual machines. Rick