PowerCLI restrictions ?

[Bernd_Nowak]

Hi all,

I started to do some testing with the PowerCLI but noticed an annoying thing which is that not all commands are available in the ESXi4 free version.

Recently I played with a ESXi 4 host which was running the free 60 days version.

With this version this command works: ShutdownHost_Task

So I tried it on my own ESXi 3.5 server which has the free license code applied to and get a response like this:

Exception calling "ShutdownHost_Task" with "1" argument(s): "fault.RestrictedVersion.summary"

I then applied the free license code to my trial ESXi 4 host and wasn't surprised that after I applied the license that the command wasn't working anymore. Is there a list of available commands for the free licensed ESXi or is it trial and error ?

Why isn't it possible to do the same I can do with the vSphere Client GUI (Shutdown/Restart) from a command line utility ?

Sorry if it sounds like a rant, it shouldn't sound like one

[LucD]

Any non-read operation you perform against a "free" ESXi host will not work, independent if you're using PowerCLI or any other language.

You need at least the vCenter agent license to manage your "free" ESXi host from the vSphere client.

That explains why you can do a shutdown from your vSPhere client.

Generally speaking, the Get type cmdlets will work against a "free" ESXi host.

PS: with ESXi 3.5U3 a mistake was made and you could read/write to the "free" ESXi host.

That feature disappeared with ESXi 3.5U4

[Bernd_Nowak]

Strange restriction.

But thanks for taking the time to answer my question. So in general I can read/write with PowerCLI or any other language if I or my customers have a bought version of EXS(i) ?

[LucD]

I'm no licensing specialist but perhaps do like this thread ( ) seems to advise call VMW.

[halr9000]

While I don't like the restriction, it's not strange, per se. VMW made a business decision to limit the automation options on their free hypervisor. They want to have reasons for you to upgrade of course, and one of them is the ability to fully manage your VI using PowerShell and Perl (e.g. RCLI). Every once in a while I complain about it to my contacts there.

[vExpert|http://www.vmware.com/communities/vexpert/], PowerShell MVP, VI Toolkit forum moderator

Author of the book: Managing VMware Infrastructure with PowerShell

Co-Host, PowerScripting Podcast (http://powerscripting.net)

Need general, non-VMware-related PowerShell Help? Try the forums at PowerShellCommunity.org

[Bernd_Nowak]

Thanks for the answer. Wish that they will rethink it. I did some search for Xen Server and will try it a bit more. Although I love the VMWare products it seems that some decisions are 'strange' for me.

And it's not a 'I will quit' message but for a small customer with only 2 or 3 servers on one physical machine I found no paid version which will suit the customer. The essentials package seems nice but it's 3 physical servers. My small customers are happy with one

A small ESXi license with just the remote managment possibility added in the price range of VMWare workstation seems to be the way to go if VMWare really needs my money that bad and don't want to include this feature in the free ESXi version.

[bjkamp]

Just so you know, with vmware you can execute local scripts on the vmhost and you are able to execute local scripts remotely using ssh and Putty plink on any vmhosts in batch. See for example http://communities.vmware.com/message/1414668#1414668

Maybe that will help you managing vm machines remotely using batch scripts, if you are a script kidd

[Bernd_Nowak]

I'm talking about ESXi free version with no SSH access enabled which is the default so this is not an option. I know that I can use putty and remote scripts on ESX and that I can use the CLI tools with them or SSH.

But thanks for the tip!