jlapchuk

Hi jlapchuk,

Thanks for reaching out us!

This looks like a VMware SOAP inventory deserialization failure during RetrieveProperties: vCenter is returning a CustomFieldValue typed as CustomFieldStringValue, and the VMware SOAP client used by RDM 2026.1.18 isn’t recognizing that type, so synchronization fails while parsing the inventory.

Workaround to try first

• Edit the VMware Synchronizer entry and change “API mode” from Default to Legacy.

• If it still fails, try Experimental.

• (VMware Synchronizer “API mode” setting: https://docs.devolutions.net/rdm/kb/knowledge-base/entry-settings/configure-a-vmware-synchronizer-entry-in-en-rdm/)

If Legacy or Experimental works, that strongly suggests a compatibility issue specific to the Default API path with your vCenter version.

To confirm, please share:

• vCenter version/build number(s)

• Which API mode(s) fail vs succeed (Default / Legacy / Experimental)

Thanks in advance!

Best regards,

@Eduard Sepúlveda López

None of the legacy or experimental APIs work for us, same as everyone else on this thread. This appears to be a bug introduced with this latest version.

After upgrade to RDM v2026.1.18.0 64-bit (JIT) I'm no longer able to synchronize with any of our vCenters, receiving the following error:

System.ServiceModel.CommunicationException: Error in deserializing body of reply message for operation 'RetrieveProperties'.
 ---> System.InvalidOperationException: There is an error in XML document (7, 696).
 ---> System.InvalidOperationException: The specified type was not recognized: name='CustomFieldStringValue', namespace='urn:vim25', at <CustomFieldValue xmlns='urn:vim25'>.
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read1521_CustomFieldValue(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read1_Object(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read1863_DynamicProperty(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read1917_ObjectContent(Boolean isNullable, Boolean checkType)
   at Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderVimPortType.Read2158_RetrievePropertiesResponse()
   at Microsoft.Xml.Serialization.GeneratedAssembly.ArrayOfObjectSerializer183.Deserialize(XmlSerializationReader reader)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   --- End of inner exception stack trace ---
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle, XmlDeserializationEvents events)
   at System.Xml.Serialization.XmlSerializer.Deserialize(XmlReader xmlReader, String encodingStyle)
   at System.ServiceModel.Dispatcher.XmlSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, XmlSerializer serializer, MessagePartDescription returnPart, MessagePartDescriptionCollection bodyParts, Object[] parameters, Boolean isRequest)
   --- End of inner exception stack trace ---
   at System.ServiceModel.Dispatcher.XmlSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, XmlSerializer serializer, MessagePartDescription returnPart, MessagePartDescriptionCollection bodyParts, Object[] parameters, Boolean isRequest)
   at System.ServiceModel.Dispatcher.XmlSerializerOperationFormatter.DeserializeBody(XmlDictionaryReader reader, MessageVersion version, String action, MessageDescription messageDescription, Object[] parameters, Boolean isRequest)
   at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeBodyContents(Message message, Object[] parameters, Boolean isRequest)
   at System.ServiceModel.Dispatcher.OperationFormatter.DeserializeReply(Message message, Object[] parameters)
   at System.ServiceModel.Dispatcher.ProxyOperationRuntime.AfterReply(ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
   at System.ServiceModel.Channels.ServiceChannelProxy.TaskCreator.<>c__DisplayClass1_0.<CreateGenericTask>b__0(IAsyncResult asyncResult)
--- End of stack trace from previous location ---
   at Devolutions.VMwareManagement.InventoryNavigator.RetrieveObjectContents(String[][] typeinfo, Boolean recurse, ManagedObjectReference startFolder)
   at Devolutions.VMwareManagement.InventoryNavigator.SearchManagedEntities(String[][] typeinfo, Boolean recurse, Boolean withPath)
   at Devolutions.VMwareManagement.VMwareSoapClient.GetVMList(Boolean withPath)

Great! Thanks for the update!

Whether I open with external or embedded, it still does not work. If I run mstsc.exe /remoteGuard, then it runs RDP with credential guard enabled. Currently, I don't see an option to pass the /remoteGuard switch for an RDP session.

Hello,

I understand there's an option to use Restricted Admin Mode on a RDP session. However, beginning in Windows 10 1607 / Server 2016, there's a new option to use Remote Credential Guard. Can this option also be added to Remote Desktop Connect Manager?

https://docs.microsoft.com/en-us/windows/security/identity-protection/remote-credential-guard