Had a customer using hostname in mounting NFS and i wanted to test if DNS was a dependency for this kind of setup. Removed the DNS and..*poof* NFS mount is still alive and kicking. Apprently, ESXi caches the IP it resolves. Good news for people using NFS and mounted it using hostname Here’s a KB on how to clear the internal cache: https://kb.vmware.com/kb/2117593
Didn’t realize there was an “easy” go-to button in vRealize Orchetrator to auto-configure the following: Import license Import certificated Configure SSO Configure vCenter Server Plugin Just login to vRealize Orchestrator Configuration and setup the component manager lookup – VMware vRealize Orchestrator Configuration -> General -> vSphere Configuration
Ok. For people who keep getting this when installing additional PSCs: Unfortunately, the logs that get’s dump in your local PC (where you initiate the installation) doesn’t provide enough information for you to troubleshoot this. The correct logs to look for would be inside the PSC appliance that gets deployed. SSH to the failed PSC installation Go to the following path: /var/log/firstboot Look in