Since this post is still the first Google Result for a few relevant searches:
For anyone still finding this post 3+ years later, the answer is to upgrade Central server to v 12.1.1 or above. 12.1.1 was released 4/2/2020. Prior to that there was not a fix (At least not one that I could located).
Prior to 12.1.1 the central server still forced both TLS1.0 and SSL3 on port 6132, even if the operating system registry had them flagged as disabled.
Since this post is still the first Google Result for a few relevant searches:
For anyone still finding this post 3+ years later, the answer is to upgrade Central server to v 12.1.1 or above. 12.1.1 was released 4/2/2020. Prior to that there was not a fix (At least not one that I could located).
Prior to 12.1.1 the central server still forced both TLS1.0 and SSL3 on port 6132, even if the operating system registry had them flagged as disabled.
