pragg12's Posts

Hi, I have tried it with ESXi 7.0 (not U1). Only issue I have faced is that is if you try to link ESXi hosts as source and destination directly rather than VCSA, Converter gives error that host is m... See more...
Hi, I have tried it with ESXi 7.0 (not U1). Only issue I have faced is that is if you try to link ESXi hosts as source and destination directly rather than VCSA, Converter gives error that host is managed by VCSA. In that case you have to connect Converter to VCSAs to initiate migration. Or if you can disconnect hosts from VCSA and then try, it will work fine then.
Hi @a_p_ @jobee1  I could not find any documentation either. Hence, when faced with similar issue, I reached out to our VMware account support team and got this information. However, at that time VC... See more...
Hi @a_p_ @jobee1  I could not find any documentation either. Hence, when faced with similar issue, I reached out to our VMware account support team and got this information. However, at that time VCSA was on 6.7 and keys were for ESXi 7, I had to downgrade keys to be used on ESXi 6.7. I did a test run just now and it is not possible what I mentioned. I will retract my above comment. 
[Retracted due to incorrect information]
Glad to know CLI method worked for you.  For GUI, I suspect that it is something to do with update config file. Try steps in link below. If this doesn't work, I recommend raising case with VMware su... See more...
Glad to know CLI method worked for you.  For GUI, I suspect that it is something to do with update config file. Try steps in link below. If this doesn't work, I recommend raising case with VMware support for speedy resolution. How to workaround "Update installation failed. vCenter Server is non-operational." message during VCSA 7.0 update | TinkerTry IT @ Home
Hi, I have tried it with ESXi 7.0 (not U1). Only issue I have faced is that is if you try to link ESXi hosts as source and destination directly rather than VCSA, Converter gives error that host is m... See more...
Hi, I have tried it with ESXi 7.0 (not U1). Only issue I have faced is that is if you try to link ESXi hosts as source and destination directly rather than VCSA, Converter gives error that host is managed by VCSA. In that case you have to connect Converter to VCSAs to initiate migration. Or if you can disconnect hosts from VCSA and then try, it will work fine then.
Hi, How are you trying to install VIB on ESXi host ? If you are doing it through CLI on host, I suggest deploying it through vCLM: 1. Import the VIB in vCLM. 2. Create an extension with the import... See more...
Hi, How are you trying to install VIB on ESXi host ? If you are doing it through CLI on host, I suggest deploying it through vCLM: 1. Import the VIB in vCLM. 2. Create an extension with the imported VIB. 3. Attach it on host. 4. Remediate host with extension.  
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)
It's no bug but functionality. You can keep the log files as it is and there's no harm in that. You can also limit the log files per your requirement using the setting "vmx.log.keepOld" posted by... See more...
It's no bug but functionality. You can keep the log files as it is and there's no harm in that. You can also limit the log files per your requirement using the setting "vmx.log.keepOld" posted by T180985​. Detailed article for same below: Limit the Number of Log Files in the vSphere Web Client
Do make a cold copy on the VM before attempting any operations. I would recommend doing this on another datastore to avoid confusion. Use incognito mode of the web browser of your choice. Once... See more...
Do make a cold copy on the VM before attempting any operations. I would recommend doing this on another datastore to avoid confusion. Use incognito mode of the web browser of your choice. Once you have a cold clone of the VM, try increasing size. If it gives error, un-register the VM. Then register the VM. And try increasing the size again.
There are 2 ways: 1. Open putty and run any of below commands and see what you need: esxcfg-scsidevs -l esxcfg-scsidevs -l | egrep -i 'display name' 2. Open web client connection directly... See more...
There are 2 ways: 1. Open putty and run any of below commands and see what you need: esxcfg-scsidevs -l esxcfg-scsidevs -l | egrep -i 'display name' 2. Open web client connection directly to ESXi host. Select "Storage" under Navigator panel. ESXi will then open "Datastores" panel on right. Open Devices tab. The serial number should be located at the end, after the device's model number.
Keep us posted on what happens. I have few questions. 1. What are your observations on this ? 2. Do you see a common pattern like this issue happening for a single VLAN or a particular group of... See more...
Keep us posted on what happens. I have few questions. 1. What are your observations on this ? 2. Do you see a common pattern like this issue happening for a single VLAN or a particular group of VLANs or occurrence/re-occurrence of issue on new/current VM ? 3. Is the network infrastructure new or old ? In case of new, do verify that network settings are configured correctly. 4. If using dvswitch, verify that you use optimal port group load balancing option per discussion with Network team. 5. Verify if all VLANs are trunked on all NICs of ESXi host which are in vswitch/dvswitch. Any configuration issue in above may be the cause of your issue.
Hi, So if you are deploying the appliance in an already configured DRS and HA enabled cluster, no further configuration would be required from VMware level.
Hi, Have you tried this: Add USB Devices from an ESXi Host to a Virtual Machine
VMware decided to separate the release cycle of VMware Tools from vSphere because if there's a bug in VMware Tools, you would have to wait for a new version of vSphere before. Now, VMware release... See more...
VMware decided to separate the release cycle of VMware Tools from vSphere because if there's a bug in VMware Tools, you would have to wait for a new version of vSphere before. Now, VMware releases new version of VMware Tools and they are compatible with ESXi. Updates to VM Compatibility and VMware Tools with vSphere 6.7 Update 2
Hi, Welcome to VMTN. Can you test with VMware Tools 11.0.1 on a fresh, vanilla install of Windows Server 2019 through ISO and share your findings ? Also, which version of 2019 are you us... See more...
Hi, Welcome to VMTN. Can you test with VMware Tools 11.0.1 on a fresh, vanilla install of Windows Server 2019 through ISO and share your findings ? Also, which version of 2019 are you using ? https://my.vmware.com/group/vmware/details?downloadGroup=VMTOOLS1101&productId=614
Hi, Why are you not going for direct upgrade of ESXi to 6.5 instead of current version -> 6.0 -> 6.5 ? Since you are ESXi upgrade in latter way, you will have to upgrade VM hardware version u... See more...
Hi, Why are you not going for direct upgrade of ESXi to 6.5 instead of current version -> 6.0 -> 6.5 ? Since you are ESXi upgrade in latter way, you will have to upgrade VM hardware version upgrade in same way as well. Like this: Current version -> 11 -> 13. So double downtime per VM. Also, what NIC are the VMs using ? VMXNet should be there instead of E1000 unless there's a particular reason. What are your observations on the VMs which are facing the issue ? Any common pattern you observed; like same OS, or NIC or host or cluster ?
Hi, Here's your options if I am getting it right. 1. Your VM in source 6.7 vCenter should have hardware version below 11 to make this migration work since ESXi in vCenter 6.0 will support h... See more...
Hi, Here's your options if I am getting it right. 1. Your VM in source 6.7 vCenter should have hardware version below 11 to make this migration work since ESXi in vCenter 6.0 will support hardware version 11 VMs only. 2. Try OVFtool. 3. If your destination VC is 6.0 U3, try VMware fling: Cross vCenter Workload Migration Utility | VMware Flings 4. Use vCenter Converter if your VM hardware version is above 11. 5. Make a cold clone of VM in source 6.7 vCenter then downgrade VM hardware version to 11 before exporting. You can find guide online for same.
Hi, Are you using VM based replication or storage array based replication ? I don't know if SRM works in same site but I would suggest to raise case with VMware support if this is critical.
Hi, If everything fails, you can try creating a new blank VM and attach the disks from old VM and then you should not face this issue.
Hi, Have you tried deploying OVF directly through ESXi, not through vCenter ? Sometimes, it works so would recommend if not already tried.