You cannot reconfigure vSphere Replication & VMware Live Site Recovery appliances to register with vCenter because you hit the error.
ERROROperation Failed A general system error occurred: Failed to register H5 UI.Operation ID: 881a553c-7dc2-4cbd-b717-581ecfcbc002
/var/log/vmware/dr/drconfig.log :
--> Unhandled exception
--> com.vmware.vim.sso.client.exception.ServerCommunicationException: Error communicating to the remote server https://vcenter.broadcom.com/sts/STSService/vsphere.local
--> at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:996)
--> at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.executeRoundtrip(SecurityTokenServiceImpl.java:902)
--> at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl.acquireToken(SecurityTokenServiceImpl.java:155)
--> at com.vmware.vlsi.client.sso.StsService.acquireBearerToken(StsService.java:88)
--> at com.vmware.vlsi.client.sso.StsService.acquireBearer(StsService.java:82)
--> at com.vmware.hms.config.cli.command.CommandBase.run(CommandBase.java:299)
--> at com.vmware.hms.config.cli.App.run(App.java:146)
--> at com.vmware.hms.config.cli.App.main(App.java:206)
--> Caused by: com.vmware.vim.sso.client.exception.ServerCommunicationException: Error communicating to the remote server https://vcenter.broadcom.com/sts/STSService/vsphere.local
--> at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:226)
--> at com.vmware.vim.sso.client.impl.SoapBindingImpl.sendMessage(SoapBindingImpl.java:120)
--> at com.vmware.vim.sso.client.impl.SecurityTokenServiceImpl$RequestResponseProcessor.sendRequest(SecurityTokenServiceImpl.java:983)
--> ... 7 more
--> Caused by: com.sun.xml.ws.client.ClientTransportException: HTTP transport error: javax.net.ssl.SSLHandshakeException: URI name must include scheme:vcenter.broadcom.com
VMware vSphere Replication 9.x
VMware Live Site Recovery 9.x
This error arises when the vCenter certificate does not conform with X.509 certificate standard set for public key certificates. vCenter's SSO library could not recognize the URL.
When the subjectAltName extension contains a URI, the name MUST be stored in the uniformResourceIdentifier (an IA5String). The name MUST NOT be a relative URI, and it MUST follow the URI syntax and encoding rules specified in [RFC3986]. The name MUST include both a scheme (e.g., "http" or "ftp") and a scheme-specific-part. URIs that include an authority ([RFC3986], Section 3.2) MUST include a fully qualified domain name or IP address as the host. Rules for encoding Internationalized Resource Identifiers (IRIs) are specified in Section 7.4.
Regenerate the certificate to comply with X.509 standards by either removing the URL information or updating it accordingly, then replace the vCenter certificates. You can now reconfigure all the appliances, and it should function properly.