cgevans

Actually, looking at the installed features, 4.5 is already installed. Joymon V/S Code: How to make .Net 4.0 & 4.5 use TLS 1.2 TLS 1.2 is enabled by default in 2012, but support from the .NET side only starts in version 4.5. To get 4.0 applications to use the 4.5 system.dll and therefore support TLS 1.2 you can add that…

Just v4.0.30319. I can install v4.5 though and switch the app pool over if that will help? I've been looking at this as well... HTTPS Monitor and SSL Certificate Expiration Date Monitor reports down status when TLS 1.0 disabled on monitored IIS ser… I tried to disable TLS v1.0 with the Nartac tool, but SolarWinds didn't…

Orion Platform 2015.1.2, QoE 2.0, IPAM 4.3, NCM 7.3.2, NPM 11.5.2, NTA 4.1.2, UDT 3.2.2, IVIM 2.1.0 The Orion Application Pool in IIS is using .NET v4.0. Is there any way to get it to support TLSv1.2, or is that in the next version?

For anyone looking for a solution to this, I solved it by creating the SNMPv3 node with placeholder credentials and then deleting those and adding an existing credential to the NodeSettings table. Python example: # If the node is SNMP version 3, then update the credential set from placeholder credentials. if…

Is this still a valid way of doing this? The API prevents you from adding an SMMPv3 node without specifying credentials. You can add an entry to the NodeSettings table after creation, but it is now an additional entry for that node and remnants of the old credentials used when creating the node are left behind. Is there a…

Update: As mentioned in the thread Upgraded server. Python API broken, PowerShell working , HTTP is not supported, (even though it connects). So, this made me look into the SSL issue. The best method would be to get TLSv1.2 working on the server, but this is apparently not supported in the current release version. Adding…