Microsoft Forefront Security 2010 for Exchange Server is running on Exchange server {0} with reverse DNS lookup enabled. If enabled, this may cause performance problems.
Microsoft Exchange was unable to initialize the Content Filter agent. Check the access control lists (ACLs) on the files ...
Microsoft Exchange was unable to initialize the Content Filter agent. It could not allocate sufficient memory for an internal ...
Microsoft Exchange was unable to initialize the Content Filter agent. Notification of the file system change could not be ...
Microsoft Filter Pack isn't installed on server {0}. The Microsoft Filter Pack is necessary to index and search Microsoft ...
Microsoft Forefront Security 2010 for Exchange Server is running on Exchange server {0} with reverse DNS lookup enabled. ...
Microsoft Forefront Security 2010 for Exchange Server is running on Exchange server {0} without reverse DNS lookup enabled. ...
Microsoft Office 365 Best Practices Analyzer Beta 1.0 can allow you enter alternate credentials to run the on-premises checks. ...
Modifying CompleteAfter within a short period of time before the original CompleteAfter may not take affect. Settings propagate ...
Monitoring is not enabled for database {0}. Last reported monitoring (AutoDagExcludeFromMonitoring) state is {Probe.StateAttribute3} ...