Comments on: Setting of advanced options with the VI Toolkit

By: bjorn bats

bjorn bats — Mon, 22 Jun 2009 07:14:22 +0000

hugo,

is it also possible to set advanced settings of a virtual machine ?
this would be really handy, i cannot find it

By: admin

admin — Thu, 20 Nov 2008 06:50:21 +0000

Bubba,
That has something to do with “expression mode” versus “command mode”. In this case, it is not able to guess that you meant to provide a string. It tried to find a commandlet or executable that matches the name info. To be safe, you can always use parenthesis. Or read more about parsing modes here: http://keithhill.spaces.live.com/Blog/cns!5A8D2641E0963A97!6058.entry

By: bubba

bubba — Thu, 20 Nov 2008 04:29:04 +0000

Strange, I changed info with “info” and all of a sudden it started working…
Would you have some more example, but with API Ref, it would really help, thanks!

By: bubba

bubba — Thu, 20 Nov 2008 04:21:17 +0000

Strange that I am trying to change vpxSetting:

$SI = Get-View ServiceInstance
$OM = Get-View $SI.Content.Setting
$OM.QueryOptions(“log.level”)

#$newOption = New-Object VMware.Vim.OptionValue
$newOption.Key = “log.level”
$newOption.Value = info

$OM.UpdateOptions($newOption)

But i get error:

PS C:\Program Files\VMware\Infrastructure\VIToolkitForWindows> .\queryAdvValue.ps1

Key Value DynamicType DynamicProperty
— —– ———– —————
log.level verbose
The term ‘info’ is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again.
At C:\Program Files\VMware\Infrastructure\VIToolkitForWindows\queryAdvValue.ps1:7 char:24
+ $newOption.Value = info <<<<
Exception calling “UpdateOptions” with “1″ argument(s): “A specified parameter was not correct.
”
At C:\Program Files\VMware\Infrastructure\VIToolkitForWindows\queryAdvValue.ps1:9 char:18
+ $OM.UpdateOptions( <<<< $newOption)

I am thinking maybe I incorrectly use UpdateOptions?

_{»crosslinked«}