Category: VMware Issue

Dear all Issue Had some Issues with a customer connecting to an old (5.x) Horizon View environment with my 4.10 Agent (MAC). Client connects but immediately after connecting I got a black screen and a disconnection message. Resolution This is because of a change / disable TLS 1.0 version. So just use the 4.9 client or tell your customer to update 🙂 Download You can download it here: https://my.vmware.com/web/vmware/details?downloadGroup=CART19FQ3_WIN_490&productId=578&rPId=25728 Regards and Happy New Year!

Dear all Issue Today a customer called and told me, that he had some issues with access to vCenter from certain networks. After some research we found a wrong (old) default gateway enty in the vCenter. As it was VCSA 6.0 we had no VAMI at this time. So we used the console, but the menu for changing the gateway did not shown up. Access through shell and fireing up the vami in console with:

1

/opt/vmware/share/vami/vami_config_net

gave us a lot of errors. Solution Solution was to change the gatewy with the following line

Dear VMware User Today a customer called me and showed me following error (Veeam & VMware logs): Error A general system error occurred: Failed to write header to “/var/log/vmware/journal/1487689997.1: Error while writing to file. There is no space left on the device Reservation destination directory Solution Solution was to move the logs away from the scratch partition (in our case a 4 GB SD card) to a persistent scratch location (i.e. a VMware datastore) More information on the VMware KB site: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003322

Today I did an ESXi update on some HPE DL380 Gen9 servers for a customer. I attached the ISO and rebooted the first host as always. But during the update process no disks was shown to update / install the ESXi host. Resolution: The issue was, that I should take the HPE Custom ESXi ISO. Download: https://my.vmware.com/group/vmware/details?downloadGroup=OEM-ESXI60U2-HPE&productId=491 (Google for other vendors) Reboot again with the right ISO and I could start the update. Hope it helps some others out there.