|
Objective 4.2 – Manage vSphere Client plug-ins |
|
|
|
Written by Matthijs van den Berg
|
|
Friday, 16 October 2009 12:25 |
Knowledge
- Identify available plug-ins
The number of plug-ins can very with the exact release of vSphere. During the initial release the plug-ins worth mentioning are:
- vCenter Guided Consolidation
- vCenter Update Manager
- vCenter Converter
- vCenter Storage Monitor (default)
- vCenter Hardware status (default)
- vCenter Service Status (default)
- Determine required plug-ins for a given application
Not really quite sure what is meant here (again ;-) ). I think it is quite obvious that when you install the Update Manager that that Update Manager plug-in is the associated plug-in to install.
- Ensure permissions to install plug-ins
This was a really pain in the ass. I cannot find any User Access Control method of denying users access to plug-ins, the plug in menu etc. It is not an option in de roles menu. So I think the best way to deny access is not to install the plug-in on the host system. To disable this I think the best way is to use Windows user permissions.
Update 1 dec 2009: I have received a mail from Peter. He point me to 'Table a-6 - extension priveleges' of vsphere basic system administration. This should allow control over registering/unregistering/
updating and extension (plug-in). Unfortunately after testing this with a user, and leaving this option unchecked, it does not do the trick. I am not sure whether this is a bug and should work (cannot find anything else this setting should do) or that we are on the wrong track here.. if you know more... please help.
If anybody knows a better way, please contact me or leave a message in the commend system!
- Enable plug-ins after installation
When I plug-in is installed you need to enable it. To do so:
- open the Plug-in Manager
- Right click a installed plug-in
- Click “Enable” to enable the plug-in.
Tools
|