nparas5's Posts

Hello Senthil, OVF deployment is the feature provided by vCenter itself, don't think it is possible without vCenter.  You will not see any option to deploy OVF when connected to  individual ESXi host  via web client . I have checked this on 6.5 and 6.7 .

Hello There, Sol-1: Have you tried powering off VM and then v2v ? Please power off the VM and then try the same task. Also you can analyze logs under below path on machine where you have installed VM Converter for clarity of errors. C:\ProgramData\VMware\VMware vCenter Converter Standalone\logs\ Sol-2: If its a Windows VM try disabling Firewall from inside windows OS. Sol-3: The account which you are using for v2v must have administrative privileges on the VM which you are trying to convert. Although Lowering down H/W Version is not recommended, but you can do it by v2v as you are doing it. For first you can try v2v after powering off your VM.

Hello There, These Memory errors are Hardware issues, sometime these can resolve by reseating the Bad DIMM(RAM) to the same slot. Sometimes changing the slot (In HPE servers there is a sequence of inserting DIMM to DIMM Slots according to Processors A and B) For resolution you must need to log case with vendor either the DIMM is faulty so it will re-appear after changing the slot as well, so they have to replace this bad DIMM. Either theycan ask you to upgrade your BIOS or Firmware depending on your hardware. Check how much RAM is there on your physcial server and how much is the ESXi host able to detect? If its low then DIMM is faulty. And RAM is showing correct then check with your hardware vendor . And if you are proficient in Hardware and know the RAM slot sequence you can either try re-seating the DIMM to other or same slot. NOTE: Before doing this make sure there are no VMs on host and it must be in maintenance mode.

Hello There, Mostly PSODs are due to hardware issues or Bugs in BIOS , Firmware, Drivers. If you have the warranty with HPE for your physical server just log the case with vendor and share them the AHS logs from iLO. Refer below VMware KB hope it can help you understand the error in the PSOD stack: VMware Knowledge Base ESXi/ESX hosts are unstable and may fail with a purple diagnostic screens citing an NMI, Non-Maskable, or LINT1 Interrupt. The console displays an entry similar to: LINT1/NMI (motherboard nonmaskable interrupt), undiagnosed. This may be a hardware problem; please contact your hardware vendor. You may experience a purple screen when passing through a device to a virtual machine and when reviewing the vmkernel core dump, you see these events: WARNING: IOMMUIntel: 2211: IOMMU Unit # 0: R/W = 1, Device 007:00.0 Faulting PA = 0xdf63e000 Fault Reason = 6 Note: NMI log entries appear in the /var/log/vmkernel.log file, on the console, or in the VMkernel core dump file if the condition triggers a VMkernel purple diagnostic screen.

Hello There, DRS is designed to do the same way, it will auto balance your cluster and keep vmotion VMs w.r.t to the migration Threshold. Make sure to check Migration Threshold is not aggressive. If you want to keep the VM in same host and don't want it to migrate, simply use Affinity Rules for it, so that particular VM will stick to that particular host.

Hello There, You can install from VC directly without ny special procedure its normal for all w.r.t to esxi host running. Just go to in Center Server, right-click a virtual machine, click Install/Upgrade VMware Tools. There is no special procedure for any windows servers running on different roles. If you want to supress reboot and install vmtools, just select "Advanced Upgrade" options and paste the below command: /S /v"/qn REBOOT=R"

Hello There, Lets get to ESXTOP to understand disk performance metrics, not getting into brief but a small overview of it: Below are 2 main counters of Storage performance which can be viwed with the help of esxtop: DAVG: Indicates the latency at device driver end, it’s basically the time taken by I/O request to HBA driver from storage driver. It is the good indicator of performance of backend storage. Min Latency should be 25 or lower than it, of its higher than 25 then the latency is caused by your storage array, FC Switch misconfiguration or faults. DAVG is not disk utilized by your VMs, infact disk performance varies from OS to OS in windows you can try using perfmon\Physical Disk counters to monitor disk performance. In your case i think its normal . KAVG: Min threshold value of this counter should be between 0-2, if it’s higher than 2 it indicates the disk I/O latency from host kernel storage stack. Disk I/Os could be queued at kernel level if it’s high. This can seriousy impact your VMs performance.

Not Sure why you want to disable but this should never be an option rather than a workaround. How would you power on a host physically assume after power outage at DCs? Power Button is required many times to hard reset host when its hung from GUI and SSH, Power Button is required when you perform hardware troubleshooting/installation. From Data center perspective this question is not possible not because H/W vendors can't do it but this is an important requirement . For security point of view that's why Data Centers are secured and isolated places where servers are kept in locked racks..

Hello There, First test the Network Settings from the Host console itself, if they are able to resolve Gateway/DNS etc or not. Also check hostd, vpxa, logs etc for the error/warning events. Also from the console please check if you are able to see uplink adaptors/NICs, sometimes there are hardware driver compatibilities with newer version of esxi.

Hello Michael, Good Day! What hardware are you using for the asked ESXi 4.0? It seems to be related to HBA adaptor driver as well. If any hardware upgrade (Drivers\BIOS\Firmware) is available please upgrade. Parallely you can check with your storage team if they are seeing any disconnects from Fibre Switch end or not. If they are all clear then the maim culprit is your HBA drivers.

Hello There, Just log a case with your hardware vendor HP, for this alert. They must have some upgrades like BIOS/Firmware for this. Mostly Both Vendors (Vmwar/HP) will ask you to upgrade to latest whether patches or firmware upgrades. You will definitely get solution from them only. First try with HPE.

Orphaned delta files can cause serious performance issues. These files still remains after the snapshot deleted/removed. These are also represented by Zombie Files. You need to use the PowerCLI script to get the list of Orphaned VMDKs. You can cross check and then try deleting them. Refer Below Link: Finding orphaned VMDK’s using PowerCLI | vmware admins I have also used this script in my past experience, you can test and then try using this.

Hello There, You can look for OVF Template option. Verify that the virtual machine is powered off. Steps: Select the virtual machine and select File > Export to OVF. Enter a name for the OVF file and specify a directory in which to save it. Specify whether to export the virtual machine as an OVF, a folder with separate files, or as an OVA, a single-file archive. Click Export to start the OVF export process. Similarly you can select Import option and deploy the OVA file. NOTE: I think you must need vCenter to do this OVF Deploy operation. From Standalone ESXi you can't import /deploy the OVA/OVF Files.

Hello , It seems your Server is crashed with Bug check BSOD. You need to analyse the Memory Dump created under "C:\Windows\System32" with the use of WinDBG Tool. It will give you exact details of Bugcheck. You can also analyse MiniDump "C:\Windows\System32\MiniDump" it will only give you the details of the driver casued Bugcheck. Moreove BugChecks are caused by Third Party drivers/softwares/ Only thing can help you solve this is you need to analyse the Memory.dmp file with the help of WinDBG Tool. Refer this link to analyse the Memory Dump: Step by Step tutorial to debugging memory dump caused by Blue Screen of Death by WinDbg – MyTechTweaks

See if you are able to see the specific VM with this command: vim-cmd vmsvc/getallvms If you are able to see that specific VM, that must be having some numeric ID. Get the status of VM is its Power ON or not: vim-cmd vmsvc/power.getstate vmid If its on please power off with below command: vim-cmd vmsvc/power.off vmid Use restart if you need to restart in place of power.off ××××××××××××××××××××××××××××××××××××××××××××××× And if you want to remove this VM permanently, please run below commands as well: First of all Unregister the VM using VIM command: vim-cmd vmsvc/unregister vmid Then Delete the VM using destroy command: vim-cmd vmsvc/destroy vmid. Hope that will help

Anyhow it will destroy previous installation when you try to boot from USB, its still the same thing same as to installing a new ESXi. Refer below article you can anytime revert back the ESXi to previous version: Reverting to a previous version of ESXi (1033604) | VMware KB

Join Computer to Domain with Desired Computer Name and OU - PowerShell Blogger https://support.microsoft.com/en-in/help/315273/automating-the-creation-of-computer-accounts Check Above Scripts for the same, you can only do this by Powershell Scripting. NOTE: Its related to Windows/Active Directory not with VMware,

If its problem in single machine please try to un-install the same in "Safe-Mode", windows Installer will not run in safe mode so you need to create one registry key from command line and then run the net start command to start the service, below are the steps: Reboot machine , press F8 and go to safe mode. Open Command Prompt and run below: REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\MSIServer" /VE /T REG_SZ /F /D "Service Start the service by: net start msiserver Go to add remove programs and uninstall. Hope this works. NOTE: You might need check the processes running from "iexplore" first in task manager, if they are try killing them and if not proceed to uninstall the same by Safe Mode.