Remote Plug-in Discovery by the vSphere Client

The vSphere Client service checks for new remote plug-ins on the following different events:

• vSphere Client service startup. Any new remote plug-ins registered in the Extension Manager before this event will be installed and visible in the vSphere Client after the server startup finishes and the user logs in.

• User login. User login triggers a check for remote plug-ins that were registered after the server was started. The vSphere Client does not wait for the plug-ins to be fully installed before displaying the vSphere Client user interface. After the newly discovered remote plug-ins are deployed and ready for use, the user sees a notification, and a subsequent refresh will display the plug-in in the user interface. The notification displays as a banner at the top of the vSphere Client window, similar to this illustration:

  

• Browser refresh, while in developer mode. To select developer mode, you can set remote.plugin.updateOnBrowserRefresh=true in webclient.properties. A browser refresh while logged in to the vSphere Client triggers a check for newly registered remote plug-ins. Similar to user login, the vSphere Client will not wait for the plug-ins to be fully installed before proceeding. An additional refresh may be needed after the notification is displayed.

Remote Plugin Uninstallation

Unregistering a plug-in package on vCenter Server causes the vSphere Client service to delete the plug-in from the environment. A vCenter Server instance discovers plug-in unregistration when the vsphere-ui service restarts. At that time it removes the plug-in from cache.