The most recent content from our members.
Hi, We are running SCOM 2012 R2 UR14 and using Solarwinds NPM for N/W monitoring along with SolarWinds Management Pack for SCOM to get the alerts into SCOM. We are now planning to implement TLS 1.2 in our SCOM 2012 R2 environment. As part of the plan we are checking all the Management Packs we are using support TLS 1.2 on…
Current agent deployments are failing Qualys PCI scans due to the availability of the TLS 1.0 protocol which is not allowed as of the end of June 2018. Disabling TLS 1.0 in the registry of the server has no effect on the scan results. Unless TLS 1.0 is disabled or the option is made to disable it the PCI audit will fail.…
ipMonitor Version: 10.0 build 1371 ... Does it Support TLS 1.2?
You seem to have a strict "no public timelines" policy which while very unhelpful to begin with, is becoming a big problem for us with the TLSv1.2 issue and our need to comply with PCI. Can you tell me if you will have support for TLSv1.2 completed prior to June 30th of this year per PCI requirements? If this is not…
As 2018 is fast approaching so is the June 30, 2018 deadline to disable TLS 1.0 and 1.2 due to PCI requirements. Currently EOC needs to have TLS 1.0 enabled on its self and any of the servers being monitored. I would be great sooner then later of we could get this supported added in as many companies have already started…
I have KIWI Syslog evaluation version(Kiwi_Syslog_Server_9.5.1.Eval.setup). I have enabled SSL on Syslog server following all the steps as mentioned in syslog help ) . But on KIWI Syslog Server Console Under (File-> Setup->Inputs->Secure TCP) I am getting message "Only available in licenced version". But under FAQ on KIWI…
It looks like you're new here. Sign in or register to get started.