ESXi 4.1: setting license via command line

Setting the license at the command line is done with the following command:

vim-cmd vimsvc/license

If you run it you’ll see that one of the options is to –set=string.
But if you run it like this:

vim-cmd vimsvc/license --set=XXXXX-XXXXX-XXXXX-XXXXX-XXX11

You will get an error.

The right way to do it is:

vim-cmd vimsvc/license --set XXXXX-XXXXX-XXXXX-XXXXX-XXX11

Notice there is no ‘=’. I would ask that someone please update the help message here.

You can run it again with the –show option and you’ll see your license has been accepted :-)

  • ebob9

    Does this not work for hosts attached to a vCenter server?

    I tried to use this to swap out a license on an ESXi host. The command was accepted, and /etc/vmware/vmware.lic was updated, and the new license shows in a vim-cmd vimsvc/license –show command.

    However, if I connect to the host with a vSphere Client, I still get the old license in the Configuration -> Licensing window. Does another change need to happen somewhere else to update the vCenter client? and any idea if that can be done from the ESX cli?

    The vSphere display looks to be purely cosmetic – I switched it back to “Evaluation” mode, and got the popup that the license would expire in 60 days. However, vim-cmd vimsvc/license –show still showed the appropriate “Enterprise Plus” license, and my dvSwitch stayed functional, which shouldn’t be the case if it was actually using an Eval license. I’m worried though that in 60 days, something will kick in and expire!

    Finally, awesome blog! Extremely helpful!

  • Pingback: Buy Cheap Nike Air Max Shoes

  • Pingback: china

  • Pingback: chaussure Louboutin femme

  • Pingback: Chaussures Louboutin femme