I’m getting a redundancy lost error on one of my ESX hosts, and I was wondering if someone could point me in the correct direction here.

 

I’ve inherited this vmware/vcenter farm and I’m having a heck of a time with this error.

 

I’ve logged into my switches and I don’t see any ports that don’t have a link light that should. I’m thinking this is a configuration error somewhere.

Summary

 

This is a drop-in replacement of  the implementation of  the vCenter plug-in for vRealize Orchestrator

The plugin implementation is completely redesigned, by keeping the existing content

The new plug-in offers:

• Optimization of the communication with vSphere servers and reducing of the load on these
• Hassle-free update of Scripting API, when Vsphere API changes, thanks to new approach for auto-generated integration
• Preserve maximum Scripting API compatibility, respectively content compatibility

 

For 7.3 release following improvements were delivered:

• All PBM API types are exposed as vRO scripting types
• All SMS API types are exposed as vRO scripting types
• Exposing of the Storage Policies and Policy Components  as vRO inventory items

Plugin versioning and interoperaility with vSphere vCenter servers

• The plugin core functionality (connectivity, inventory) is compatible with vSphere with version 5.5 and above.
• vSphere API version exposed in the scripting API is 6.5
  • That means that all API methods, properties and types introduced in vSphere 6.5 are made available to vRO scripting content developers and will work if supported by the vSphere server product. For convenience in this new version of the plugin all the methods and properties are annotated in their description (visible in vso.xml and API explorer ) with version tag, e.g ‘@since vSphere API 5.5’

Interoperability with vRO

The plugin is compatible with vRO version 7.3 and newer.

Install procedure

 

Few of the workflows are changed to reflect the minor incompatible changes in the API, so these will be overwritten during install.
The plugin can be installed in the standard way

Released versions (newest at the bottom)

 

Version 6.5.0.5817435

• Fixing in bulk fetching of objects based on queries – plugin factory ‘findAll’ method now uses default set of properties to be pre-loaded
• Fixes in ‘Convert independent disks’ workflow

Version 6.5.0.6216831

• Fixes in construction of instances of scripting types based on VLSI basic types , e.g – VcKeyAnyValue’
• Fixes in ‘data’ objects serialization process

Version 6.5.0.6374976

• Fixes in vlsi client resources finalization to prevent leaking of vlsi monitoring threads

Version 6.5.0.6471915

• Fixes in deserialization of ‘Any’ attributes, causing failures in “Clone, Windows with single NIC and Credentials” and dependent workflows

Version 6.5.0.7037717

• Rest API query specifications implementation moved to plugin, resulting in performance improvements in case such a query is used (XaaS Blueprint forms etc.)

Version 6.5.0.7208762

• Additional fixes to plugin’s Rest API query specifications implementation

Version 6.5.0.7720419

• Fixes in the Object fetching functionality
• Update VMODL definitions for the plugin with a newer version
• Fixing compatibility issues with vRO 7.3
• Fixing Malformed URI exception when executing the workflow “Get virtual machines by name with PC”

Version 6.5.0.9407750

• VcKeyAnyValue issue with values of type array of string

Version 6.5.0.10376265 (VMC fix – KB 59459)

• Fixes in cache update logic
• Fixes in connection validation against newer versions of vSphere servers
• Enable explicit preloading of properties for set of managed objects

Version 6.5.0.11809518

• Fixes in  reconnection logic to vSphere servers in case of restart

Version 6.5.0-12316907 (built 2019-02-14)

• Adds CertificateManager to the management objects available in the plug-in. You can access it through:
  var certManager = sdkConnection.certificateManager;

Version 6.5.0.

• Extending logging in ‘Copy file to Guest’ functionality

Version 6.5.0-13863019 (built 2019-05-29)

• Maintenance thread causes memory leak
• Performance improvements – plugin finders now load all the needed properties. This improves the loading of multiple object used as output parameters

Version 6.5.0-14070255 (built 2019-07-02)

• Fixes in the ‘Copy file from/to Guest’ connection establishment (PKIX failures)

Version 6.5.0-14137330 (built 2019-07-11)

• Fixed serialization of non-findable plugin objects (e.g. VcAlarmState, SnapshotInfo, etc) into workflow attributes
• Fixed a possible NullPointerException when old vm snapshots are removed along with child snapshots

Version 6.5.0-14534446 (built 2019-08-30)

• Skipping non-existing values when converting Method name values received from the Property Collector
• Fixing problems with maintaining sessions when the number of vCenter servers is greater than 25
• Fixing memory leaks

Version 6.5.0-15013492 (built 2019-11-04)

• Fixed “cert parameter is required” error in “Register vCenter Orchestrator as a vCenter Server extension” workflow for vRO 8.0

Version 6.5.0-15225986 (built 2019-12-03)

• Compatibility with vSphere 6.7u3 API

Version 6.5.0-15464295 (built 2020-01-15)

• Fixed problem with caching of hosts in ESXi cluster

Version 6.5.0-16613969 (built 2020-07-21)

• Fixed compatibility with VMC M11 release (June 2020 release)

Version 6.5.0-16904859 (built 2020-09-16)

• Fixed issue loading endpoint configurations when there is issue in one of them
• Fixed workflow Remove old snapshots to ignore erroneous ESX hosts

Hello,

If I have a ThinApp executable or dat file but I don’t have the original precompiled setup capture files, is it possible to extract the application’s file and registry contents from the executable/dat file?

Thanks