At most one remote plug-in instance with a given extension ID can be registered per vCenter Server

Remote plug-in registrations with different extension IDs are considered different plug-ins.

Remote plug-in registrations with the same extension ID but different manifest file locations are considered different instances of the same plug-in. In the case of multiple instances, any object-specific view is loaded by the plug-in server instance that is registered with the vCenter Server instance that manages the object. The view makes back-end calls to the server instance that loaded it.

Remote plug-in registrations with the same extension ID and the same manifest file location are considered a single instance. That instance serves all the vCenter Server instances with which it is registered. Any object-specific view is loaded by the single plug-in server instance that is registered with all the vCenter Server instances.

Remote plug-ins with the same extension ID and different manifest file locations can also have different versions. In that case, any object-specific view is loaded by the instance that is registered with the vCenter Server instance that manages the object. The details of an object-specific view might differ, depending on the version of the plug-in that is registered with the vCenter Server instance. The view makes back-end calls to the server instance that loaded it.

If an object is managed by a vCenter Server instance that has no instance of the plug-in registered, then no object-specific view is displayed for that plug-in.

In case of multiple instances, a single global view will be displayed for the remote plug-in, aggregating the global views of all plug-in instances, and a plug-in view selector allows for switching between the global view content from the different instances.