I just want to caution everyone against believing a roll back from 6.7 will fix this issue. As I mentioned above, we're seeing it at two sites on 6.6 and 6.5 as well. Waiting to hear what SolarWinds discovers, but we originally began seeing the issue when running a Windows update as part of a larger package of hotfixes and patches on our networks running SEM back in March.
↧