Corner Bowl Software | Security, Compliance, Server & Log Management Software


Server Manager

Important! Install the .Net Framework 4.7.2 prior to installing Server Manager.
Files Version Date Size Platform Link
Server Manager 64 bit 5/20/2019 3:08 PM 16.60 MB .Net 4.7.2
Server Manager 32 bit 5/20/2019 3:08 PM 16.59 MB .Net 4.7.2
Server Manager 64 bit 1/22/2019 7:43 PM 16.42 MB Server 2003/.Net 4.0
Server Manager 32 bit 1/22/2019 7:43 PM 16.41 MB Server 2003/.Net 4.0
Server Manager Help File * 5/20/2019 3:05 PM 2.27 MB
* After downloading the help file, open Explorer, navigate to your Downloads directory, right click on the help file, select Properties, then check the Unblock option in the lower right corner.

Build Notes


    Fixed a critical directory watcher bug

    Mon, 20 May 2019 08:58:13 MDT

    • Previously when monitoring a directory for created, modified, moved and deleted files the trigger action threw an object reference error. This bug has been fixed.

    Updated installer to include prompt for installation directory

    Mon, 13 May 2019 10:13:44 MDT

    • Previously users were unable to set the installation directory during the initial installation. The installer now provides this option.

    Fixed several disk space monitor bugs

    Wed, 08 May 2019 08:29:50 MDT

    • Previously Disk Space Monitors that were configured to monitor specific disks that included a disk that was not found and 'Ignore disk not found errors' was selected the entire monitor would trigger an error alert. This bug has been fixed.
    • Previously when re-opening a Disk Space Monitor Template that was configured to monitor specific disks the configured disks did not display on the Disk and Shares tab until after a machine was selected in the Servers/Workstations drop-down list. This bug has been fixed.

    Fixed legacy import bug

    Mon, 06 May 2019 05:29:48 MDT

    • Previously the Log Manager, Disk Monitor and Internet Server Monitor import functions were attempting to load the legacy configuration files from the wrong directory. This bug has been fixed.

    Fixed two bugs

    Mon, 22 Apr 2019 02:22:20 MDT

    • Previously when shutting down the service, if an Account Lockout Report was running the report did not shutdown. In cases where numerous servers were assigned to the report this caused the service to appear as though it hung during shutdown. This bug has been fixed.
    • Previously when displaying consolidated logs host names that had aliases assigned to them did not display the alias in the log viewer header but instead displayed the actual hostname or IP. This bug has been fixed.

    Fixed UI bug

    Wed, 17 Apr 2019 09:51:01 MDT

    • Previously when updating a Syslog or Text Log Consolidation Template with a different Log Entry Retention Policy Template and no other updates were made the UI did save the update. This bug has been fixed.

    Fixed a backup configuration bug

    Tue, 16 Apr 2019 01:34:31 MDT

    • Previously when manually backing up the configuration if the previously backed up directory is on a disk that is no longer accessible, the backup function threw an 'Access to the path' error. This bug has been fixed.

    Fixed a Server 2016 Logon Session Report bug

    Fri, 12 Apr 2019 08:16:56 MDT

    • Thanks to several customers for reporting a bug in the Windows Server 2016 Logon Sessions report I have fixed the report. Microsoft changed the format of Event 4624 on Server 2016. The parsing code has been updated to support Server 2016 - 2003.

    Fixed critical licensing bug

    Wed, 03 Apr 2019 10:02:32 MDT

    • In certain online instances licensing was lost. This bug has been fixed.

    Added detail to log messages

    Thu, 28 Mar 2019 09:39:26 MDT

    • Previously when removing or archiving consolidated log entries, the output messages did not always include the log information and when it was included, the log name was embedded within the message making it difficult to read within the output view. The Log Entry Retention Policy function now includes the log name in front of each message separated by a dash enabling users to more easily identify which log each message is associated with.

    Added verbose information to licensing validation

    Sat, 16 Mar 2019 10:58:56 MDT

    • Previously if a license was copied from another installation or the user registered while logged into a VPN, the license validation process did not log the MAC address contained within the license.xml file. The validation process now logs the invalid MAC address to the service log file and explains the issue in hopes users can self-diagnose and resolve the issue on their own.