Chat now with support
Chat mit Support

Foglight for Active Directory 5.7.2 - Release Notes

Resolved issues and enhancements

Resolved issues and enhancements

The following is a list of issues addressed and enhancements implemented in this release.

Defect ID

Resolved Issue

AD-698

Improved descriptions for the rule Host Logical Disk Capacity Available.

AD-694

Fixed the javax.naming.NameNotFoundException error found in the agent log.

AD-689

Improved the rule Agent Encountered Fatal Error, to trigger it only when WQL query is invalid or the specified class does not exist in the given namespace.

AD-567

Trigger an alert when a forest trust is broken in the monitored AD domains.

 

Back to Top

Deprecated features

Deprecated features

Foglight for Active Directory no longer supports Monitored Domain Controllers Windows Server® 2003.

 

Back to Top

Known issues

Known issues

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

Defect ID

Known Issue

AD-619

Memory Utilization shows a negative value.

Workaround: After changing the memory, restart the Active Directory agent to refresh the memory capacity.

n/a

Metrics that do not have generally accepted thresholds for alarms are configured as trend alarms.

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.

Workaround: We recommended 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.

n/a In some circumstances, DCs on Windows Server 2012/2012 R2 systems may experience high CPU usage when monitored by the Active Directory agent. This issue only appears when using WinRM connections.
Workaround: Using WMI/DCOM connections prevents this issue. For details, see Troubleshooting.

 

Back to Top

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 Issue

AD-41

The automatic reboot feature of Windows® updates may not allow enough time for the Foglight Management Server (FMS) to shut down correctly. This can result in broken agents when the service is restarted.

Workaround: Manually stop the FMS before performing updates.

 

Back to Top

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen