start-vm throwing error

[arjen]

Hi,

I am just starting out with PowerCLI.

I have connected to an ESXi 4.1 host (successful). Various commands (like get-VM) work fine.

"Start-VM -VM GuestName" fails with the error below. Can anyone point me in the right direction to solve this?

Start-VM : 7/15/2010 1:30:12 PM Start-VM fault.RestrictedVersion.summ

ary

At line:1 char:9

+ Start-VM <<<< -VM Guestname

+ CategoryInfo : NotSpecified: ( , SecurityError

+ FullyQualifiedErrorId : Client20_MoServiceImpl_Invoke_ViError,VMware.Vim

Automation.ViCore.Cmdlets.Commands.StartVM

[arjen]

Small update. I just tried a different operation (set-vm -MemoryMB 2048) on a guest, with the same error. So maybe it is an error doing things (rather than just retrieving values)?

[RvdNieuwendijk]

Hi Arjen,

try it like this:

$vm = Get-VM Guestname
Set-VM -VM $vm -MemoryMB 2048
Start-VM -VM $vm

Regards, Robert

Message was edited by: RvdNieuwendijk

[arjen]

Still exactly the same error.

The user account I am connected with can do all of these operations with no issues when connected via vSphere Client.

[RvdNieuwendijk]

You might get the error fault.RestrictedVersion.summary if you are running the unlicensed version of ESXi. See .

Message was edited by: RvdNieuwendijk

[arjen]

I have entered a license key (and everything looks fine under Licensed Features). Is there something else that defines "Unlicensed version"?

[LucD]

Do you connect to a vCenter or directly to the ESXi server ?

____________

Blog: LucD notes

Twitter: lucd22

[arjen]

Directly to ESXi

[RvdNieuwendijk]

It looks like a license problem. I have no problem changing the settings of a VM with PowerCLI 4.1 directly connected to an ESXi 4.1 server using the 60 days evaluation license.

[DSTAVERT]

The free version is limited to read access via scripts so no write access or starting/stopping vms.

[LucD]

What date do you see in the Expires field under the Licensed Features ?

____________

Blog: LucD notes

Twitter: lucd22

[arjen]

Here is what I see in the Licensed Features screen (key removed):

Product: vSphere 4 Hypervisor Licensed for 1 physical CPUs (1-6 cores per CPU)

License Key: ##########################

Expires: Never

Product Features:

Up to 256 GB of memory

Up to 4-way virtual SMP

[LucD]

That looks ok.

Just to make sure, can you connect with the vSphere Client to the ESXi server ?

And can you do a change from there ?

____________

Blog: LucD notes

Twitter: lucd22

[arjen]

Yes - everything is working flawlessly from the vSphere client side.

[DSTAVERT]

.RestrictedVersion says this is the free version and I don't believe you can issue scripted commands like start vm

[arjen]

OK. So just so that I am clear then - PowerCLI is really only for vCenter usage scenarios?

[LucD]

No, absolutely not.

You can connect to a vCenter but just as wwell to an ESX(i) server.

Only thing to remember is that your ESXi has to be licensed to be able to make changes through PowerCLI.

And that is the mystery here.

____________

Blog: LucD notes

Twitter: lucd22

[DSTAVERT]

There are commands that work but for the most part they are restricted to read. Some exceptions are restoring a configuration and performing an update to the ESXi host. If this is for a production environment then you should really have a look at the Essentials package which does give you vCenter and access to all the scripting possibilities.

http://www.vmware.com/vmwarestore/smb-solutions-server.html

[DSTAVERT]

Luc

Correct me if I am wrong it means paid license not just licensed does it not. The free version is also licensed.

[LucD]

You're right.

I just remembered this post .

With a vCenter Agent license you will be able to manage your ESXi from the vSphere client.

But not through PowerCLI

____________

Blog: LucD notes

Twitter: lucd22