7.4.0.3049 - September 22nd, 2017
- Mailscape 365: Reporting: Resolved SQL Error:Violation of PRIMARY KEY constraint 'PK_example’
- Mailscape: Monitoring: DAG Improvements
- Improved DAG monitoring performance
- Optimized how we handle lagged Database copies
- Optimized how we handle DAG Failover states
- Mailscape: Monitoring: SQL: improved memory usage of ENow SQL service on the web server
- EMS: Monitoring: Alerts: Provide a global setting to reduce alert "bouncing"
- EMS: Monitoring: Alerts: Implemented Alert Intelligence feature
- Mailscape: Reporting: Custom Report: Fix delivery time in custom traffic reports
- Mailscape: Reporting: Update the SQL traffic summary table in batches
7.4.0.3020 - February 1st, 2017
- New Mailscape End User Experience tests: We've added more than a dozen Outlook-specific tests to our Mailscape probes to help you better identify and diagnose Outlook connectivity and service issues. These tests build on our existing synthetic transaction and protocol tests to give you more visibility than ever into what Outlook users are seeing.
- Improved the reliability of the Mailscape 365 OWA logon test to better handle some types of Microsoft service errors.
- Added the ability to choose custom ports for monitoring in Uniscope.
- Improved our Insights report engine to give you more sorting and arrangement options in reports that contain data grids.
- Improved performance of the EMS Network Agent when gathering Windows patch/hotfix data.
- Our lawyers made us fix a typo in the Uniscope license agreement. Then they sent us a bill.
- Other stability and performance fixes for Mailscape, Mailscape 365, Uniscope, Compass, and Foresite.