So you need to enable it per registry change (see below), you also need to understand that there is a client config and a server config. Please keep noted that TLS 1.2 is disabled per default in Windows 2008 (see here). I still do not know if the one to blame is my server setup or the CozyRoc component, so I am now looking for any way to ensure that TLS 1.2 works on the server, independently of the SSIS setup. Please use TLS 1.1 or higher when connecting to Salesforce using 'UNSUPPORTED_CLIENT: TLS 1.0 has been disabled in this organization. Now when trying to connect I receive an error saying UPDATE: I tried to connect to our test Salesforce site, at which TLS 1.0 is disabled.

Ideally, I would like to know that my SSIS packages use TLS 1.2. My question is: how can I test if our server can use TLS 1.2 to communicate with SalesForce? I know that disabling TLS 1.0 can possibly mess up other connections, so I do not want to do that. The CozyRoc components which construct the call support TLS 1.2. Next, after rebooting of course, I recorded a trace with Wireshark to find out that our CozyRoc components in SSIS packages use TLS 1.0, as in Server Hello message we are getting TLS 1.0 in the handshake protocol section. We added no keys to SCHANNEL though, now the only protocol listed there is SSL 2.0. We installed the patches and made sure that the registry has required entries as it is stated in this article. As SalesForce drops TLS 1.0 next week, we are forced to use TLS 1.1 or 1.2 in our API calls, which we use to extract data for our DWH from Windows Server 2008R2 using SSIS custom CozyRoc components.

Test tls 1.2