Hello and welcome the brand new FrameFlow web site!
We’ve redesigned everything to make the site mobile friendly and much more responsive.
Have you looked at FrameFlow Multi-Site Monitor and wondered how it works? To learn more about it, watch our two minute presentation. It explains how our unique multi-site technology can help you to distribute your monitoring tasks and scale up your configuration to 1000’s of systems.
We released v2016.1 today and our first new update this year delivers a set of fixes for recently reported issues. If you’re running on an earlier version we recommend that you upgrade when you have a chance and take advantage of the updates included in this new build.
Some highlights include:
– Fixed an issue with subtitle displays for rackmount network diagram objects.
In parallel we have been working on a major update that will focus on dashboard improvements and add some amazing new utilities that can be accessed from right inside the FrameFlow interface. We don’t yet have a fixed date for the next release but we’re aiming for early March.
Here we are: Patch Tuesday again. This month Microsoft has delivered just six fixes but several of them are “cumulative updates” so they in fact contain a multitude of fixes. Of the six major items, three of them are rated critical with a risk of remote code execution so as always it’s important to get this month’s fixes rolled out as soon as possible.
For the complete list of fixes see the Microsoft Security Bulletin Summary for October 2015.
This month’s delivery includes 14 fixes with 4 of them rated Critical and the rest rated Important. In the Critical category we find fixes for remote code execution flaws that affect Windows, Office, the .NET Framework and more. Interestingly, in the first Patch Tuesday since Windows 10 was released, we find critical fixes for Microsoft’s new Edge browser too.
The remainder of the fixes address various privilege escalation and information exposure problems.
For the complete list of fixes see the Microsoft Security Bulletin Summary for August 2015.
Building FrameFlow Server Monitor: A Day in the Life
We do our best to keep our software lean and mean. Our business is 100% based on a try-before-you-buy model, so it’s important that we make a great first impression and part of that has to do with the ease of deployment and perception of quality. There are few things we hate more than when we go to download a simple utility to get a job done and it weighs over 500 megs in size.
Keeping our software fast, efficient and small isn’t always an easy thing. We’re sometimes at the mercy of third-party components that we integrate with and sometimes we have to deal with problems thrown our way by the development tools that we use.
Recently we faced a challenge along these lines and here is how it played out…
This month’s delivery includes a total of 14 patches with 4 of them listed as critical.
One of the fixed flaws is flaws is a perfect example of why all system administrators need security on multiple levels.
FrameFlow v2015.2 Released
We are very happy to announce that FrameFlow v2015.2 is now available for download. Licensed users can log into their account on our site to find the download links. Those of you who are in the evaluation phase can re-download the eval version. Either way, run the setup and it will upgrade your existing installation while preserving all of your settings and configuration.
This release is a major update bringing lots of new functionality. The major highlight is support for multiple alert levels including success, warning, error and critical.
To implement this we updated every single event monitor to allow you to specify multiple thresholds and control how you are alerted. We also updated all dashboard elements, network diagram displays and the structure of the interface itself to give you a clear view of multi-level status.
The end result gives you beautiful color-coded displays and an at-a-glance ability to identify and prioritize issues.
Timing Flaw Discovered in Windows Ping Utility
It’s not everyday that you discover a flaw in a core networking component of a major operating system, but that’s just what happened here at FrameFlow last week. The command line “ping” is the workhorse of network and server monitoring. It’s the basic test that any sysadmin will use to determine if a remote system is alive and responding to network requests. As we investigated in more detail we were even more surprised to discover that this bug is deep in the Windows API and affects pretty much any program that needs to run ping tests.