#Srm compatibility matrix 6.0 upgrade#

This method also works for other extensions registered with the vCenter Server. Refresh the page and verify that the extension is now deleted. Close the Unregister Extension window and return to the Extension Manager.If successful, the method invocation result should display вЂ“ void вЂ“ status as depicted below.Paste the vmware.vcDr string in the Value field and click Invoke method. Copy the vmware.vcDr string and go back to the Extension Manager.The description should read вЂњVMware vCenter Site Recovery Manager extensionвЂќ. Steve OConnor, Director of IT, Aston Martin. Click on extensionList and then click on Description. With Juniper, we have a high-performance network that is simpler, more consistent and easier to support.SAP KBA 2160815 - FAQ Note: SRM-MDM Catalog versioning and compatibility with SAP MDM and SAP SRM SAP Note 2119166 - Support of SRM-MDM Catalogs for Netweaver 7.4 SAP Note 2373702 - Release Information Note of SRM-MDM Catalog all versions based on MDM 7.1 SP15 Build 7.1.15. Click (moreвЂ¦) on the Properties table to expand the list. SAP Note 1476694 - Change in SRM-MDM Catalog 3.0 components in SMP.Open your internet browser and navigate to the following URL вЂ“ and log in as the administrator.

#Srm compatibility matrix 6.0 upgrade#

As per the Upgrade Compatibility matrix (VMware Product Interoperability Matrices) you can only upgrade SRM 5.8.1 to SRM 6.1.2. Note: According to KB 1025360, this method should also work for the vCenter Server Appliance. Hi Mike, Yes, you have unfortunately hit an issue where you cannot directly upgrade SRM. For example, ASDM 7.12 (1) can manage an ASA 5515-X on ASA 9.10 (1). ASDM versions are backwards compatible with all previous ASA versions, unless otherwise stated. Here is a quick how-to on manually removing the SRM extension from the vCenter Server. ASA 9.12 (x) was the final version for the ASA 5512-X, 5515-X, 5585-X, and ASASM. Recently, I did some SRM troubleshooting for several customers where the SRM extension was not removed from the vCenter Server after running the uninstaller on a Windows machine running vCenter Server.