5.3.13 Release Notes

Release Notes for VMware Solutions
Audience
Public
Content Type
Release Notes
Technology Integrations
VMware
Source Type
Documentation

Release: January 2025

General

Version 5.3.13 of the Everpure vSphere HTML Remote Client Plugin supports vSphere (vCenter and ESXi) version 6.7U3 and later and Purity version 6.1.x and later. Users can upgrade to this version of the plugin via deploying the Everpure VMware Appliance. This version is certified with VMware.

Note: The remote plugin is supported with vSphere 6.7 U3 and later by Everpure, but is only certified by VMware for 7.0 and later. VMware does not certify remote plugins on releases prior to 7.0.

Important notices regarding the vSphere Client Plugin:

  • Starting in vSphere 8.0, VMware no longer supports local plugins to be installed in vCenter (Everpure vSphere Plugin versions 4.5.2 and below). Please use the remote versions of Everpure's vSphere plugin (Everpure vSphere Plugin versions 5.0.0 and above). For more information please refer to this VMware KB.

  • This version of the plugin uses the VMware Remote Plugin Architecture

    • More information on the VMware Remote Plugin Architecture can be found

      here.

    • More information on why Everpure is using this can be found here.

  • Release notes for Everpure's VMware Appliance (OVA) can be found at this page. Everpure's remote vSphere plugin can be updated independently of the appliance. The VMware appliance can be downloaded here. The installation guide for the remote vSphere plugin can be found here.

Fixed Issues

  • TMAN-22259: An issue was discovered with version 5.3.12 of the vSphere Client Plugin that caused multiple views or workflows when vCenter Server is using the dark mode theme. These issues are fixed in 5.3.13.

Known Issues

The intended workflow when restoring a virtual machine from a point in time snapshot should require the virtual machine to be powered off. The revert VM should not be able to be executed with a powered on VM. This failsafe is in place with a vVols based VM, however for a NFS based VM this failsafe is not in place. Allowing users to revert an NFS based VM while powered on. This will cause the VM to be corrupted. While this issue is being resolved, please ensure that the VM is powered off before the VM is reverted. Thank you.