SupreetK's Accepted Solutions

Yes, it is a free tool. Can be downloaded from the below link and a link to the user's guide. You will find many blogs on the net explaining the conversion process step-by-step - Download Center for VMware Products https://docs.vmware.com/en/vCenter-Converter-Standalone/6.2/convsa_62_guide.pdf Cheers, Supreet

While you are on the CPU tab, press f to check if %RDY is selected to show. By default, it will be the next column to %VMWAIT. Looks like your putty screen is too small or the fonts size is too big. Hence, you are not able to see the next columns. F should be selected for the %CPU State times to show up in the CPU page. Alternatively, you can use VisualESXTOP which provides a better viewing experience in case you are not a big fan of the command line - VisualEsxtop Cheers, Supreet

If it is a planned activity such as any hardware replacement, ESXi patch upgrade, etc, the VMs have to be migrated to the other host and the host has to be placed into maintenance mode before the reboot. If the DRS is set to Fully Automated, placing the host into maintenance mode will automatically migrate the VMs to other host(s). This is particularly useful when there is a large cluster and we don't want to worry about distributing the load across the remaining hosts. Cheers, Supreet

AFAIK, there is only one way to achieve this. Create two folders under the datacenter - 'Alarm-Required-VMs' and 'Alarm-NotRequired-VMs'. Place the required VMs accordingly in these folders, disable the alarm at the vCenter level (or at the datacenter level - wherever it has been configured currently) and enable the alarms only for the folder 'Alarm-Required-VMs'. As you would know already, you can also disable all the alarms for a specific object such as a VM. However, this will disable all the alarms and there is no option to disable a specific alarm. Cheers, Supreet

PowerCLI cmdlet “Update-VmfsDatastore” deletes the existing VMFS-5 datastore to create a VMFS-6 datastore. More details in the below link - Online Documentation - Cmdlet Reference - VMware {code} Cheers, Supreet

Can you refer to the below link and check what is the status of CBT (true or false) and the value of 'Change ID' in the MOB page for the VM in question? Backup and Change Rate, Part 2: Querying Change Rate - Veeam Hub​ Cheers, Supreet

1) VM hardware version 4 and above is supported with ESXi 6.5. 2) Ensure no VMs are running on snapshots before backing them up with Veeam. 3) If the existing datastore version is VMFS-5, create the same version on ESXi 6.5 as well. 4) Same network portgroups need to be created on the new servers. 5) If you want to move them live between 5.5 and 6.5, ensure EVC is enabled in case the CPU series is different. Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered. Cheers, Supreet

As cliched as it may sound, you might raise a feature request - Contact VMware​. If there are considerable number of requests, VMware might bring it back The chances of it look very slim though :smileyplain: :smileyplain: Cheers, Supreet

Check the below link to know how to add multiple IQNs (or IP addresses) in the existing storage target - vGeek: Configuring Microsoft iSCSI Target datastore on Esxi server and multipathing Step by Step Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered. Cheers, Supreet

Abstract from the below document - 'Do not encrypt any vCenter Server Appliance virtual machines' --> Virtual Machine Encryption Best Practices​ Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered. Cheers, Supreet

None of the versions of the driver 'mpt3sas' support the 'Second Level LUN ID' feature. You can avoid these warming messages by not presenting any LUN having LUN ID greater than 255, via this controller. You can use software LUN masking on the ESXi to prevent the ESXi from seeing any LUNs above LUN ID 255. However, this is not recommended. Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered. Cheers, Supreet

As I thought, WINSvr-flat.vmdk seems to be missing. Since it is a data disk (and not the descriptor), it cannot be recreated. Only option would be to restore it from the backup, if any. If WINSvr16 is the new VM you are talking about, I would say let's go ahead and get it up. Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered. Cheers, Supreet

Please follow the below steps and check if it works - 1) Upgrade the ixgbe driver to the version 4.5.3 - Download VMware vSphere​ 2) Run the below commands to disable the native driver module and enable the async module - <esxcli system module set --enabled=false --module=ixgben> <esxcli system module set --enabled=true --module=ixgbe> (or) <esxcli system module set --enabled=true --module=net-ixgbe> 3) Reboot the host Please consider marking this answer as "correct" or "helpful" if you think your questions have been answered. Cheers, Supreet