Wu's Blog

You may see following error when you scanning ESXi hosts by vCenter Update Manager. Host cannot download files from VMware vSphere Update Manager patch store. Check the network connectivity and firewall setup, and check esxupdate logs for details. You also see similar logs in /var/log/esxupdate.log. [Errno -2] Name or service not known The root cause could be following: ESXi host cannot resolve DNS name of vCenter Update Manager Server. One of the DNS servers incorrect if you set multiple DNS servers on ESXi host.

Virtual appliance is future of how VMware delivery their product to customers. It's pain to migrate from vCenter Server Windows version to virtual appliance. The only way was build up new virtual appliance and move everything out of Windows vCenter Server. The challenge is you lost data if you have integrated vCenter Server with other VMware products, or using DVS. VMware released vCenter Server Migration Tool after VMworld 2016. It gave me confidence to give it a try. I assume vCenter Server is embedded SSO. I did the migration 2 or 3 times, following is summary of my experience. The migration tool only support migrate vCenter Server 5.5 windows edition to vCenter Server 6.0 U2. Prerequisites vCenter Server is more like core services today since lot of 3rd party software call vCenter API to interactive with VMs. You may have some products integrated with vCenter Server already. Please upgrade to vCenter 6 compatible version before migration. I suggest create a local account

I wrote an article to introducing how to integrate PowerCLI with PowerShell and PowerShell ISE . VMware just released PowerCLI 6.5 R1, it includes lot  of new features and modules. And somehow my way doesn't work. Following is new way to integrate PowerCLI 6.5 with PowerShell and PowerShell ISE in Windows 10. PowerShell and PowerShell ISE both have it own $profile. So we need to do two times. Before we start Please make sure your PowerShell execution policy is not  restricted . You can get the setting by run  following command: Get-ExecutionPolicy PowerShell Integration Open PowerShell window. Run following command to confirm profile file is not existing. Test-Path $profile If return is 'False', go to step 2. If return is 'True', Backup the file and go to step 3. Run following command if the  profile file  doesn't existing. New-Item -Path $profile -type file -force | Out-Null Test-Path $profile The return above should be 'True'. Profile file is crea