pragg12's Accepted Solutions

Hi, If the GUI is not working for you, you can try CLI method from below link. I used this with VCSA 6.7; haven't tried it in VCSA 7 yet but since the command is available in VCSA 7, it should work.... See more...
Hi, If the GUI is not working for you, you can try CLI method from below link. I used this with VCSA 6.7; haven't tried it in VCSA 7 yet but since the command is available in VCSA 7, it should work. Also, ensure you have backup of existing appliance before proceeding with this. How to patch VMware VCSA | StarWind Blog (starwindsoftware.com)
Hi, I will try to put in my 2 cents as I am reading this. If a virtual machine has 128 virtual CPUs or less, you cannot use hot adding to further increase the number of virtual CPUs. To chan... See more...
Hi, I will try to put in my 2 cents as I am reading this. If a virtual machine has 128 virtual CPUs or less, you cannot use hot adding to further increase the number of virtual CPUs. To change the number of virtual CPUs beyond that limit, you must first power off the virtual machine. By contrast, if a virtual machine already has more than 128 virtual CPUs, you can use hot adding to further increase the number of virtual CPUs to up to 256. When I read this for the first time, words "further increase" and "beyond that limit" means that if a VM has CPUs less than 128 and I need to increase CPUs over 128; this requires VM to be powered off. If you want to increase CPU to a number below 128 and if hot add is already enabled, VM does not require to be powered off. Now if a VM already has 128 CPU and is powered ON, there is no problem with further increasing CPU.
Hi, I just heard back from VMware Support that they have finally published KB for this issue. Windows 2016 Server loses its network card after a reboot with autoupdate of tools enabled (71... See more...
Hi, I just heard back from VMware Support that they have finally published KB for this issue. Windows 2016 Server loses its network card after a reboot with autoupdate of tools enabled (71386) What I would suggest is: 1. Disable VMware Tools autoupgrade for Windows 2016 VMs in vCenter. 2. Let the Windows update finish all patch installation including patches for September 2019. 3. Enable the VMware Tools autoupgrade for Windows 2016 VMs again in vCenter. 4. Monitor and repeat 1 to 3 if you face same issue again.
Hi, Welcome to VMTN. Normally, you should be able to add. If there are cluster settings which would require you to change something on ESXi or VMs, you will get error prompt with the inf... See more...
Hi, Welcome to VMTN. Normally, you should be able to add. If there are cluster settings which would require you to change something on ESXi or VMs, you will get error prompt with the information. In any case, there should be no impact to currently running VMs. Go on and let us know what happens. --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.
Hi, Distributed switch requires Enterprise Plus license. Refer to below vSphere licensing and pricing white paper. VMware vSphere Compute Virtualization Licensing, Pricing, and Packaging Wh... See more...
Hi, Distributed switch requires Enterprise Plus license. Refer to below vSphere licensing and pricing white paper. VMware vSphere Compute Virtualization Licensing, Pricing, and Packaging White Paper
You can double check with network person if they are able to see the MAC on their network devices connected with these ESXi hosts. Also, check with backup guys if they have configured this datas... See more...
You can double check with network person if they are able to see the MAC on their network devices connected with these ESXi hosts. Also, check with backup guys if they have configured this datastore in their system and get it removed and then try again. Same goes for any 3rd party application configured to work with vCenter in your environment, if any.
The first link mentions about same if you scroll to bottom. When you boot a server with this USB Flash Drive the ESXi Installer will copy the whole installer to the memory which means that yo... See more...
The first link mentions about same if you scroll to bottom. When you boot a server with this USB Flash Drive the ESXi Installer will copy the whole installer to the memory which means that you can install ESXi to the device where you are installing from. Just select it during the installation. This also works for diskless ESXi hosts where you want to install ESXi to an SD Card. Create a Bootable ESXi Installer USB Flash Drive
Hi, Welcome to VMTN. Going forward, please post in English after translation so we can help in best way. For now, I have translated your question to English as below. Correct me if I'... See more...
Hi, Welcome to VMTN. Going forward, please post in English after translation so we can help in best way. For now, I have translated your question to English as below. Correct me if I'm wrong or misunderstood your question. Question: Can the 6.5 version of the ESXi host be configured with the 6.7 version of the esxi host vsphereHA, can the vmotion function be used normally? Answer: You can keep both 6.5 and 6.7 hosts in a single vSphere cluster with HA, DRS enabled. You have to make sure below prerequisites are met: 1. Hardware, specifically CPU of hosts should be of same family. 2. Configure EVC on same hardware (CPU) level. 3. VM hardware version available for 6.5 is 13 and for 6.7, it is 14. Make sure all VMs stay at hardware version below 13 because VMs with hardware version over 13 (14) will not run on 6.5 hosts. Not a prerequisite but a concern, ESXi 6.5 and 6.7 ship with different VMware Tools version and although there would be no impact on VMs' performance with different VMware Tools version running on the hosts but it is nice to have uniform VMware Tools version on all VMs. VMware Tools version is not dependent on ESXi version to work. Let me know if you have more query on this.
Hi, Welcome to VMTN. You require shared storage to proceed further. Listing below few FT articles for vSphere 6.7 for your reference. You can also check more FT documentation through lin... See more...
Hi, Welcome to VMTN. You require shared storage to proceed further. Listing below few FT articles for vSphere 6.7 for your reference. You can also check more FT documentation through links on same article pages. Best Practices for Fault Tolerance Virtual machine files (except for the VMDK files) must be stored on shared storage. Acceptable shared storage solutions include Fibre Channel, (hardware and software) iSCSI, vSAN, NFS, and NAS. Fault Tolerance Checklist