You are viewing limited content. For full access, please sign in.

Question

Question

Enable TLS 1.2 on Laserfiche 11 on a Server 2012 R2 system

asked on March 20, 2023 Show version history

We were giving the 'STEPS - TLS 1.2 Implementation-2019-10-29 Original word document to implement TLS 1.2  but the document states it is for a Server 2016 install.   We have a Laserfiche 11 install on a Server 2012 R2 server.  Followed the Server 2016 instructions.   We do NOT have access to any of our Laserfiche websites now.   And can not get to our SQL database.   Does anyone have TLS 1.2 implementation documentation for Laserfiche 11 on a Server 2012 R2 server?

0 0

Replies

replied on March 20, 2023

Windows 2012 can be configured to support TLS 1.2, so what you want is possible. One question is if the steps in that document are a viable way to achieve your goal. If the document describes itself as a guide for Win 2016, I'm sure the authors didn't try it on Win 2012.

What I didn't see mentioned in the document was any mention of configuration of client machines and applications, which might be necessary depending on your version. But, "We do NOT have access to any of our Laserfiche websites now" implies to me that the configuration went wrong on the server side; all modern browsers should be capable of connecting over TLS 1.2.

0 0
replied on March 21, 2023 Show version history

Most likely a number of Windows Server 2012 R2 features (including but not limited to RDP) were still configured to use TLS 1.0/1.1, and when those protocol versions were disabled at the OS level, a bunch of things stopped working.

When I've accidentally locked myself this way before, I was able to re-enable TLS 1.0/1.1 on the affected machine using remote registry editing (see below) or PowerShell remoting.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.