Chat now with support
Chat with Support

Foglight for Exchange 5.7.2.3 - Release Notes

Resolved issues and enhancements

Resolved issues and enhancements

This 5.7.2.3 release of Foglight for Exchange accompanies the release of Foglight Evolve 9.0. It includes the following resolved issues and enhancements.

Defect ID

Resolved Issue

EXC-1494

Removed the dependency of Office365 in Exchange Monitoring Cartridge.

EXC-1501

Added Email Actions & UI Notification for Rule: EXC Agent Updates.

EXC-1509

Wrongly declared parameters number in query 'Site Unknown Servers’.


Deprecated features

Deprecated features

There are no features deprecated in this release.

 


Known issues

Known issues

The following is a list of issues known to exist at the time of this release.

Defect ID

Known Issues

EXC-1527

When host provider has been selected as VMware cartridge/Hyper-V cartridge, though the host provider will be changed to IC /Active Directory cartridge later, datastore metrics still display on Exchange Explorer Resource Utilization dashboard.

n/a

Metrics that do not have generally accepted thresholds for alarms are configured as trend alarms.
Workaround: The significance of trends is dependent on the environment and default settings may generate many meaningless alarms in a busy environment while failing to fire at all in a smaller environment. We recommend that the administrator allow the agent to collect values over an adequate period of time to observe normal performance and then adjust trend alarms to fire at suitable thresholds.

 

 


Third party known issues

Third party known issues

The following is a list of third party issues known to exist at the time of this release.

Defect ID

Known Issues

EXC-37

The automatic reboot feature of Windows updates may not allow enough time for the FMS to shut down gracefully. This can result in broken agents when the service is restarted.

Workaround: Manually stop the FMS before performing updates.

EXC-31

Exchange services may start before the AutoDiscovery/AutoPurge (ADAP) service causing a failure to transfer Exchange performance libraries to the WMI repository. This results in 0x80041010 (class not found) errors in the log when queries run against these libraries.

Workaround: To refresh the WMI repository, run wmiadap.exe /f at the command line after Exchange services have started.

 


Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating