I can’t speak specifically to BC, but I suspect your major impacts will be on the SQL server, web server, and web clients rather than NAV/BC. It is a very good security measure to adopt. We did this about 2 years ago with on-prem SQL and web servers, and didn’t have any major issues. I recall we did have some unexpected issues with MS Office (I can’t recall specifically what), and had a couple of PC clients that got missed. Research any specific settings needed if you’re running older versions of SQL or Windows Server. Here’s the official documentation from MS including the registry key settings: https://learn.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-server. We found this handy tool that made the updates a lot easier than manually adjusting the reg keys: https://www.nartac.com/Products/IISCrypto. There is a lot of rebooting needed, so be mindful of your backup schedules. Windows event viewer will also be your friend to identify servers and/or software that might not be using the expected TLS version.
Please note:
This action will also remove this member from your connections and send a report to the site admin.
Please allow a few minutes for this process to complete.
Report
You have already reported this .
Welcome to our new site!
Here you will find a wealth of information created for people that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!