Guest OS Customization for Ubuntu 18.04 Server LiveCD will fail due to conflict between cloud-init and VMware guest OS customization or systemd services execution sequence on booting virtual machine. Follow below workaround on VMware vSphere ESXi 6.5 to set cloud-init or perl scripts as the customization engine when customize guestOS for Ubuntu 18.04 Server LiveCD. Continue reading “[Solved] Guest OS Customization will fail for Ubuntu 18.04 Server LiveCD”
Pool provisioning operations are not initiated after doing view upgrade for VMware Horizon 7 version 7.5.x due to the stale jars left behind after upgrade. We see the error messages Pool Info currently inconsistent, skipping determineActions for pool in CS logs at C:\ProgramData\VMware\VDM\logs. Execute below steps on the brokers one at a time and repeat the steps for the other brokers in the cluster. Continue reading “[Solved] Pool provisioning fails after upgrade VMware Horizon 7 version 7.5.x”
ESX Agent Manager (EAM) Service fails to start after VMware vCenter Server Appliance (VCSA) reboot or recovering from 100% storage utilization issue.
EAM MOB web interface unable to access as well. Before EAM starts, eam.properties file is getting updated using cis.utils.replace_properties_in_file. This rewrites the eam.properties file which causes a loss of the data inside the file or eam.properties getting removed during start of the EAM service in an environment without any disk space.
Follow below steps to recover EAM service on VCSA 6.0 by manually replacing eam.properties file.
Problem: VMware announced potential in-guest data inconsistency issue happen at virtual machine disks (VMDKs) that has been extended while running on VMware vSAN 6.6, 6.7 and later storage which ships with ESXi 6.5.0d and later including vSAN 6.6 (vSphere 6.5 EP2), vSAN 6.6.1 (vSphere 6.5U1), vSAN 6.6.1U2 (vSphere 6.5U2) and vSAN 6.7.
Problem: Windows System Error Event 7011, Service control manager “A timeout (30000 milisecond) was reached while waiting for a transaction response from the VMtools service.” This timeout event error only happen on windows VM with 8.6.5 version of VMWare tools. Basically this is not an application or service specific but a generic windows error and it can occur with other services too.