1-800-691-1991 | 9am - 8pm ET

Monitoring vSphere 5.1 and 5.5 with Veeam MP/SPI 5.7


If you connect to vCenter Server 5.1 or 5.5, Veeam MP/SPI 5.7 will not collect some data, including hardware sensor metrics and vCenter-specific events and properties that were introduced by VMware since VMware vSphere 4.0. vCenter events and properties that were introduced before VMware vSphere 4.0 will be collected without errors.


Although as per the system requirements the Veeam MP/SPI 5.7 does not support the VMware vSphere 5.1/5.5 platforms, it is possible to configure a connection to vCenter Server 5.1/5.5 in the Enterprise Manager Web UI.


To resolve the issue, apply the Veeam MP/SPI 5.7 patch available on the Veeam MP and Veeam SPI downloads web pages, following this link.

More information

With this patch applied, nworks 5.7 MP/SPI are compatible with all vSphere 5.x versions. All functionality introduced for support of vSphere 5.0 will be available. Note that no additional events or metrics specific to vSphere 5.1/5.5 will be collected.

Note, that once the patch is applied, you will see a warning in nworks UI, because the collector version will be later than that of the Enterprise Manager. The warning is expected and does not indicate any issue; it can be safely ignored.

Veeam Management Pack for Microsoft System Center
Last Modified:
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later