Later versions of vCenter only support newer versions of the TLS protocol.
If you see errors in System Manager for vCenter data capture similar to:
Webservice e<name> does not exist or cannot be accessed on
the network
but you can prove connectivity by accessing https://<name>/mob in a browser and can log on with the userid and password you have set using the accounts.exe utility, then it is possible that TLS support has been increased to only permit TLS 1.2.
To re-establish connectivity, on the Windows systems running Acquire, open regedit and go to this location:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319
Create this DWORD key: SchUseStrongCrypto
Set the value to 1, close regedit and restart the Acquire service.
This is a Microsoft .NET registry item. More background and details can be found at the URL:
https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls