Posted on October 5th, 2015
Today I released a new build of Overseer, 5.0.163. This version fixes a problem that some people experienced with the Overseer service not starting. This ended up being a Windows-system-level validation of the certificates used to sign Overseer which would time-out on some systems(particularly those without internet connections). This fix disables the automatic-validation of the certificate when starting the Overseer service.
Posted on April 7th, 2015
Hi. It has come to my attention, through Google Adwords support, that some people are apparently unable to find how to un-install Overseer. I can’t believe that the smart users of Overseer(or other system-administrator software) wouldn’t know how to un-install software using the built-in mechanism for Windows(or the link added to their start menu), but Google insists they needed instructions posted on the website, regardless:
- Open Windows Control Panel
- Choose “Uninstall Program”
- Double-click “Overseer Network Monitor 5.0″, and complete the process that launches.
Good luck– this might be a tough one for some.
Posted on October 24th, 2014
I’ve just released a new version of Overseer. This version adds support for ‘Telus’ as an SMS carrier. It also is the first Overseer installer and executables to be code-signed using our new code signing certificate. This was an expensive certificate to purchase, but I feel it was required due to Google and Microsoft displaying warning messages about Overseer not being ‘commonly downloaded’ to end-users scaring them away from downloading Overseer.
Posted on October 20th, 2014
I’ve just released a new version of Overseer Network Monitor, 5.0.158. This version adds a ‘start service’ and ‘stop service’ options when right clicking a Windows Service resource type. This can be useful to some if you need to force a restart of a Windows Service remotely.
Posted on February 27th, 2014
I’ve just released another version of Overseer. This version includes a few changes requested by a few customers.
The first change is to add a ‘Fail If’ type to the FTP monitoring ability in Overseer. The specific types added(in addition to the obvious FTP server unreachable/unavailable), is to count the # of files in the specified FTP directory(specified in the URL, i.e. ftp://server/directory/). This counts all files(including directories), and will fail if too many or too few files are present. This can be very helpful for monitoring to see if automated file-based processes have stopped processing for some reason.
The other changes are to add new columns. I added a “Up/Down time” to the main resource list, which shows the downtime for any resource that is down, but also shows the up-time for any resource that is online. Note that the up-time is based on Overseer’s knowledge of the resource last being down, so when you first update, the up-time might be under-stated if it hasn’t gone down recently.
In addition to the up/down time column, I added a “Disk Space %” column to the resource list view if the filter is currently on disk space resource types.
Lastly, I changed the resource list grid to save/restore column widths between runs of Overseer– so once you get your column widths set, you don’t have to keep setting them with subsequent starts of Overseer.
Posted on December 27th, 2013
One of the most frequent support requests I get, is a step-by-step guide on how to move Overseer from one computer(or server) to another. This happens for multiple reasons in production environments. Unlike some other software, moving Overseer to another server is quite easy and painless– no special license activation keys are needed, etc.– just your license key from your original install, the latest Overseer setup file, and a medium to transfer the database(network, thumb drive, etc.).
- Before getting started, it is always best to update Overseer to the latest version, available at http://www.overseer-network-monitor.com/Download.aspx. Please do this on the original computer first.
- Next, start the Overseer management application using the desktop shortcut, and click the ‘Service Running’ icon in the upper right corner to stop the service(say ‘yes’ when prompted if you really want to stop the service).
- Once the service is stopped, it’s time to export your data. Go to Tools->Backup and Restore Wizard. Follow the prompts, noting where the backup file is being placed(you can specify another location if so desired).
- Once backed up, you can get your license key information from Help->License, or ideally your original license Email.
- Now, copy the backup file you just made in step #3 to a safe location– thumb drive, network location, etc.
- Un-install Overseer from this computer.
- Install a fresh copy of Overseer on the new computer, using the same latest version you upgraded the first computer to in #1.
- Apply your license key in Help->License…
- Go to Tools->Backup and Restore Wizard, and select the option to restore your database, pointing to the file you saved off in step #5.
- Wait for the restore/import to complete(this can take a while if you have a large database). Once done, all your settings, resources, and history should be restored onto this new computer, and Overseer should start monitoring your resources from this new computer.
Posted on November 15th, 2013
I have just released a new version of Overseer, 5.0.143. This version adds a ‘Resource List’ report, which a customer requested. This report groups resources by group, and shows the name, type, schedule, notification group, last state, and last check. This can also be exported in the print preview to CSV, Excel, PDF, and more.
Also in this build, and also by request of a customer, is event log filtering by keyword. Some applications don’t properly setup event IDs, so the only way to distinguish between events is using a keyword filter. An event filter can now optionally filter by keyword. Keep in mind that this causes the entire text of the event log records to be downloaded to the Overseer computer when they’re checked, so this type of filter can slow things down– it’s best to filter by source, type, and/or event ID on any filters that you use a keyword filter, if possible.
Lastly, I’ve noticed that sometimes when deleting a resource from Overseer that has a significant amount of history(i.e. has existed for a while), the interface went un-responsive as it completed this data operation. To increase the GUI responsiveness of Overseer, I set this history deletion/housekeeping to happen in the background, allowing the user to continue working in the Overseer application.
Posted on October 23rd, 2013
I’ve just released a new version of Overseer Network Monitor. This version fixes an authentication bug with non-Microsoft FTP servers. It also adds Cellcom to the supported carriers list for SMS notifications.
Posted on October 11th, 2013
I’ve just released a new version of Overseer. This version addresses a bug that I recently became aware of that affected some people trying to monitor event logs– an error regarding “unauthorized operation” was being reported. This is fixed in this version.
Additionally, I added the ability to drag and drop resources from one group to another, making it far easier to quickly organize your resources into resource groups.
Lastly, I added a simple version check upon Overseer start. Now, when you start the Overseer application, Overseer will check the website to determine the latest version of Overseer, and prompt to update if there’s a new version available.
Posted on September 24th, 2013
I’ve just released another version of Overseer. This version fixes a problem that a customer reported with HTTP authentication. I also fixed a problem with the installer, where it wasn’t always deleting the data folder when the user clicked ‘yes’ to deleting all data.