The easy fix is just a reg file that has the registry entry defined in the KB article. Here's an example of what it might look like.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000AA8
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000AA8
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings]
"SecureProtocols"=dword:00000A80
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings]
"SecureProtocols"=dword:00000A80
The above, should, enable all protocols for x86 and x64. It also follows the recommendation to enable it in IE although that is probably better handled by a GP policy.
Note that this is highly configurable as you may or may not want all the protocols enabled. Most modern HTTPS sites require TLS 1.2 only so enabling the others is a security risk.