Support & Downloads

Release Notes for GSX Monitor

GSX Monitor    12.0.0 : Release Notes
November 15, 2016

New Features:

GSX Monitor now supports End User Experience Analysis for:

  • Exchange Online
  • Skype for Business Online
  • SharePoint Online

GSX Monitor now supports Microsoft ADFS Proxy monitoring.

GSX Monitor now supports Microsoft Exchange 2016 monitoring.

 

New Features [Robot User]

  • Remote deployment: Robot Users can be easily deployed in critical monitoring locations. They update automatically and are always synchronized with the centralized version at the Manager level.
  • Robot User Scan results: Centralized alerting.
  • Optimization of the Robot User hard disk footprint.
  • Robot Users schedule and deployment persistence.
  • Garbage collection: configurations which are unused or not referenced anymore by the Manager, are automatically unscheduled and removed from the Robot User.
  • Deployed Robot Users continue to do all their tasks on the hosts where they were deployed regardless of being logged in the system or not.

 

New Features [GSX Monitor]

  • Connector Scanning: scanning frequency selection can be provided using the scheduler.
  • Connector Architecture: GSX Monitor automated backups now include Connector’s configuration.
  • Connector Templates: it is now easier to replicate a configuration on multiple similar instances with templates.
  • Connector Architecture: traces facilitate debug issues related to deployment or scanning.
  • Connector Architecture: Robot User scan results are visible in GSX Gizmo.
  • Connector Architecture: GSX Monitor status is visible in GSX Gizmo.
  • Licensing: the number of allowed Robot Users is controlled.

 

Fixed Issues:

  • Alert Profiles: in certain circumstances, dialog boxes are not displayed properly.
  • Domino Spot Check Report: messages about Database quota monitoring are incorrect.
  • Domino Spot Check Report: there is no alert when Domino Agent errors are detected in a message box.
  • GSX Monitor Alerts: unable to change the event severity for pending mail threshold.
  • IBM Connections: URL Get Latency time.
  • IBM Connections: now able to properly scan URLs not secured via https.
  • IBM Connections: added URL Alerts retries.

Posted on Nov 21, 2016

GSX Monitor    11.2.2 : Release Notes
August 18, 2016

Fixed issue:

  • Mail routing scenario probes: the unique key is no longer added to the subject line when using the Domino sending method.

Posted on Aug 18, 2016

GSX Monitor    11.2.1 : Release Notes
August 8, 2016

New Features:

  • GSX Monitor now supports Microsoft ADFS monitoring.
  • GSX Monitor now supports Microsoft Azure AD Connect monitoring.

 

Improvements:

  • Exchange servers: DAG scanning performance is improved.
  • Microsoft Active Directory monitoring performance is improved.

 

Fixed issues:

  • If the primary SMTP gateway is down, GSX Monitor sends an alert every minute until the pending mail is deleted from the Mail Viewer queue.
  • High CPU load on SharePoint servers when GSX Monitor is inquiring for ‘Version’.
  • Domino Spot Check Report: the Agent monitoring takes too much time.
  • A loading issue can occur on graphs and scenario results.
  • License viewer: the activation message box is unclear.
  • Sametime scanning is reported down with the error message ‘WAS Node down’.
  • The item menu ‘ Copy tooltips > All ’ is not available for Skype for Business.
  • Exchange Spot Check Report: mailboxes report is empty.

Posted on Aug 8, 2016

GSX Monitor    11.2.0 : Release Notes
June 14, 2016

New Features:

  • GSX for Microsoft Windows Server
  • GSX for Microsoft Skype for Business
  • GSX for IBM Connections
  • GSX for IBM WebSphere

In addition to that, this version contains all the new functionalities released recently. That includes:

  • GSX for Microsoft SQL Server
  • GSX for Microsoft Active Directory
  • GSX for Microsoft Exchange Online Network Latency Diagnostic
  • GSX for Cisco IronPort
  • GSX for IBM DB2

 

Improvement:

  • It is now possible to specify a ‘Default Organization’ at GSX Monitor first launch.

 

Fixed issues:

  • Domino Log Scanning using Scheduler may not work correctly (for older GSX Monitor migrated configurations).
  • SNMP trap description is empty for Domino critical log alerts.
  • When scanning manually (Scan now) a Domino server, an error can occur in some cases.

Posted on Jun 14, 2016

GSX Monitor    11.1.2 : Release Notes
April 25, 2016

Fixed issues:

  • In large environments, Spot Check Report for Exchange Online is not returning full results when a connection exception occurs.
  • SNMP trap summary is empty for Domino dead or pending email.
  • Editing a Lync server template can disrupt the User Interface.
  • In certain cases, ActiveSync Spot Check Reports are failing when special characters are used.
  • Soft MCU REST API port is not configurable for Sametime VMCU builds after August 2015.

Posted on Apr 25, 2016

GSX Monitor    11.1.1 : Release Notes
February 29, 2016

GSX Monitor

Fixed issues:

  • Domino Alerts are not reported to GSX Analyzer.
  • Spot Check Report issue when the mailbox name contains a single quote character.
  • Monitor Main View settings (number of lines per row) are not saved after change.
  • A Spot Check Report is not sent if at least one of its conditional report does not specify a distribution list.
  • Domino log scan settings revert back to 1 day or daily when switched to weekly or daily with 7 days interval.
  • SNMP Trap severity is not taken into account and set to 0.
  • SharePoint and BES 5 scanning interval are not respected.

Posted on Feb 29, 2016

GSX Monitor    11.1.0 : Release Notes
January 25, 2016
 
New Features:
  • New Alerts on Lync Performance counters.
  • New Alerts on Lync Mediation and Edge Performance counters in GSX Analyzer.
  • Exchange Hub Transport Queues Statistics in Statistics view / Alerts / Tooltip. 
  • Exchange Mailbox Database additional Statistics in Statistics View.
  • New column for Exchange Spot Check Report Mailbox characteristics.

 

Fixed issues: 
 

  • Configuring the Scheduler into a new Alert Profile is not possible.
  • A crash could occur when updating DirSync PowerShell Port.
  • Fixed command line issue when installing GSX Monitor as a Windows Service.
  • The scheduler does not allow to go beyond year 2015.
  • Sametime 9 Community Server Statistics Collection issue when the path to the STLog file is not configured. 
  • Fixed PowerShell memory leak issues.

Posted on Jan 25, 2016

GSX Monitor    11.0.2 : Release Notes
November 30, 2015
 
GSX Monitor

New Features:

  • Support Lync Edge Role.
  • Support Lync Mediation Role.
  • Enhanced support of Lync authentication schemes.

Fixed issues:

  • Fixed issue with the GSX Monitor Licence Viewer not starting when the configuration database is missing.
  • Fixed issue when the escalation alert was not triggered.
  • Fixed issue when sorting DirSync Windows by status.

Posted on Nov 30, 2015

GSX Monitor    11.0.1 : Release Notes
November 3, 2015
 
GSX Monitor

Fixed issues:

  • Fixed issue when the trial version of GSX Monitor did not start on VM Ware.
  • Fixed UI issue when changing Spot Check Report category.
  • Windows services names are now listed in the Windows Services alerts body.
  • Default port for Exchange PowerShell endpoint is now correctly set to 80.

Posted on Nov 4, 2015

GSX Monitor    11.0.0 : Release Notes
October 22, 2015
 
Windows XP and Windows Server 2003 are no longer supported.
Microsoft .NET Framework 4.5.1 is required.
 
GSX Monitor

New Features:

  • DirSync Monitoring:
    • Monitor the status of DirSync synchronization
    • Alert on DirSync critical services
    • Alert if synchronization did not occur in a reasonable timeframe

Fixed issues:

  • Fixed intermittent remote PowerShell errors while scanning Lync servers
  • Copy/Paste Disks Alerts configuration is now allowed for Lync, SharePoint and BES12 from the Server Settings view
  • Improved performance when monitoring the SharePoint Search Database
  • Fixed issue when configuring a BES12 database with a “-“ character
  • BES12 Spot Check reports are now accessible when GSX Monitor is modularized without Domino and Exchange
 

Posted on Oct 22, 2015

GSX Monitor    10.13.1 : Release Notes
September 8, 2015

Improvements:

Date format has been improved in BES 12 Spot check reports. 

Fixed issue:

  • Exchange 2010 and 2013 could be reported as Down due to a remote PowerShell exception.
  • Results of the Lync synthetic transaction monitoring now include the exact reason for test failure.
  • When monitoring Lync, a count is now only performed on the Lync users, instead of fetching the complete list and perform a count afterwards. 

Posted on Sep 8, 2015

GSX Monitor    10.13.0 : Release Notes
July 27, 2015

New Features:

  • Spot Check Reports can now be configured with powerful condition and filter features:
    • Report entries can be filtered down with one or several conditions (e.g. Devices from NYC office that don’t sync)
    • Reports can be restricted to a specific number of entries (e.g. Top 50 on mailbox size)
    • Custom formulas (combine, exclude, etc.)

Each configuration can contain one or several reports based on these custom criteria. Each report can be sent to common or dedicated distribution lists.

  • New BES12 Spot Check Reports with detailed information about BES12 devices.

Improvements:

  • New statistics on Lync Edge servers (Authentication failures, Allocation failures, Packets dropped, connections, etc.)
  • New statistics on Lync Mediation servers (failed calls, Load call failure index, Media connectivity check failure, etc.)

Fixed issue:

Traveler device and user statistics for servers in a pool are now reported at the pool level, and no longer at the server level. 


Posted on Jul 27, 2015

GSX Monitor    10.12.2 : Release Notes
June 29, 2015

Fixed issues:

  • Performance counters were not correctly retrieved when the remote server was in a locale different from US. 
  • Domino templates are now correctly loaded even in case of incomplete save.
  • The ActiveSync scenarios are now working as expected on Office 365. 
  • Traveler user alerts are no longer played at the server level if it belongs to a Traveler pool.

Posted on Jun 30, 2015

GSX Monitor    10.12.1 : Release Notes
May 28, 2015

New Feature:

Meetings and Tasks creation can now be simulated in ActiveSync Scenarios.

Improvements:

  • From the Alerts view, entries related to spot check reports or change monitoring have been removed as it was not relevant to have them displayed as alerts.
  • In the Exchange and ActiveSync scenario views, the user name and password fields are now displayed in the settings grids.
  • Improved Modularization and Email Service settings stability.

Fixed issues:

  • DatabaseAvailability and DatabaseRedundancy Replication Health Checks are irrelevant and have been removed from the scanning of Exchange 2013 Mailbox servers being ina DAG.
  • The Domino Disk Space Warning LED is now working as expected.
  • A port scanning timeoutcould lead to a crash.
  • An error could occur when configuring an Exchange Scenario containing a Create Email action with the send email option enabled.
  • Lync version and build numbers are now reported in Daily, Weekly and Monthly reports.
  • The default scanning frequency for Exchange clusters is now set to 5 minutes. 

Posted on May 28, 2015

GSX Monitor    10.12.0 : Release Notes
April 28, 2015

New Features:

  • It is now possible to create Spot Check Reports for Exchange Online organizations, including Mailboxes, Public Folders and ActiveSync Devices reports.
  • A new ActiveSync Scenario view allows to simulate end users ActiveSync activities such as opening a mailbox, creating emails, resolving users, checking user availability, and monitor the execution time and status of these scenarios.
  • GSX Monitor now supports IBM Traveler 9.0.1.3 monitoring.

Improvement:

The GSX Monitor Settings windows have been redesigned.

Fixed issues:

  • The Domino "Home Server" is obsolete and has been removed from GSX Monitor settings.
  • While fetching Traveler user statistics via SQL, if the primary configuration is failing, GSX Monitor now checks if the secondary (mirror) configuration is enabled before trying to use it.
  • After a change in the Modularization, the Email Service settings now need to be validated (or updated if necessary).
  • The Full backup option is now working as expected even when the destination folder is too large.
  • In Exchange Spot Check Reports, the sort on the report columns is now working properly.
  • The Sametime "average access time" values are now correctly displayed in the Server Statistics view.
  • In some rare cases, Domino memory related statistics could be incorrect.
  • Audit Report details containing special characters are now displayed correctly.

Posted on Apr 28, 2015

GSX Monitor    10.11.1 : Release Notes
March 19, 2015

New Features:

  • BES 12 server and pool monitoring now available in GSX Web Enabler.
  • Lync monitoring now available in GSX Web Enabler.
  • Sametime 9 last improvements now available in GSX Web Enabler.

Improvements:

  • It is now possible to create custom Sametime WebSphere nodes.
  • The GSX Monitor post-install process has been improved and the wizard now includes the notes.ini file path definition and the GSX Analyzer stations configuration.
  • The Exchange Replication Health settings can now be done before the server is added to a DAG, making the configuration process easier.
  • A new variable representing the error date and time has been added to SNMP Traps.
  • In some rare cases, and when sending email alerts via Domino, the alert subject could be truncated.
  • Improved GSX Web Enabler Main View properties with latest monitored platforms.

Fixed Issues:

  • Scanning Exchange Windows services containing a $ sign generated wrong status.
  • The Exchange Mailbox Database status is now displayed correctly when a database is not Mounted nor Healthy.
  • A new shortcut has been added to the GSX Monitor installation to help deploying the License Component when it has not registered correctly during the install or upgrade process.
  • In certain cases, when monitoring a station which is not part of the same domain as the targeted SQL server, the SQL test connection could fail.
  • When scanning a Traveler pool, the alert on percentage of users not synchronized is now displayed correctly.
  • In Exchange Active Sync Spot Check Reports, some dates were not correctly displayed because an extra UTC conversion was performed.
  • At first start, the Domino email configuration can now be set up if any IBM platform is selected in the modularization, even if Domino is not.
  • The Work Connect Notification Service setting is now saved correctly when editing the BES cluster configuration.
  • When testing connection to SharePoint PowerShell, the "Object reference not set to an instance of an object" error message has been replaced by a more accurate message.
  • Fixed a scale issue in Exchange Disk space graphs (free space / used space).
  • The application could crash when the BlackBerry version selection from the Server Settings view was not correct. 

Posted on Mar 19, 2015

GSX Monitor    10.11.0 : Release Notes
February 23, 2015

New Features:

  • Sametime 9 Audio/Video components integration (VMCU and VMGR servers monitoring).
  • BlackBerry 12 Pool monitoring.

Fixed issues:

  • Sametime alert on Windows Services down has been reviewed to improve readability.
  • Improved formatting on Domino Change Monitoring alert emails.
  • While scanning URLs, some error messages were inaccurate.
  • While configuring URLs, test connections were only using SSL3 to make SSL handshake. Since Poodle fault, this feature now only uses TLS1.
  • Refreshing Windows Services status works fine when creating a BlackBerry 12 server from the wizard.
  • Template for BlackBerry 12 can now import correctly a BES 12 server configuration.

Posted on Feb 23, 2015

GSX Monitor    10.10.2 : Release Notes
January 26, 2015

Fixed Issues:

  • Fixed issue of Database corruption for Exchange and Lync monitoring during upgrade to 10.10.1 
  • Outlook Web Services can no longer be selected in the Exchange 2013 Sever Settings grid, as expected.
  • Scanning a Traveler pool URL is now using correct parameters for SSL (SSL3 from .ini file or TLS by default).
  • Exchange 2007 Windows Services are now correctly retrieved using WMI.
  • Some Exchange and Lync statistics were inaccurate and not sent to GSX Analyzer in Daily, Weekly and Monthly reports.

Posted on Jan 26, 2015

GSX Monitor    10.10.1 : Release Notes
December 19, 2014

Improvements:

  • When scanning an Exchange DAG, it is now possible to exclude lagged database copies from the DBLogCopyKeepingUp and DBLogReplayKeepingUp results.
  • When monitoring Exchange Hub servers, you can now set an advanced scanning mode with dedicated thresholds and alert profiles for each queue type.
  • Exchange Disk Space statistics for usage and latency are now detailed in the Statistics view.

Fixed Issues:

  • When scanning Exchange 2010, the Test-ReplicationHealth test was not triggered if the Hub role was not selected in the server configuration.
  • The Server Guard options on Domino servers could return empty error messages in case the remote commands were not enabled.

Posted on Dec 19, 2014

GSX Monitor    10.10.0 : Release Notes
November 12, 2014

New feature:

Support of BlackBerry 12 monitoring. GSX Monitor tests the connectivity status of the following components:

  • Active Sync endpoints, to make sure the users are able to synchronize their device.
  • SQL Database status, as well as the Database size
  • SRP to ensure connection from your BES servers to the BlackBerry NOC (Network Operations Center).
  • Windows Services on remote servers
  • Dedicated BES 12 Statistics view with:
    • System status
    • Active sync end points status
    • Information on user and devices

 

Fixed Issues:

  • In Alert configuration, the "Test email" button always display a message box (for success or failure).
  • Obsolete Exchange statistics  have been removed from the Graphs view.
  • An error could occur when initializing the Lync Statistic view.
  • Exchange and Lync Windows Services are now retrieved using exclusively PowerShell.
  • In some cases, localized Exchange performance counters were not retrieved.
  • Sametime statistics collection method was not saved correctly when configuring a new Sametime 8 server.
  • The prioritization of alerts on the Domino System LED has slightly changed: Tasks "down" has now priority on Disk Space "in warning".
  • A memory leak could occur when performing IBM Notes scanning operations (Domino, Domino Performance, Change Monitoring, etc).
  • In some rare cases, and when sending email alerts via Domino, the alert subject could be truncated.
  • The Exchange Mailbox status was wrong even when mailbox databases were down.

Posted on Nov 12, 2014

GSX Monitor    10.9.1 : Release Notes
October 15, 2014

Improvements

  • Lync simultaneous server monitoring performance has been improved.
  • A DomainUsername field has been added to the Lync Test Users configuration, so that tests no longer fail when the UPN and the SIP addresses are different.
  • Improved the error message warning that GSX Monitor is already running in another instance.

 

Fixed Issues

  • Due to support of Unicode in Domino scanning processes, an error could occur while processing Domino statistics buffer.
  • When configuring the communication between GSX Monitor and the Remote UI, it is now possible to select a different Remote UI IP address if GSX Monitor is not able to determine which one has to be used to ensure the connectivity between the Remote UI and GSX Monitor.
  • Dedicated URL debug files were generated in the wrong folder.
  • All Traveler user alerts are now triggered as expected.
  • Editing a SharePoint server from the Server Settings view is now done through the SharePoint wizard, fixing configuration issues related to SQL.
  • Sametime Windows Services reported in error are now displayed in the LED tooltip.
  • An unhandled exception could occur when GSX Monitor was launched while transfering data to GSX Analyzer.
  • The Exchange Database Failover alert can now be copy-pasted from one configuration to another in the Server Settings view.

Posted on Oct 15, 2014

GSX Monitor    10.9.0 : Release Notes
September 15, 2014

New features

Support of Microsoft Lync monitoring. GSX Monitor tests the following Lync services:

  • Front-end service
  • Web application service
  • Instant Messaging Service
  • VoIP (Voice over IP) service

GSX Monitor retrieves Lync performance counters at the System level and at each Service level.

Improvements

  • In GSX Web Enabler, the Traveler system LED was always split in two, even when the server was not in a Traveler pool.
  • The Negotiate authentication method can be used on the Microsoft PowerShell endpoint (for multi-tenant environments, when domains cannot be trusted and when basic authentication cannot be used).
  • Several Mail Routing cycles can now run in parallel; you no longer need to wait for a cycle to complete to start another one.

Fixed issues

  • A memory leak could occurs while sending emails in Port job and in Mail Routing.
  • SMS alerts containing unicode characters are limited to 70 characters.
  • The "Enforce password protection for configuration changes" option now protects Global Preferences, Monitor OnTheFly Preferences and Alerts Preferences.
  • In Mail Routing configurations, the SMTP Sender option can now be copy/pasted.
  • In Alert configuration, the "Test email" button always displays a message box (for success or failure).     
  • When scanning Sametime, an issue could occur while reading some Domino document fields.
  • Some Domino statistics were not computed just after the server had been configured.
  • The Default Home Server is no longer empty when GSX Monitor first starts.

Posted on Sep 15, 2014

GSX Monitor    10.8.2 : Release Notes
August 12, 2014

Improvements:

  • Non relevant debug traces are no longer logged in the EventLog.
  • The SSL / TLS encryption is now supported in SMTP port scanning.

Fixed issues:

  • Exchange Mailbox Database statistics were not correctly computed before being sent to GSX Analyzer.
  • When performing a Test connection in an Exchange configuration, the PowerShell Access Time  is now computed correctly.
  • GSX Monitor is now able to monitor more types of URLs, including redirections.
  • Errors no longer occur when using a Notes ID file that is not password protected.
  • The Traveler probes are now correctly removed from 'Sent Items' while performing mail routing.

Posted on Aug 12, 2014

GSX Monitor    10.8.1 : Release Notes
July 7, 2014

Fixed issues:

  • Fixed an issue with Mail Routing probes that were not working as intended when the GSX Probe Key was located in the Body field of an email rather than in the Subject field.
  • Daily/Weekly/Monthly Uptime and Downtime statistics are now correctly computed for the Exchange Outlook protocol.
  • The Retry value of the Traveler HTTP Thread Usage Alert is now saved and displayed correctly when editing the Traveler server again.
  • Fixed issue in Domino log scanning: only uppercase keywords could be found.
  • When editing an Exchange Scenario containing a 'Download attachment' action, the attached item was not saved and needed to be selected again, resulting in an error message.
  • Domino Disk warning status is now correctly generated in GSX Web Enabler.
  • When scanning a SharePoint 2013 server with SNMP, the SharePoint version was not correctly retrieved, resulting in system information (RAM, CPU, etc.) not being displayed.

Posted on Jul 7, 2014

GSX Monitor    10.8.0 : Release Notes
June 3, 2014

New Features:

  • Overview for Exchange Online organizations
  • Support of SharePoint 2013 servers monitoring (plus support of Claims and ADFS)
  • Support of Sametime 9 servers monitoring
  • Ability to configure an Exchange Web Service as Email alerting service.

If the bandwidth is too low, the sending of Mail routing large attached files with EWS can be long and then result in a timeout.

  • Traveler users alerting options improved
  • Sending of Traveler Pool statistics to GSX Analyzer

Improvements:

  • All character sets (Asian, Middle East, etc.) are now supported throughout the application.
  • The configuration wizard of Domino Spot Check Reports has been redesigned.
  • The Traveler "Http thread usage" statistics is now computed as follows: (Http.CurrentConnections / Http.Workers) x 100.
  • In the Traveler Statistic View, when a server is part of a pool, the list of users of the selected server now shows the alert status of the pool instead of showing unconfigured alerts.
  • The License Information window has been reviewed for a better understanding of licenses in use.
  • The Traveler Outdated Devices alert can now be set in minutes (the previous minimum threshold was 1 hour).

Fixed issues:

  • In Exchange multi-sites environments, the Mailboxes Spot Check Report now retrieves all mailboxes correctly.
  • In some rare cases, the computation on Mailbox Database average size could be wrong.
  • SharePoint Content Databases were retrieved many times, causing performance issues on the server hosting the SQL SharePoint instance. Corresponding queries could then time out.
  • The Test Connection on SharePoint failover servers of Content DBs and Search DB is now working properly.
  • In some rare cases (with specific port number and no SQL instance defined on database), the SharePoint site list could not be retrieved from the Scenario or Performance wizards.
  • The Exchange Database Failover alert is now triggered even if the Mailbox role is down.
  • In the Traveler Statistic view, the "Total number of registered devices" is now correct when two different users synchronize a same device, and the "Last synchronisation date" is now showing the most recent sync date.
  • In the Traveler Statistics view, the "Total number of online users" statistic is now reported.
  • In Web Enabler, the SharePoint roles are now correctly displayed/hidden in the server rows, depending on the actual server role(s).

Posted on Jun 3, 2014

GSX Monitor    10.7.2 : Release Notes
March 17, 2014

New Feature:

New Exchange Spot Check Report for ActiveSync Devices connections (detailed information about connected devices, synchronization, etc.).

Improvements:

  • In the Main View, the Sametime System LED is no longer split if no Windows Services have been configured.
  • When defining size thresholds in some components' configurations, you can now choose between several values (megabyte, gigabyte, etc.).
  • Change Monitoring and Spot Check Reports configurations are no longer taken into account in the Global Outage alert.

Fixed issues:

  • In the Exchange Overview, the status of Scenario, Mail routing and Spot Check Reports configurations is now only considering enabled configurations.
  • In some cases, the Exchange scan ended up without giving any server status nor statistics.
  • When configuring a Sametime server from the wizard, the 8.5+ Specific tab could be disabled even if a version 8.5 was selected.
  • Domino Stat "Platform.Process.server" is now correctly retrieved.
  • In the Exchange Server Settings view, the "Mailbox used for Protocols checks" column is now hidden for 2013 servers, as this option is only available for 2010 servers.
  • In the Traveler Statistics view, some statistics were missing (version, mail flow, HTTP Thread, etc.).
  • Exchange CPU percentage calculation now supports multiple physical processors.

Posted on May 6, 2014

GSX Monitor    10.7.1 : Release Notes
February 6, 2014

Fixed issues:

  • Connectivity issues could occur when browsing Exchange Mailboxes' folders in Scenarios or when testing Mail Routing connection with an Exchange Web Services (EWS) configured.
  • From the Main View properties, you can now dissociate the LED color configuration of Exchange 2010 and Exchange 2013 DAG status.
  • The Microsoft.PowerShell Endpoint configuration is now available in Server Settings > Exchange Server > Scanning.
  • The Exchange DAG status computation has slightly changed, so DAGs are now considered Down when the Mailbox status of all servers is down or at least one DB is not available, and considered in Warning when the Mailbox status of at least one server is down.
  • In GSX Web Enabler, the Traveler Pool users’ status was not updated while GSX Monitor was running.
  • Fixed memory leak in GSXExchange.exe (aborting scans no longer impacts memory).
  • In the BES Statistics view, the Users Status computation could be incorrect; it is now computed differently and well rendered.
  • In the Exchange configuration wizard, you can now specify an OWA URL with an https protocol.
  • On Windows Server 2003, the Exchange configuration wizard crashed when opening.
  • In the Exchange Main View Properties, the Hub LEDs related to Delivery and Unreachable Queues have been removed to avoid any confusion with the Transport/Hub LED Status.
  • In the Exchange Server Settings view, copy-pasting CAS alerts did not copy Outlook connectivity settings.

Posted on Feb 6, 2014

GSX Monitor    10.7.0 : Release Notes
January 20, 2014

New Features:

Support of Exchange 2013 environment:

  • Autodiscover your Exchange 2013 organization with your Mailbox and CAS servers.
  • Monitor your Exchange organization and be alerted when a problem occurs at the Protocol level, Mailbox level, Transport level or Proxy level.
  • Monitor the Mail Routing within your Exchange 2013 organization according to predefined SLAs, either on physical servers or online.
  • Define Spot Check Reports on Mailbox Characteristics and Public Folders.

New Exchange Overview for On-premises and Hybrid organizations, with Scenarios and Spot Check Reports real-time status.

Exchange Scenarios: simulate and monitor user experience by checking status and execution time of day-to-day activities (compose custom scenarios among the following actions: Open Mailbox, Create meetings, tasks and folders, Download attachments from emails, Search for folders, emails, appointments and tasks).

New wizard for Exchange cluster configuration.

Monitoring of System Processes on Exchange servers.

New Database Failover alert: receive an alert as soon as a database failover occurs in the DAG.

Improvements:

  • Remote WMI is not used anymore to collect system statistics. GSX Monitor now uses exclusively PowerShell to monitor Exchange environments.
  • When connection drops that does not impact users occur on Exchange Roles (2010) or Services (2013), the alert is not issued immediately to prevent from false positives, but checks for the Business and Off hours settings instead (to get notified only when the situation gets critical).
  • To navigate more easily between views, it is now possible to display the subviews selection by clicking the view's name or icon instead of having to click the little arrow.
  • In the Traveler Statistics view, the version of the Domino server on which Traveler resides is now given.
  • Improved Scenario, Performance and Mail routing views display for configurations that are under maintenance.
  • Minor interface and labels improvements.

Fixed issues:

  • In the Main View Properties, irrelevant Custom statistics have been removed from selection.
  • SRP (Server Routing protocol) status was not correctly displayed in the BES Statistics view when the server name could not be resolved.
  • The "OWA Average Access Time Threshold" alerts is no more sent when OWA Protocol is not selected in the server configuration.
  • The Exchange Hub role SMS alerts now contains the Exchange server name.
  • In the Exchange 2010 server configuration wizard, the validity of the specific OWA URL is now checked.
  • If Database conversion fails (from FDB to SDF), an error message is now displayed.
  • SharePoint SQL error string is now displayed in the Main View LED.
  • In the Exchange Overview, the DAG status is not given until the servers’ status is reported.
  • In some cases, the percentage of Traveler users alerts could be superior to 100%.
  • Due to PowerShell authentication, only 2010 and 2013 servers can be selected in Spot Check Reports and Exchange Overview configurations. Exchange 2007 servers have then been removed from selection.
  • Exchange statistics containing dates (in Statistics View, Spot Check Reports, etc.) are now displayed in Coordinated Universal Time (UTC).
  • Improved some email alerts content.
  • When a log scanning failed on a BES server due to unexpected errors, the log scanning on other BES servers were also considered down.
  • Exchange availability (up time and down time) sent from GSX Monitor to GSX Analyzer could be inaccurate due to Performance Counters being down.
  • In the Domino Performance graph properties, the "Database Access Time" label was missing.
  • SNMP traps are now sent correctly to SCOM 2012 when GSX Monitor is running as a service.
  • GSX Monitor is now stable with IBM Notes client version 9.
  • When a Traveler pool database was hosted on a DB2 server, the Pool scanning was not working if the login used was different from the DB2 schema used for the Traveler database.
  • Exchange System drives were sometimes not taken into account for Disk space checks.

Posted on Jan 21, 2014

GSX Monitor    10.6.2 : Release Notes
December 2, 2013

Improvement:

  • Change Monitoring can now report on documents errors while scanning.

Fixed issues:

  • In Domino Spot Check Reports, ACL Monitoring alerts (e.g. cannot access to a database) are no longer triggered when the expected behaviour is back to normal.
  • In names.nsf, users defined with a Domino server name without any domain name (example "GSX01" instead of "GSX01/GSX") are no longer reported in the "Orphan mailbox" rule.

 


Posted on Dec 3, 2013

GSX Monitor    10.6.1 : Release Notes
October 28, 2013

New Feature:

In Mail routing configurations, mail probes can now be sent to an IBM Traveler device.

Improvement:

The SNMP module is now by default enabled during the installation.

Fixed issues:

  • A memory leak could occur while running Exchange Spot Check Reports too frequently.
  • The number of Spot Check Reports configurations is now correctly displayed in the license information.
  • In the Ports Configuration wizard, the Search option is no more prompting if the LDAP configuration is disabled.
  • In Exchange monitoring, when a server was considered in timeout, it could result in various inconsistent statistics (mailbox databases disappeared from stat view, ...)
  • The Change Monitoring reports on Domino Program Documents only displayed one update while several updates actually occurred.
  • Using a server distribution list for Traveler clusters is now working as expected.
  • When at least one system critical Windows Services is down on a mailbox server belonging to a DAG, it has impacts on mailbox databases in the corresponding DAG Statistics view.

Posted on Oct 28, 2013

GSX Monitor    10.6.0 : Release Notes
September 17, 2013
 
New Features:
  • Traveler High Availability (HA):
    • You can now create Traveler pools monitoring configurations and alert either at the pool level or at the server level.
    • Status on High Availabiity, SQL DB and IP Sprayer can be checked from the Traveler pool statistics screen.
  • Mail Routing:
    • New configuration wizard.
    • Exchange mail routing using Exchange Web Services (EWS).
    • GSX Monitor can now detect, report and alert on mounting points of Exchange servers and SharePoint servers (except with SNMP scanning method).
  • New SCOM 2007 Management Pack:
    • Alerts are now better sorted in the dashboard, depending on their criticity (information, warning and critical).
    • Alerts are automatically marked as closed when the 'Back Up' alert is triggered.
  • New GSX Monitor licensing system with detailed information per platform and/or per user.
 
Improvements:
  • A menu in GSX Monitor now allows you to launch the Modularization after restart.
  • The GSX Monitor Station Name can now also be given in the Modularization at first GSX Monitor startup.
  • You can now link a Port configuration to a Domino server configuration from the Wizard.
  • Alerts on Traveler users can now be configured for one device or for all devices.
  • Web Enabler is now by default enabled in Trial licenses.
  • The list of users that have not synchronized their devices recently is not displayed in the alert email.
  • License information window now display more information about evaluation version.
 
Fixed issues:
  • Deleting a BES configuration from the Main View could fail.
  • An exception made Sametime Services scanning freeze, resulting in all servers being down.
  • The Traveler users 'back up' alert is no more sent when a deleted user is configured.
  • Compacting GSX Monitor DB every 2 months (at GSX Monitor start up) is no more necessary, since SQL CE does not need it.
  • Error messages from a non-accessible BES server can now be closed (in BES Statistics and Wizard screens).
  • In a Spot Check Report configuration, GSX Monitor can now retrieve Exchange Mailboxes whatever the Mailbox Database name format is.

Posted on Sep 19, 2013

GSX Monitor    10.5.5 : Release Notes
September 2, 2013
 
If you upgrade from a version prior to 10.5 and if you are monitoring SharePoint servers including a backend SQL server configuration (which do not reside on the same station), a dedicated SharePoint row will then be created in the Main View for the SQL Server configuration.
 
 

Improvements:

  • Additional checks for the station OS have been added both at install level and at the Prerequisites checks level.
  • Some messages in email alerts have been corrected to be more accurate depending on the alert type.

 

Fixed issues:

  • GSX Monitor can now perform log scanning on BES and SharePoint servers in non-trusted domains or from a Workgroup.
  • The definition of outages statistics has been improved in the Periodic Statistics screen.
  • All running background processes are now checked during an upgrade of GSX Monitor.
  • More detailed information is provided when errors raise in PowerShell prerequisites.
  • Some labels were not accurate in the MIB details window.
  • The Mailbox characteristics spot check report now generates an accurate number of mailboxes.
  • Scanning Active Directory ports with SSL no longer consumes a lot of RAM.
  • SharePoint test connection could display “Invalid query”.

Posted on Sep 9, 2013

GSX Monitor    10.5.4 : Release Notes
July 23, 2013

 

If you upgrade from a version prior to 10.5 and if you are monitoring SharePoint servers including a backend SQL server configuration (which do not reside on the same station), a dedicated SharePoint row will then be created in the Main View for the SQL Server configuration.
 
 
Fixed issues:
  • Any Public Folder 'Spot Check Report' will be reported "available" and all fields populated if the PowerShell connection to the Mailbox server is available, even if no Public Folder is present on this server. Retrieving statistics for Public Folders is now possible on more than 1000 Public Folders.
  • Editing an existing Traveler configuration could stop Domino servers scanning.
  • An exception could make SharePoint and Exchange scanning freeze.
  • The SharePoint SQL Test Connection now establishes connections to failover databases in case of connection failures.
  • SharePoint Disk Space alerts are now detailed correctly in the Main View LED tooltips.
  • SharePoint Templates are now correctly loaded at GSX Monitor startup.

Posted on Jul 25, 2013

GSX Monitor    10.5.3 : Release Notes
May 30, 2013

If you upgrade from a version prior to 10.5 and if you are monitoring SharePoint servers including a backend SQL server configuration (which do not reside on the same station), a dedicated SharePoint row will then be created in the Main View for the SQL Server configuration.

 

Improvements:

  • Domino server names are now alphabetically sorted in wizards' dropdown lists.
  • Updated WMI query on DomainController/DomainControllerName to request DnsForestName with the domain configured in GSX Monitor.
  • You can now search and sort SharePoint sites while configuring SharePoint Site Performance or Scenarios.

 

Fixed issues:

  • The number of configured scenarios in the tree view is now updated after a configuration deletion.
  • In certain cases, SQL queries could take longer than expected and may finally time out (SQL role is then reported Down). To prevent this, you can now set a timeout on the SQL query execution.
  • When editing a Change Monitoring configuration, the selected Directory rule is now a configured rule.
  • Exchange Overview Test Connection now checks that local PowerShell Execution Policy is not restricted.
  • SharePoint Sites are now listed in Scenario and Site Performance configurations even if one of the Content DBs is not available.
  • The "Outlook" CAS Check now specifically targets the CAS server instead of using the CAS Array URL for testing access to mailbox via RPC over HTTP or TCP.
  • Test connection failed when BES SNMP Community was not Public.
  • Domino buffer is now correctly translated, even when too large.
  • An error occurred if more than 16 CAS servers were added to a CAS Array. The limit is now set to 32 servers.
  • In DAG/CAS Array down alert, the "down since" value could be erroneous and servers in timeout are now highlighted.
  • BES logs Scanning now uses the correct server name from the BES configuration.
  • SQL status did not reflect when a SharePoint Search DB was missing.
  • When Outlook Web Services were enabled, the CAS status could be reported Up when some CAS check were failing. The Outlook Web Services tests now use the specific mailbox when configured. Exchange Server tooltip now displays all the failing CAS checks.
  • When a timeout occurred while reading Sametime logs, the Sametime Login statistics were not reported correctly.
  • If you use Exchange specific test mailbox and if you have selected OWA and encountered unexpected issues on OWA checks (resulting in CAS Down status), you can now enter a specific URL which targets the OWA virtual directory of this CAS server.
  • You can now easily copy/paste Scenario configurations.
  • BES log reports are sent to GSX Analyzer even if the distribution list in GSX Monitor Preferences is empty.
  • Traveler users can now be removed from a configured Traveler server.

Posted on May 30, 2013

GSX Monitor    10.5.2 : Release Notes
April 30, 2013

If you upgrade from a version prior to 10.5 and if you are monitoring SharePoint servers including a backend SQL server configuration (which do not reside on the same station), a dedicated SharePoint row will then be created in the Main View for the SQL Server configuration.

 

Fixed issues:

  • An error occurred if more than 16 CAS servers were added to a CAS Array. The limit is now set to 32 servers.
  • On Exchange Mailbox servers configured in a DAG, you can now set a "Transient Parameter" which specifies (in minutes) how long the queue lengths can be exceeded before the queue length tests are considered to have failed.
  • The threshold on Mailbox database size is now limited to 999.999.999 MB (previously 999.999 MB)
  • An error message could raise while using a template of SharePoint server configuration.
  • Traveler 9 scanning reported servers down due to Traveler task and HTTP task renaming.
  • SharePoint servers are now properly sorted in the Statistics view depending on their role.
  • Any Public Folder 'Spot Check Report' will be reported "available" and all fields populated if the PowerShell connection to the Mailbox server is available, even if no Public Folder is present on this server.
  • While scanning Exchange Mailboxes in large environments (e.g. 50,000 mailboxes), the GSXScanEngine.exe process could leak to use more than 1GB of RAM.
  • Sametime WAS scanning is no more reported down when initializing.
  • The Populate function on SharePoint Aliases is now working properly when configuring SharePoint SQL servers.
  • In the Statistics view, the disk space statistics were not reset properly on SharePoint SQL servers.
  • In some cases, disk space information was not displayed correctly in Web Enabler LED tooltips.
  • The deleted Traveler devices were still displayed in the Traveler Statistics view.

Improvements:

  • Install link depends on the type of the Operating system : workstation/server.
  • You can now exclude specific Exchange Databases from DAG checks (e.g. for databases used for archiving purposes).

Posted on Apr 30, 2013

GSX Monitor    10.5.1 : Release Notes
March 28, 2013

If you upgrade from a version prior to 10.5 and if you are monitoring SharePoint servers including a backend SQL server configuration (which do not reside on the same station), a dedicated SharePoint row will then be created in the Main View for the SQL Server configuration.

 

Fixed issues:

  • SharePoint scanning failed when SNMP was configured.
  • An exception could freeze the application while scanning BES servers.
  • WMI Queries on specific namespaces caused the NLB Monitoring to be constantly failing.
  • Domino Logs scanning now takes into account any modification of the server maintenance.
  • Domino Logs scanning is now working properly.
  • It is now possible to disable SQL configuration to avoid Database connections when scanning BES servers.
  • In Web Enabler, replication reports were not updated properly.

Posted on Apr 30, 2013

GSX Monitor    10.5.0 : Release Notes
March 19, 2013

If you are monitoring SharePoint servers including a backend SQL server configuration (which do not reside on the same station), a dedicated SharePoint row will then be created in the Main View for the SQL Server configuration.

 

New Features and Improvements:


SharePoint Monitoring Renewed:

  • New View: SharePoint Overview with Farm Automatic Discovery.
  • SharePoint servers are now monitored by role (Web-Front-end, Application and SQL).
  • Availability Statistics per SharePoint server role.
  • SharePoint Availability and Periodic statistics for Content Database.
  • New alerts on growth and size for Site Collections and Content DBs.
  • Ability to specify which document to upload in SharePoint document upload Scenario.

Domino Disk Space: a Warning threshold can now be defined to get alerted before critical Disk Space alert is triggered.

Improved Post-install User experience:

  • Stations requirements now checked during the install.
  • New Wizard with Modularization, Prerequisites Checks and Email Server Configuration.
  • Prerequisites Documentation can be consulted in case Prerequisites fail.
  • New Window to create Server Configurations at GSX Monitor’s first launch.
  • Getting Started with your Servers monitoring: Platform Specific Documents.
  • Test Connections are now user-friendly and show a Troubleshoot link in case a prerequisite on your monitored servers is not fulfilled.
  • Product Documentation is now provided in HTML format and allows users to send feedbacks.

Main View improvements:

  • New Server Configurations window with Ctrl+N and at GSX Monitor’s first start
  • Copy/Paste Tooltips by right-clicking a row or doing Ctrl+C / Ctrl+V.
  • Delete the selected server(s) from the Main View by right-clicking a row or pressing Del key.
  • Navigate through your Main View rows using your keyboard arrow keys.
  • Open Server Statistics directly from the Main View by pressing Ctrl+S.

Exchange Spot Check Reports:

  • Public folders.
  • Mailbox characteristics.

Ability to use Regular Expressions in Domino, BES and SharePoint Log scanning.

The Firebird Database (monitor.fdb) is replaced by a SQL CE Database (monitor.sdf).

IBM Traveler Devices Statistics can now be sorted by user.

 

Fixed issues:

  • SharePoint disk space value has been added to the SharePoint Statistics view.
  • In the Traveler Statistics view, Users names are now displayed in their Abbreviated form instead of Canonical form.
  • In SharePoint, PowerShell authentication can now be done in Basic mode with SSL enabled.
  • Enabling the Debug mode does not require a reboot anymore.
  • Resolved conflict when the username specified in a SharePoint scenario was the same name as a local user account on the target server.
  • An exception made the BES scanning fail when retrieving the BES Users status.
  • Maintenance Calendar viewer now displays correctly the maintenance timeframe when it is set across two days.
  • The sound alerts configured in Alert Profiles are now triggered properly when the database has been migrated from an old version of GSX Monitor.
  • SharePoint Web Services alerts now display detailed information.
  • SharePoint Web Services LED tooltip now display which services exceed threshold.

Posted on Mar 20, 2013

GSX Monitor    10.3.3 : Release Notes
March 19, 2013

PREREQUISITES

If you upgrade from a version earlier than 10.1:

  • Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.
  • IIS Web Server must be installed on GSX Analyzer station.

 

Monitoring Exchange servers 2000 and 2003 is no longer supported. All your servers configurations for these versions will be deleted when upgrading.

 

Fixed issues:

  • The ‘Network down’ test is no more performed when Sametime services are up, avoiding Network Down erroneous information.
  • The Traveler timeout set in GSX Monitor Preferences is now taken into account.
  • Exchange disk space alert is now sent correctly even when free disk space is 0 bytes.
  • Rows could automatically move in the Main View when a Port Configuration linked to a Domino server was set.

Posted on Mar 19, 2013

GSX Monitor    10.3.2 : Release Notes
February 12, 2013

PREREQUISITES

If you upgrade from a version earlier than 10.1:

  • Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.
  • IIS Web Server must be installed on GSX Analyzer station.

 

Monitoring Exchange servers 2000 and 2003 is no longer supported. All your servers configurations for these versions will be deleted when upgrading.

 

Fixed issues:

  • Retrieving SharePoint Sites could fail when configuring DB on a specific port.
  • Some Sametime meetings statistics were missing in the Main View rows.
  • Quickr Places settings are now saved properly.
  • Quickr settings can now be copy/pasted properly.
  • SharePoint scan now takes into account the aliases for SQL that matches the following pattern "alias\instance".
  • An issue occurred in the Domino Disk Space alert generation, resulting from a 0-byte remaining disk space.
  • An exception made the Log statistics update failed, so the Log scanning LEDs were not showing relevant information.
  • Exchange Mailbox and CAS LEDs are now correctly displayed in WebEnabler for Exchange 2007 to reflect Windows Services status.

Posted on Feb 13, 2013

GSX Monitor    10.3.1 : Release Notes
January 14, 2013

PREREQUISITES

If you upgrade from a version earlier than 10.1:

  • Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.
  • IIS Web Server must be installed on GSX Analyzer station.

 

Monitoring Exchange servers 2000 and 2003 is no longer supported. All your servers configurations for these versions will be deleted when upgrading.

 

New Features and Improvements:

  • Exchange Outlook Anywhere connectivity can now be monitored.
  • Outlook Web Services alerts now focus on Availability Service, Offline Address Book, Unified Messaging and Outlook Anywhere.

Fixed issues:

  • The Average Mailbox size in the DAG Statistics view is now displayed correctly.
  • Scanning Exchange servers without having selected any role is now possible (Edge servers for example).
  • The Global maintenance alert profile is played only if the root alert profile is not disabled.
  • Exchange Main View properties was not showing non-critical Windows Services properly.
  • Erroneous information could be displayed in Exchange Hub LED tooltip.
  • Fixed issue on Exchange Disks statistics graphs generation.
  • An overflow exception could make the SharePoint server test connection fail.
  • Exchange mailbox statistics now ignore soft-deleted mailboxes and are only comprised of active and disabled mailboxes.

Posted on Jan 17, 2013

GSX Monitor    10.3.0 : Release Notes
November 27, 2012

 

PREREQUISITES

If you upgrade from a version earlier than 10.1:

  • Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.
  • IIS Web Server must be installed on GSX Analyzer station.

 

Monitoring Exchange servers 2000 and 2003 is no longer supported. All your servers configurations for these versions will be deleted when upgrading.

 

New Features and Improvements:

  • Exchange Availability statistics for Mailbox, CAS, Hub roles and Mailbox Databases:
    • Up time / Down time
    • Up count / Down count
  • Introduction of Hub Servers Monitoring:
    • Status of Hub Server
    • Status of Delivery and Unreachable Queues
  • A specific test mailbox can now be used for Exchange CAS checks.
  • Exchange Server Monitoring improvements:
    • Missing performance counters does not report the server down any more.
    • The Statistics View now shows the Performance Counters status per role and gives more details (status, value, error) on each counter.
    • Critical Windows services status now impacts related Role(s) status and no more the server general status.
    • A ‘Retry before alert” value can now be specified for DAG Replication Health alerts.
    • The Exchange System LED now only reports on server connectivity (PowerShell Connection on 2010 version)
    • If using the Agent, the Server availability is defined by the connection to the agent.

 

Fixed issues:

  • GSX Monitor stopped scanning Exchange servers when a cluster was deleted.
  • Replay Service is added to the list of recommended Windows Services.
  • Pending and Dead mails have been replaced by Delivery and Unreachable queues.
  • Exchange 2007 Statistics could be reported wrong from the Statistics View.
  • A problem could occur after creating an Exchange server that have previously been deleted.
  • In certain cases, an exception made the Exchange scanning hang when monitoring clusters.
  • The Maintenance Calendar now shows the Special Maintenance.
  • From the Statistics View, the average Mailbox size is now displayed in "0.000" format if the value is in between 0 and 1.

Posted on Jan 14, 2013

GSX Monitor    10.2.5 : Release Notes
November 13, 2012

PREREQUISITES

If you upgrade from a version earlier than 10.1:

  • Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.
  • IIS Web Server must be installed on GSX Analyzer station.

 

Improvements:

  • Traveler alerts:
    • In the alert body, components being found in error (HTTP, Traveler, servlet) have been added.
    • In the graphs, more information has been added to the tooltip.
    • New alert on HTTP CPU usage (custom threshold, alert down and back to normal alert).
  • A specific Windows Account can be specified to authenticate to SharePoint SQL and Log Scanning.
  • A specific Windows Account can be specified to authenticate to BES SQL and Log Scanning.
  • Change Monitoring reports have been improved:
    • Faster loading by embedding images in the report.
    • Labels changed from “Change Monitoring Down” to “Change Monitoring could not be performed”.
    • Alerts content has been enhanced.
  • A Calendar view button has been added to all Server Maintenance Configuration views.

Fixed issues:

  • When generating CSVs, new lines are automatically replaced by space characters to get a good formatting.
  • The password protection in GSX Monitor Preferences now works properly.
  • Fixed SharePoint logs scanning issue when occurring after a time change because of Daylight Saving Time (DST).
  • Fixed issue with SharePoint Log Scanning after having deleted log files.
  • Double-clicking the Domino Performance status LED displayed non-existing proxy settings.

Posted on Nov 13, 2012

GSX Monitor    10.2.4 : Release Notes
October 19, 2012

PREREQUISITES

If you upgrade from a version earlier than 10.1:

  • Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.
  • IIS Web Server must be installed on GSX Analyzer station.

 

Fixed issues:

  • Problem on sorting dates in User Scenario Results has been fixed.
  • Exchange LEDs in Moniweb did not reflect the right configuration.
  • An exception could occur while importing old reports in GSX Analyzer.                             
  • CAS protocols alerts are now hidden when the corresponding protocol is excluded from the CAS checks.
  • Sound or test sounds in Preferences > Alerts menu are now working properly.
  • Optimization of Exchange statistics initialization at GSX Monitor startup.                             
  • A regression has been fixed regarding constant Domino log scanning.
  • The LastBackup.zip file is no more sent on task crash, preventing from receiving mails with big attachments.
  • Reminder alerts on Domino pending/dead mails were sent while the initial alert was not. In addition to this, the “No more pending/dead mail” alert was not sent.        
  • Sametime 8.5+ WAS now reports more detailed error messages.
  • A ‘Support’ folder containing support tools has been added under GSX Monitor root folder.

Posted on Oct 22, 2012

GSX Monitor    10.2.3 : Release Notes
September 13, 2012

PREREQUISITES

If you upgrade from a version earlier than 10.1:

  • Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.
  • IIS Web Server must be installed on GSX Analyzer station.

 

New Feature:

SSL Certificates are now automatically trusted to prevent any error when checking CAS for ActiveSync.

Fixed issues:

  • Domino Scan no more crashes when GSX Monitor reaches the scan timeout.
  • Fixed issue on SharePoint scanning when some SQL queries failed while retrieving information on content databases (unexpected behavior of SQL SUM function).
  • Multiple instances of the same alert type were generated by GSX Monitor.
  • Comma Separator in Distribution List now works properly.
  • GSX Monitor archives (backups) can now be extracted using Windows archive extractor.
  • A Full Backup now extracts all necessary content and keeps the folders hierarchy.
  • When configuring a cluster, the Business Hours field can now be copy-pasted from one cluster to another.
  • The Test Mail dialog box could hang even after the mail was sent.
  • Fixed issue in Domino Database Performance when trying to copy/paste alert profiles. 
  • SharePoint and BES Log Scanning reports were not sent to GSX Analyzer if the Distribution list option was not selected.
  • ‘Once a day’ option is now working fine for Domino Log Scanning.

Posted on Sep 13, 2012

GSX Monitor    10.2.2 : Release Notes
July 26, 2012

 

If you also want to have GSX Analyzer installed, you have to download the GSX Monitor & Analyzer package and read its release notes here.

 

PREREQUISITES

If you upgrade from a version earlier than 10.1:

  • Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.
  • IIS Web Server must be installed on GSX Analyzer station.

 

Fixed issues:

  • The Exchange credentials are now encrypted in GSX Monitor database.
  • Enable/disable button did not work in Domino replication.
  • SharePoint urls with non alpha characters (_ or -, etc) were not correctly retrieved.
  • Fixed regression where the DAG was reported as down when GSX Monitor found Recovery databases that were not replicated.
  • When the port used for Java to monitor websphere was changed manually, it was reset each time GSX Monitor restarted.
  • Sharepoint Search Scenario failed with “No Response” message.
  • Issue when exporting BES user list to a CSV file.
  • Fixed regression where the Quickr server was reported as down if the Web Services requests did not return valid XML content.
  • Fixed issue in SharePoint log scanning when log files were not in the expected format and “0 lines processed” was reported by GSX Monitor.
  • Fixed issues in Change Monitoring when the process exited due to Notes API issues.
  • Exception could make the CAS alert message not relevant.
  • Tests on CAS protocol (OWA, POP3, IMAP) could sometime have unexpected behavior with up/down sequence.

 


Posted on Sep 13, 2012

GSX Monitor    10.2.1 : Release Notes
June 13, 2012

 

If you also want to have GSX Analyzer installed, you have to download the GSX Monitor & Analyzer package and read its release notes here.

 

PREREQUISITES

If you upgrade from a version earlier than 10.1, Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.

 

Fixed issues:

  • Test emails sent to GSX Analyzer do not show up anymore.
  • An exception occurred while connecting to Wavecom Sierra Wireless Multiband modem.
  • The Pending messages limit for BES user alerts was limited to 100 messages (now 99 999 messages).
  • An exception occurred while setting up a BES cluster, then cancelling the operation.
  • Domino statistics on Turkish Operating Systems were not retrieved nor sent to GSX Analyzer.
  • After creating a Cluster, the status was showing "Up" in the tooltip instead of “Not scanned”.
  • It is now possible to reset multiple entities in Scenario, Performance and Change Monitoring views.
  • An exception made the application crash when loading an organization in the Exchange Overview.
  • GSX Monitor now retains correctly Sametime 8 server’s password with special characters.
  • In SMTP port monitoring, the “Retry before alert” value is now interpreted correctly.
  • SharePoint User Scenarios and Performance is now working with SQL Aliases.
  • Email Alert Attachments for Spot Check Reports can now be retrieved from any Mail client.
  • GSX Monitor historic file (GSXHist*.txt) was saved to C: instead of GSX Monitor ‘Data’ directory.
  • Domino Spot Check reports was frozen when “Agent Monitoring” were configured.
  • Domino Log Scanning did not start.
  • Spot Check Reports Alerts Email attachments are now created properly.
  • If no Search DB is configured in SharePoint, no scan is performed for indexer/crawler.
  • An exception occurred when modularizing GSX Monitor with the Exchange Overview.

Posted on Jun 13, 2012

GSX Monitor    10.2.0 : Release Notes
April 26, 2012

 

If you also want to have GSX Analyzer installed, you have to download the GSX Monitor & Analyzer package and read its release notes here.

 

PREREQUISITES

If you upgrade from a version earlier than 10.1, Microsoft .NET Framework 2 and Microsoft .NET Framework 4 (Full) must be installed on the monitoring station.

 

New Features:

  • The Exchange Overview is a new view in GSX Monitor allowing you to automatically discover your Exchange architecture (servers and clusters, organized per role).
  • A new window (Help > License Information) shows how many licenses are used for each category, and how many free licenses remain.
  • Network Load Balancing monitoring is enabled on Exchange CAS Array.
  • Change Monitoring reports can be customized (header and footer).
  • GSX Monitor now supports WSS 3.0 and SharePoint Foundation 2010.
  • If you use SQL Aliases in your SharePoint farm, you can now retrieve Aliases automatically or manually.
  • GSX Monitor now supports SharePoint backends distributed on several SQL servers.
  • New Access time alert on SharePoint Web Services.
  • New Graphs for SharePoint Web Services.
  • New Graphs for Exchange CAS protocols latency, MAPI connectivity latency and Total users connections.

Improved:

  • Windows Services in Exchange are now separated in two distinct categories: critical and non-critical Services.
  • The maximum number of Domino tasks that you can monitor is now 25.
  • In the Scenario View, four buttons have been added (Select all, Unselect all, Move up and Move down configurations).

Posted on Jun 13, 2012

I am already a member

Starting with GSX
Testimonials Contact us


Microsoft SilverPartnerBlackberryIBM Lotus

CONTACT US TODAY!

CONNECT WITH GSX

GSX Solutions© 2017   Legal   License Agreement   Privacy Policy