VMware Cloud Community
halr9000
Commander
Commander
Jump to solution

scripting vCenter plugins

Has anyone messed with vCenter plugins? I need to write a script to see if a plugin is enabled or disabled. So far, I've not had much luck finding the right API hooks. I even looked at XML config files and I don't see one o' dem either.

I've scoured ExtensionManager and don't see an indication of whether a plugin is enabled or not. It's gotta be in the SDK somewhere though.

$extMgr = Get-View (Get-View ServiceInstance).Content.ExtensionManager


[vExpert|http://www.vmware.com/communities/vexpert/] 2009-2010, PowerShell MVP, PowerCLI forum moderator

Author of the book: Managing VMware Infrastructure with PowerShell

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

Follow me on Twitter: @halr9000

My signature used to be pretty, but then the forum software broked it. vExpert. Microsoft MVP (Windows PowerShell). Author, Podcaster, Speaker. I'm @halr9000
0 Kudos
1 Solution

Accepted Solutions
LucD
Leadership
Leadership
Jump to solution

I think you're mixing two different features here.

The ExtensionManager allows one to add/remove additional functionality to the vCenter with the Register/Unregister methods.

Some examples: Converter, Update Manager, Performance Overview reports...

Some of these Extensions provide plugins for the vSPhere Client.

Most of the time these plugins allow one to interact with the Extension.

But there can also be free-standing plugins.

For example the following XML file will create an entry pointing to a local PowerCLI Reference.

<scriptConfiguration version="1.0.0">
	<key>PowerCLI Refrence</key>
	<description>PowerCLI Reference</description>
	<view parent="Inventory.Global">
	<title locale="en">PowerCLI Refrence</title>
	<url>file://D:\User\vSphere PowerCLI Cmdlets Reference\index.html</url>
	</view>
</scriptConfiguration>

These plugins are computerbased, i.e. if you "enable" a plugin on PC1 it will not automatically be enabled on PC2.

The enabled/disabled state of a plugin is kept in the registry in HKCU\Software\VMware\VMware Infrastructure Client\Preferences\UI.

Each plugin has a REG-SZ key with a of value Enabled or Disabled.

____________

Blog: LucD notes

Twitter: lucd22


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

View solution in original post

0 Kudos
2 Replies
LucD
Leadership
Leadership
Jump to solution

I think you're mixing two different features here.

The ExtensionManager allows one to add/remove additional functionality to the vCenter with the Register/Unregister methods.

Some examples: Converter, Update Manager, Performance Overview reports...

Some of these Extensions provide plugins for the vSPhere Client.

Most of the time these plugins allow one to interact with the Extension.

But there can also be free-standing plugins.

For example the following XML file will create an entry pointing to a local PowerCLI Reference.

<scriptConfiguration version="1.0.0">
	<key>PowerCLI Refrence</key>
	<description>PowerCLI Reference</description>
	<view parent="Inventory.Global">
	<title locale="en">PowerCLI Refrence</title>
	<url>file://D:\User\vSphere PowerCLI Cmdlets Reference\index.html</url>
	</view>
</scriptConfiguration>

These plugins are computerbased, i.e. if you "enable" a plugin on PC1 it will not automatically be enabled on PC2.

The enabled/disabled state of a plugin is kept in the registry in HKCU\Software\VMware\VMware Infrastructure Client\Preferences\UI.

Each plugin has a REG-SZ key with a of value Enabled or Disabled.

____________

Blog: LucD notes

Twitter: lucd22


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

0 Kudos
halr9000
Commander
Commander
Jump to solution

I suspected as much. Thanks for the reg tips!

My signature used to be pretty, but then the forum software broked it. vExpert. Microsoft MVP (Windows PowerShell). Author, Podcaster, Speaker. I'm @halr9000
0 Kudos