Backup An ESXi Host's Config Using vCLI
Assuming you are already connected to your VI server using vCLI...
$ehost = Get-VMHost host
Get-VMHostFirmware $ehost -BackupConfiguration -DestinationPath your backup path
Full PowerCLI documentation here.
seen from China

seen from United States

seen from Malaysia
seen from China
seen from Egypt

seen from Malaysia
seen from United States

seen from Germany

seen from Singapore

seen from Jordan
seen from Jordan

seen from China

seen from United States
seen from Türkiye

seen from United States

seen from Germany

seen from United States

seen from Malaysia
seen from United States
seen from United States
Backup An ESXi Host's Config Using vCLI
Assuming you are already connected to your VI server using vCLI...
$ehost = Get-VMHost host
Get-VMHostFirmware $ehost -BackupConfiguration -DestinationPath your backup path
Full PowerCLI documentation here.
#PowerCLI 5.0.1 Release - Install and Notes
It's a happy day in the PowerCLI world. VMware released their latest update, 5.0.1. This release finally brings to light the vCloud Director cmdlets that many of us have been waiting for so patiently. Luc Dekens has put together a great rundown of the new features on his blog at http://www.lucd.info/2012/01/10/powercli-5-0-1-goes-cloud/ so I'll try not to overlap. Also check out Jake Robinson's post at http://geekafterfive.com/2012/01/09/powercli-in-the-cloud/. In line with my post for the last release here are some install screenshots. I left out some of the common Next Next's. Want the vCloud Director cmdlets? Better pay attention when doing the install. Check it out below. Download the latest code to local disk from http://communities.vmware.com/community/vmtn/server/vsphere/automationtools/powercli Make sure you close any IDEs like ISE, PowerGUI, etc. as well as any PowerShell or PowerCLI sessions you have open. This should eliminate any need to reboot. Launch the installer. Note the new build version 5.0.1.4431. Get your Next on
HALT! I was a little surprised that the vCloud Director portion was not set to install by default. It makes sense however since not everyone using 5.0.1 will need vCD cmdlets. That being said, make sure you update this if you wish to install this snap-in. Back to the Nexts
Naturally it will remove the previous version and install the new. This install appeared to be more time consuming than previous installs. My guess is that this is a result of having 2 snap-ins being installed rather than one. Once complete I launched PowerCLI and checked my version with Get-PowerCLIVersion. This cmdlet will give you the build number of both PowerCLI and all of the Snap-ins. Extremely helpful if you're having issues and look for help in the release notes or the community forums.
Make sure you look at the release notes and get a feel for the new features and limitations. Also make sure you check out Luc's post. http://www.vmware.com/support/developer/PowerCLI/PowerCLI501/powercli501-581491-releasenotes.html#whatsnew Links
http://communities.vmware.com/community/vmtn/server/vsphere/automationtools/powercli
http://www.vmware.com/downloads/download.do?downloadGroup=PCLI501
http://www.lucd.info/2012/01/10/powercli-5-0-1-goes-cloud/ - Luc Dekens
http://geekafterfive.com/2012/01/09/powercli-in-the-cloud/ - Jake Robinson
http://www.vmware.com/support/developer/PowerCLI/PowerCLI501/powercli501-581491-releasenotes.html#whatsnew
#PowerCLI 5 Upgrade Procedure in Pictures
I recently updated my laptop to PowerCLI 5, even if it was about 4 weeks later than I should have. :) I figured since I was doing it I'd put down the instructions in screenshots. Since not everyone needs to see the simple upgrade installation I'll go ahead and point out some of the good bits. DOWNLOAD
Installation is definitely a click through
If you have PowerGUI or a PowerCLI session open you will have to close them to complete the upgrade.
PowerGUI has seemed to take a bit longer to load the VMware snap-in but after about 20 seconds it did start recognizing and auto-completing PowerCLI cmdlets.
Check your installed version by typing Get-PowerCLIVersion into the PowerCLI console.
Ok, now for the pictures. It's straight forward but I'm sure someone will be glad to have them. Enjoy!
Once installation is complete, load PowerCLI 5 and run Get-PowerCLIVersion.
If you're a PowerGui 3 user you'll be happy to see all the new cmdlets available. Enjoy!