Plain Virtualization

Recently, got to know from a customer who have a vCenter Server Appliance 6.7 that went down after a reboot. The services refused to come up. Looking at the error generated, it looks something similar to this KB . However, this was the the similar Error RC code which returns 1 instead of 11. So we went asked the customer what actually happens and the results was they change a new DNS server with new IP but did not update vCenter Server. This is a big impact! Why is this so? If you have deploy a vCenter Server, the requirement for forward and reverse DNS is required as a prerequisites else the vCenter Server Installation wizard will not proceed further. So while the vCenter Sever is still running without been updated on the new DNS, services on the vCenter start to act abnormally. A reboot will completely bring it down as nothing will start without DNS. The only service that will start is the vSphere Client service. There are few ways to change your DNS which I am going to lis...

I used to perform upgrade easily for vCenter on Windows.  That been said, with the introduction of vCenter Server Appliance (VCSA), it has also been easy as well using the admin portal via https:// :port 5480 with the .pak file. Wasn't was I aware after doing some research to find out VCSA in version 6.0 does not have admin portal to do the upgrade.  Instead I need to upload the update file from  here  (you got to login to your account). I followed this  guide  from this user. Apparently after upgrade form baseline 6.0, the admin portal for the appliance is been returned.  Glad that is an one time experience. Why was the admin 5480 been left out in the first place?