Comments on: Upgrade to vSphere ESXi 6 via command line

By: Heaven

Heaven — Sat, 24 Dec 2016 23:41:00 +0000

In reply to Mostafa Khaiil. That's really thninikg at a high level

By: magander3

magander3 — Tue, 28 Jul 2015 18:24:59 +0000

Hi Mostafa,
thanks for your comments. I added a section below the commands that states e.g. “Important: Make sure to use two minus – – signs before depot”. I also added a comment about using a shared datastore instead of the local one i used “When upgrading multiple ESXi hosts you should use a shared datastore but i didn’t have one available for my single ESXi mgmt host”. Reason for a local datastore in my case was that i didn’t have any shared storage, this was a single mgmt ESXi host.

Thanks
//Magnus

By: Mostafa Khaiil

Mostafa Khaiil — Tue, 28 Jul 2015 18:05:33 +0000

Hi Magnus,
Please change the “long hyphen” to 2 short one in the “–depot” and “–profile” options. Most editors automatically convert 2 hyphens to a long dash.

Alternatively, you may use the short-hand options without the “=” e.g. -d and -p
e.g., to list profile in depot:
esxcli software sources profile list -d /vmfs/volumes/54aeddbd-e5943701-1cf2-f8db88fbd420/VMware-ESXi-6.0.0-2494585-depot.zip

and to upgrade:

esxcli software profile update -d /vmfs/volumes/54aeddbd-e5943701-1cf2-f8db88fbd420/VMware-ESXi-6.0.0-2494585-depot.zip -p ESXi-6.0.0-2494585-standard

I would also suggest using a datastore shared by all ESXi hosts you plan to upgrade. This will save time and disk space. If no such a shared datastore exists, you may host the depot on an internal web site and use the the zip file’s URL with the -d option.