Even when the less secure TLS 1.0 and 1.1 have been disabled on a network or computer, some Snow applications may continue to try and use these versions to secure communications. This happens because some versions of the .Net Framework default to these versions. Follow the procedure below to update the applications to ignore this .Net configuration in favor of the most secure option available.
- Make a backup copy of the .config file for the application before you begin, so you can rollback in case something goes wrong.
- Open the .config file for the application using a text editor such as Notepad++.
- Inside the <configuration> element, add the following content (<configuration> element included for your reference -- do not duplicate it):
<runtime>
<AppContextSwitchOverrides value="Switch.System.Net.DontEnableSchUseStrongCrypto=false"/>
</runtime>
</configuration>
- Save the file and restart the application.
Here's an example of the .config file for Snow Update Services with the required content added:
Alternatively, follow the procedure below to set this configuration in the Windows registry. Doing so affects all the applications installed on the computer exmploying the configured framework. Modifying the registry can be dangerous and may cause system instability or even data loss if not done properly.
- Backup the registry before making any changes.
- In the Registry Editor for the application server, expand the tree to find the configuration node for .NET Framework
- For .NET Framework version 2.0.50727, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v2.0.50727.
- For .NET Framework version 4.0.30319, go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319.
- For each installed version:
- Create a new DWORD value named SystemDefaultTlsVersions and set its value to 1.
- Create a new DWORD value named SchUseStrongCrypto and set its value to 1.
- Restart the application.
Related Articles
Secure your estate with HTTPS and TLS 134Number of Views TLS versions used by FlexDeploy, RISC Networks, and RN150 1Number of Views The request was aborted: Could not create SSL/TLS secure channel. 56Number of Views Failed to connect to Flexera Service Gateway with error "Could not create SSL/TLS secure channel." 14Number of Views Error: "The request was aborted: Could not create SSL/TLS secure channel" when calling api.flexera.com from Windows Server… 60Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago