AppManager for Microsoft Exchange Server and Exchange Online lets you monitor the operation, performance, connectivity, and availability of Exchange Server 2007, Exchange Server 2010, Exchange Server 2013, and Exchange Server 2016, and monitor the mailbox quota and the service health for Exchange Online.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ website in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials website.
This release of AppManager for Microsoft Exchange Server and Exchange Online provides the following enhancement:
Support for Microsoft Exchange Server 2019: This release supports Exchange Server 2019. For more information, see System Requirements.
This release of AppManager for Microsoft Exchange Server and Exchange Online resolves the following issue:
Exchange Module fails to initialize MCPSHostClient: This issue occurs when the system locale setting is not English US and the decimal separator is not dot or period. With this hotfix release, this issue is resolved. (ENG348482)
To get the updates provided in this release, you must install the module to the AppManager repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts. For more information, see the “Upgrading Knowledge Script Jobs” section in the management guide.
This release of AppManager for Microsoft Exchange Server and Exchange Online replaces all Previous Releases.
For the latest information about supported software versions and the availability of module updates, visit the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the Exchange computers you want to monitor (agents), and on all console computers |
8.0.3, 8.2, 9.1, 9.2, 9.5, or later One of the following AppManager agents are required:
NOTE:
For more information about these hotfixes, see the AppManager Suite Hotfixes page. |
|
Microsoft Windows operating system on the agent computers |
One of the following:
|
|
Microsoft Exchange Server on the agent computers |
One of the following:
|
|
AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the Exchange Server computers you want to monitor (agents), and on all console computers |
Support for Windows Server 2008 R2 on AppManager 7.x requires the AppManager for Windows module, version 7.6.170.0 or later. For more information, see the AppManager Module Upgrades & Trials page. |
|
Microsoft Exchange Server Role installed on the agent computers |
At least one of the following Exchange Server roles installed:
|
|
Microsoft .NET Framework installed on the agent computers |
3.0 and 3.5 |
|
Windows PowerShell Engine |
2.0 for Exchange Server 2007 and 2010 3.0 or later for Exchange Server 2013 and 2016 NOTE:For Windows 2012 make sure that PowerShell 2.0 engine feature is installed. If this component is not installed the discovery process fails. |
|
Microsoft SQL Server Native Client 11.0 (for TLS 1.2 support) |
11.3.6538.0 or later NOTE:The SQL Server Native client can be installed from this Microsoft download link. |
AppManager for Exchange Online has the following system requirements:
|
Item |
Requirement |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the Exchange computers you want to monitor (AppManager agents), and on all console computers |
8.0.3, 8.2, 9.1, 9.2, 9.5, or later One of the following AppManager agents are required:
|
|
Microsoft Windows operating system installed on agent computers |
One of the following:
|
|
AppManager for Microsoft Windows installed on the agent computers |
8.0.104.0 or later |
|
Windows Azure Active Directory Module for Windows Powershell (64-bit) installed on the agent computers |
1.0.9031.1 or later |
|
Microsoft .NET Framework installed on the agent computers |
3.5 and 4.0 or later |
|
Windows PowerShell Engine |
3.0 or later |
|
Microsoft SQL Server Native Client 11.0 (for TLS 1.2 support) |
11.3.6538.0 or later NOTE:The SQL Server Native client can be installed from this Microsoft download link. |
NOTE:If you want TLS 1.2 support and are running AppManager 9.1 or 9.2, then you are required to perform some additional steps. To know about the steps, see the article.
AppManager for Microsoft Exchange Server and Exchange Online includes a managed object, along with a set of PowerShell scripts, and Knowledge Scripts to discover and monitor Microsoft Exchange Server and Exchange Online resources. The download package includes this release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-Exchange2007-7.6.183.0.msi, the module installer.
AM70-Exchange2007-7.6.183.0.ini, a configuration file used with the AppManager setup program.
AM70-Exchange2007-7.6.183.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
AM70-Exchange2007-7.6.183.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckExchange2007.exe, the pre-installation check used with the AppManager setup program.
DefaultRule_Exchange2007.xml, a configuration file used for deploying the module with Control Center.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
Run the module installer to install the module components in the following locations:
On the Exchange computers you want to monitor (agents) to install the agent components
On all console computers to install the Help and console extensions
Run the module installer only once on each of these computers.
You must also install the Knowledge Scripts and Analysis Center reports. You can install these components into local or remote QDBs. When installing to the primary QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name. Select the option to install Analysis Center reports, and then specify the SQL Server name of the server hosting the Analysis Center Configuration Database.
IMPORTANT:If you use Control Center 7.x, run the module installer for each QDB attached to Control Center. If you use Control Center 8.x or later, run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs.
Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
For more information about installing this module, see the AppManager for Microsoft Exchange Server and Exchange Online Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
MCPSHostServer.exe process might utilize too much CPU: When you run multiple jobs simultaneously, the MCPSHostServer.exe process might use significantly high CPU. (ENG340952)
Exchange2007_CAS_Connectivity Knowledge Script does not have sufficient access rights to run on Exchange Server 2010. When you run the Exchange2007_CAS_Connectivity Knowledge Script on the Exchange Server 2010 agent computer, you get an insufficient access rights error. The error occurs when the Knowledge Script tries to create a test user account. (DOC339377)
To work around this issue, do the following:
Open the Exchange Management Shell on the agent computer.
Run the Get-Mailbox extest* | Remove-Mailbox command to remove the existing test user account.
Change directories to the Scripts directory under the Microsoft Exchange installation directory.
Run the Get-MailboxServer | .\New-TestCasConnectivityUser.ps1 command.
Follow the on-screen instructions to create a new test user account.
Exchange2007_CAS_Connectivity test user created on Exchange Server 2010 does not work on Exchange Server 2007. When you run the CAS_Connectivity Knowledge Script on a Client Access server, the script automatically creates a CAS test user mailbox on each Mailbox server in the Exchange deployment if those mailboxes do not already exist. In an Exchange deployment containing Exchange 2007 and Exchange 2010 servers, if you run the CAS_Connectivity script on an Exchange 2010 Client Access Server, the script will not be able to create the mailboxes on Exchange 2007 Mailbox Servers, and AppManager raises an error event about the problem. This is due to the issue that Microsoft does not support creating mailboxes across different version types. To resolve, you must manually create the CAS test user mailboxes on the Exchange 2007. (DOC335681)
Exchange2007_CAS_OABAvailability Knowledge Script is not supported for use with Exchange Server 2013. Due to changes made by Microsoft with the architecture of Exchange Server 2013, the Exchange2007_CAS_OABAvailability script does not work if you run this script on an Exchange Server 2013 Client Access server. This issue only occurs with servers running Exchange Server 2013. (ENG330948)
Exchange2007 jobs cause high memory usage and poor performance. If you are experiencing high memory usage with the jobs started by Exchange2007 Knowledge Scripts, you can increase the value of the PowerShell maxMemoryUsage setting in the server's configuration file, AppManager\bin\PowerShell\MCPSHostServer.exe.config. Increasing this value can reduce the number of servers that are active at any point in time, while also reducing the frequency of server restarts caused by the memory usage exceeding the limit imposed by the maxMemoryUsage setting. For best performance, NetIQ Corporation suggests you use a value of 500 MB. The value for maxMemoryUsage depends on the CPU and memory of the AppManager agent computer, the number of mailboxes, mailbox databases, offline address books, and other elements of the Exchange server, and the number of Exchange2007 Knowledge Script jobs that are running. (ENG331029)
Upgrade of AppManager for Exchange Server 2007/2010 version 7.3 or 7.4 to version 7.5 does not remove the old objects. When you upgrade AppManager for Exchange Server 2007/2010 version 7.3 or 7.4 to version 7.5 and discover the Exchange Server resource objects, the old Exchange objects are not removed from the Navigation pane or TreeView. You must manually delete the old Exchange2007 objects from the Navigation pane or TreeView in AppManager. (DOC329572)
Exchange2007_CAS_OABAvailability Knowledge Script does not work with offline address books if they are in a public folder. If you changed the offline address book from something other than the default offline address book and if it is in a public folder, the Exchange2007_CAS_OABAvailability script raises an event stating that the Web server returned an error. This Knowledge Script monitors the offline address books only if they are hosted in a virtual directory. (ENG309138 and DOC313092)
Exchange2007_CAS_OABAvailability Knowledge Script job run on Exchange 2010 CAS role server does not obtain the URL addresses of the address books located on Exchange 2013 servers. If you run the Exchange2007_CAS_OABAvailability Knowledge Script job on an Exchange 2010 CAS role server in an environment that has Exchange 2013 mailbox servers, the job cannot obtain the URL addresses of the address books located on the Exchange 2013 servers and displays an error. Therefore, you should not run this job from Exchange 2010 CAS role servers to test the availability of Exchange 2013 mailbox servers. (DOC330397)
Discovery_ExchangeDAG does not work when Discovery_Cluster was previously run on a resource object. If you previously ran the Discovery_Cluster Knowledge Script on nodes that now belong to a DAG, the Discovery_Cluster script discovered the Windows Cluster resource object, NT_CLU_MachineFolder. If you later run Discovery_ExchangeDAG on any node that belongs to the DAG, the script will not discover any new objects, because an object with the same name was added using the Discovery_Cluster Knowledge Script. As a result, you will not be able to use the Discovery_Exchange2007 Knowledge Script to discover the databases on the DAG object, because Discovery_Exchange2007 does not work with the NT_CLU_MachineFolder resource object. To address this situation, remove the Windows Cluster object that was discovered with the Discovery_Cluster Knowledge Script and use the Discovery_ExchangeDAG Knowledge Script to discover the DAG object. (ENG289028)
Discovery_Exchange2007 creates only one object after view is deleted. If you delete all discovered objects or delete the Exchange2007 view altogether, then run Discovery_Exchange2007, the job does not re-discover all of the deleted objects, it discovers only one of the objects you deleted, and displays it in the console. (ENG270851, ENG275474, ENG183262)
AppManager does not raise events when one of the All_* Knowledge Scripts runs on a passive physical node. When you run one of the All_* Knowledge Scripts on a physical node that is in the passive state, AppManager does not raise an event for that computer. These scripts only raise events on active physical nodes. The scripts include All_BestPracticesAnalyzer, All_ClockSynchronization, All_EventLog, and All_ServiceStatus. (ENG286303)
The event message for the MBS_MailFlow Knowledge Script inaccurately lists the timeout value. When the threshold for the maximum response time for mail flow test is exceeded, the timeout value listed in the event message is inaccurate. (ENG289303)
MBS_Replication does not show details properly in the Chart Console. If you create a chart in the Chart Console based on data gathered by the MBS_Replication Knowledge Script and hover over a data point, the flyover details might not be shown correctly. (ENG276421)
Duplicate events from the BestPracticesAnalyzer Knowledge Script. Because several events logged by the Exchange Best Practices Analyzer tool are generic to the Exchange organization, the BestPracticesAnalyzer Knowledge Script might raise the same events for each Exchange 2007 Server role installed on the same Windows computer. (DOC258800)
This release of AppManager for Microsoft Exchange Server and Exchange Online includes enhancements added in previous releases.
This release provided the following enhancements:
Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Microsoft Exchange Server and Exchange Online provides support for TLS 1.2.
All_ServiceStatus KS generates events without doing any data collection: This release of AppManager for Microsoft Exchange Server and Exchange Online provides an enhancement by providing an additional parameter for data collection in All_ServiceStatus Knowledge Script user interface to collect data for all exchange server services.(ENG348350)
This release provided the following enhancements:
New functionalities added for ExchangeOnline_MailboxQuota: You can now use the ExchangeOnline_MailboxQuota Knowledge Script to perform the following jobs:
Raise events to view the top mailbox users.
Specify the list of Exchange Online domains to exclude from monitoring.
Collect data if the mailbox usage exceeds Warning quota, threshold for Prohibit Send quota, threshold for Prohibit Send and Receive quota.
Collect data if the user is blocked from sending mails.
Collect data if the user is blocked from sending and receiving mails.
ExchangeOnline_MailboxQuota now runs once daily as the default schedule: Previously the ExchangeOnline_MailboxQuota Knowledge Script was set to run every hour, which was the default schedule. In this release, the default schedule of the Knowledge Script is set to run once daily.
New functionalities added for ExchangeOnline_ServiceHealth: You can now use the ExchangeOnline_ServiceHealth Knowledge Script to perform the following jobs:
Raise events if the service is healthy or unhealthy.
Display the latest updates of the service incidents.
Specify the list of services to include for monitoring or exclude from monitoring.
TreeView lists all the subscribed Office 365 services in addition to the Exchange Online service after discovery: You can now view all your subscribed Office 365 services (workloads) in TreeView in addition to the Exchange Online service after running the Discovery_ExchangeOnline Knowledge Script.
This release resolved the following issues:
ExchangeOnline_ServiceHealth reports the service status only when a service state changes: The ExchangeOnline_ServiceHealth Knowledge Script raised an event for a service status only when the service state was changed. In this release, the Knowledge Script raises events to show service status in every iteration. (ENG344674)
Exchange2007_MBS_DatabaseStateChange takes more time to run for large number of databases: The Exchange2007_MBS_DatabaseStateChange Knowledge Script took more time to complete a job if databases are in large number. In this release, the issue is resolved. (ENG345241)
The Exchange2007_CAS_Connectivity job is aborted when no parameter is selected: When the Exchange2007_CAS_Connectivity job was executed without any parameter selection in the Knowledge Script, the job was being aborted instead of raising an event to show the error message. In this release, the issue is resolved and an event is raised to show the error message in such scenarios. (ENG344916)
Exchange2007_CAS_Connectivity throws a sign-in error when accessing the Outlook Web services: The Exchange2007_CAS_Connectivity Knowledge Script was throwing a sign-in error when it was trying to access the Outlook Web services. This error occurred because the Knowledge Script did not fetch the credentials specified in the AppManager Security Manager. In this release, the issue is resolved. (ENG344091)
Few event detailed messages for the ExchangeOnline_ServiceHealth jobs are too long: In few scenarios, the detailed event messages were too long for the ExchangeOnline_ServiceHealth jobs. In this release, this issue is resolved and a parameter is added that lets you to check only the latest message of each service incident or maintenance event that are active on a service. (ENG344210)
ExchangeOnline_ServiceHealth does not perform an action after a job is completed. When the ExchangeOnline_ServiceHealth Knowledge Script was configured to perform an action after the execution of a job, the Knowledge Script raised an event but no action was performed. In this release, the issue is resolved. (ENG344226)
Exchange2007_MBS_DatabaseStatus throws an error on an agent machine with PowerShell 2.0: The Exchange2007_MBS_DatabaseStatus jobs were throwing errors on an agent machine that had PowerShell 2.0 because of compatibility issue. In this release, this issue is resolved. (ENG344081)
ExchangeOnline_MailboxQuota throws an error after running for a long time: The ExchangeOnline_MailboxQuota Knowledge Script job ran for a long time and then displayed an error. The error was caused because the Knowledge Script was running longer than the time limit specified in the MCPSHostServer.exe.config file and was observed in one of the scenarios where there were large number of mailboxes. In this release, a workaround is provided to increase the timeout limit. For more information, see the ExchangeOnline_MailboxQuota job throws an error after running for a longer duration ExchangeOnline_MailboxQuota job throws an error after running for a longer duration section in the AppManager for Microsoft Exchange Server and Exchange Online Management Guide. (ENG344310)
MCPSHostServer.exe consumes too much CPU: In few scenarios, the MCPSHostServer.exe process was consuming too much CPU. In this release, a workaround is provided to control the CPU usage for the process. For more information, see the MCPSHostServer.exe consuming too much CPU section in the AppManager for Microsoft Exchange Server and Exchange Online Management Guide. (ENG340952)
Exchange2007_MBS_PublicFolderUsage returns an exception while monitoring two or more public folders with the same folder name: The Exchange2007_MBS_PublicFolderUsage Knowledge Script displayed an error when two or more public folders with the same folder name were monitored. In this release, the issue is resolved. (ENG345288)
This release provided the following enhancements:
Support for Microsoft Exchange Server 2016: This release supports Exchange Server 2016. For more information, see System Requirements.
Support for Microsoft Exchange Online: In this release, you can use AppManager to monitor the Mailbox quota and Service health of Exchange Online domains (tenants). The following Knowledge Scripts are introduced for Exchange Online:
MailBoxQuota: Monitors the mailbox quota of the users of the Exchange Online domains.
ServiceHealth: Reports the status of the Exchange Online service. Monitors the service incidents and maintenance incidents that impacts the domains of your Office 365 subscription.
CAS_Activity and MBS_ClientActivity do not raise events if client services are disabled: In this release, you can specify the list of servers for which the Exchange2007_CAS_Activity and Exchange2007_MBS_ClientActivity Knowledge Scripts should not raise events if the client services are in the disabled state.
A percentage threshold value can be specified for disk utilization in MBS_DatabaseStatus: In this release, you can specify a percentage threshold for the disk utilization in the Exchange2007_MBS_DatabaseStatus Knowledge Script.
MBS_Replication can ignore monitoring of replication of user-specified mailbox stores: In this release, you can specify a list of mailbox stores in the Exchange2007_MBS_Replication Knowledge Script for which replication monitoring will be ignored.
This release resolved the following issues:
Exchange2007 Knowledge Scripts fail to execute when NetIQmc is running on the local system account: If NetIQmc is running on your local system account, the Exchange2007 Knowledge Scripts fail to execute. In this release, a check mechanism is added to verify whether NetIQmc is running on the local system account and raise an event if the Exchange2007 Knowledge Script jobs fail because NetIQmc is running on the local system account. (ENG329596)
PowerShell initialization fails when system locale setting is Hungarian: The PowerShell initialization in the Discovery_Exchange2007 Knowledge Script failed when the system locale setting was Hungarian. In this release, the issue is resolved. (ENG322260)
Exchange2007_Transport_BackPressure fails when BackPressure is disabled: For Exchange Server 2013 with Cumulative Update 8 or later, the Knowledge Script failed when BackPressure was disabled. In this release, the issue is resolved. (ENG340162)
Excess temporary files cause the disk space to bloat: In Exchange Server 2013, when you ran Exchange2007 Knowledge Scripts, large number of temporary files were generated that caused the disk space to bloat. In this release, the issue is resolved. (ENG337287 and ENG341995)
This release resolved the following issues:
Exchange2007_MBS_ClientConnectivity connects to remote MBS Servers. This release resolves an issue in which the Exchange2007_MBS_ClientConnectivity Knowledge Script tried to connect to the remote MBS Servers along with the local MBS Server when you ran the MBS_ClientConnectivity job. With this release, an update to the Knowledge Script ensures that the Exchange2007_MBS_ClientConnectivity Knowledge Script connects to the local MBS Server only. (ENG336906)
The CPU load increases on Exchange Server 2010 when you run the Exchange2007_Transport_BackPressure Knowledge Script. This release resolves an issue in which the CPU load increased when you ran one of the following Knowledge Scripts on Exchange Server 2010:
Exchange2007_Transport_BackPressure Knowledge Script
Exchange2007_All_BestPracticesAnalyzer
Exchange2007_All_EventLog
Exchange2007_MBS_DatabaseStatus
Exchange2007_MBS_MessagingRecordsMgmt
With this release, you can run the Knowledge Scripts without an increase on the CPU load. (ENG338355)
Exchange2007_AllClockSynchronization Knowledge Script is unable to determine the clock synchronization for the domain controllers. This release resolves an issue in which the Exchange Server was unable to associate with an Active Directory domain or forest while running the Exchange2007_AllClockSynchronization Knowledge Script. The clocks of the domain controllers were not abe to synchronize because the information about the current Active Directory domain or forest could not be obtained. With this release, the Exchange Server is able to associate with an Active Directory domain or forest while running the Knowledge Script. (ENG337616)
This release resolved the following issues:
Exchange2007_CAS_Activity Knowledge Script displays an invalid value for POP3 command processing time. This release resolves an issue in which the Exchange2007_CAS_Activity script returned an invalid value, such as 2.149581E+09, for the average POP3 command processing time. With this release, an update to the script ensures that the values for POP3 command processing time are formatted properly. (ENG331192)
Exchange2007_CAS_Connectivity Knowledge Script generates a null-valued expression event message. This release resolves an issue in which the Exchange2007_CAS_Connectivity script generated the following event message: An error occurred during parsing or execution of the PowerShell script: You cannot call a method on a null-valued expression. The script generated this message when the monitored mailbox had no associated database. With this release, an update to the Knowledge Script prevents this situation from occurring. (ENG333425)
Exchange2007_MBS_DatabaseStateChange and Exchange2007_MBS_DatabaseStatus Knowledge Scripts generate events when the DAG is not available that have too high of a severity. This release resolves an issue in which the Exchange2007_MBS_DatabaseStateChange and Exchange2007_MBS_DatabaseStatus scripts sent Severe (with a value of 5) event messages stating that a monitored Database Availability Group (DAG) is not available, when actually the job was simply unable to communicate with the DAG. With this release, an update to both Knowledge Scripts lowers the default severity of this issue from Severe to a lower severity level. (ENG332792)
Exchange2007_MBS_DatabaseStateChange and Exchange2007_MBS_DatabaseStatus Knowledge Scripts might take an unexpectedly long time to complete. With this release, an update to how both scripts communicate with the monitored Exchange mailbox databases allows the related jobs for each script to complete in a more timely fashion. (ENG333479)
Exchange2007_MBS_DatabaseStatus Knowledge Script generates an event message stating that a DAG is not available. This release resolves an issue in which an event message stated that a Database Availability Group (DAG) was not available or the job was not running on a DAG. The event message advised you to run the Discovery_ExchangeDAG script followed by the Discovery_Exchange2007 script to rediscover this DAG. In this situation, however, both discovery scripts were successful, but the Exchange2007_MBS_DatabaseStatus script failed. With this release, an update to the Exchange2007_MBS_DatabaseStatus script prevents this situation from occurring, and the Exchange2007_MBS_DatabaseStatus script runs as expected on a DAG. (ENG333407)
Exchange2007_MBS_DatabaseStatus Knowledge Script incorrectly calculates disk space on mount points. This release resolves an issue in which the Exchange2007_MBS_DatabaseStatus script incorrectly reported the amount of free disk space on remote disk volumes that were identified as mount points on the Exchange Server. With this release, an update to the Exchange2007_MBS_DatabaseStatus script allows the script to accurately calculate the free disk space for those remote disk volumes. (ENG331753)
Exchange2007_MBS_Replication Knowledge Script generates an event message about the replay queue length that does not agree with the job's datastream. This release resolves an issue in which the Exchange2007_MBS_Replication script generated an event message stating that the replay queue length was exceeding the threshold set in the script parameters, but the datastream displayed a value that was below the specified threshold. With this release, an update to this script ensures that the event details and the datastream details report the same values. (ENG330644)
This release provided the following enhancements:
Support for monitoring Exchange Server 2013. This module now supports monitoring Microsoft Exchange Server 2013, Exchange 2007, and Exchange 2010 servers at the same time.
Support for Microsoft Windows Server 2012. This module now supports Microsoft Windows Server 2012.
This release also introduced the following new Knowledge Scripts to monitor Exchange Servers:
HTS_SafetyNet monitors the Safety Net availability in Exchange Server 2013. It replaces the HTS_TransportDumpster Knowledge Script available for Exchange Server 2007 and 2010.
MBS_ClientActivity monitors the Client Access Server activities, such as Availability, ActiveSync, Outlook Web Access, Outlook Web Services, IMAP4, and POP3 hosted on Mailbox servers on Exchange Server 2013. It replaces the CAS_Activity Knowledge Script available for Exchange Server 2007 and 2010.
MBS_ClientConnectivity monitors the connectivity of Mailbox server services on Exchange Server 2013: ActiveSync, Outlook Web services, and the Autodiscover service. It replaces the CAS_Connectivity Knowledge Script available for Exchange Server 2007 and 2010.
Transport_ConnectorStatus monitors the status of send, receive, foreign, and delivery agent connectors on Exchange Servers. This script raises an event if any of the connectors are disabled or an SMTP-based receive connector is not responding to SMTP requests. Parameters to monitor the connectors in the HTS_Connectivity Knowledge Script for previous Exchange module versions were moved to this new Knowledge Script.
This release resolved the following issues:
Discovery_Exchange2007 Knowledge Script fails when you run it on an Exchange 2007 CCR cluster environment. This release resolves an issue in which the Discovery_Exchange2007 script generates the following event message when you run it an Exchange 2007 cluster continuous replication (CCR) environment: Error Detail: The term 'Get-ExchangeServer' is not recognized as a cmdlet, function, operable program, or script file. Verify the term and try again. With this release, an update to the Discovery_Exchange2007 script prevents this event message from occurring on CCR environments. (ENG330462)
Exchange2007_HTS_Connectivity Knowledge Script does not create actions when it raises events. This release resolves an issue in which the Exchange2007_HTS_Connectivity script did not create corresponding actions for state changes when it raised events. With this release, the Exchange2007_HTS_Connectivity script properly creates actions based on events raised by the script. (ENG331037)
Exchange2007_MBS_PublicFolderUsage Knowledge Script does not monitor all public folders if you dismount the database for the primary public folder. This release resolves an issue in which the Exchange2007_MBS_PublicFolderUsage script did not monitor any other public folders that were hosted in different mailbox databases if you dismounted the mailbox database hosting the primary public folder mailbox database. With this release, the script monitors all public folders even if the primary public folder mailbox is dismounted. (ENG330554)
This release resolved the following issues:
Exchange2007 Knowledge Scripts cannot connect to a PowerShellHost server. This release resolves an issue in which, after upgrading to version 7.4.185.0 of this module, whenever you ran a script that tried to connect to the PowerShellHost server, you received the following error message: Failed to initialize MCPSHostServer PowerShell session. With this release, the Exchange2007 Knowledge Scripts can properly connect to the PowerShellHost server. (ENG316114)
Analysis Center cannot generate reports based on data gathered by the Exchange2007_MBS_DatabaseStateChange Knowledge Script. This release resolves an issue in which the Exchange2007_MBS_DatabaseStateChange script generates data that cannot be correctly interpreted by Analysis Center, resulting in no data for Analysis Center reports. With this release, this script creates data that can be processed by Analysis Center. (ENG322322)
Exchange2007 Knowledge Scripts incorrectly raise an error stating that Exchange is not installed. This release resolves an issue where Discovery_Exchange2007 and other Exchange2007 scripts incorrectly raised an Exchange not installed error message when you ran any of these scripts on a computer running 64-bit Windows. With this release, you can properly discover Exchange servers and run Exchange2007 scripts on 64-bit Windows computers. (ENG319907, ENG320741)
This release resolved the following issues:
AppManager for Exchange 2007 and 2010 attempts to connect to a database that is unavailable. This release resolves an issue in which AppManager for Exchange 2007 and 2010 reported an error when attempting to connect to an Exchange server with unmounted databases. With this release, AppManager for Exchange verifies that the database is active before attempting to verify connectivity. (ENG320232)
Exchange_CAS_Connectivity reports that it cannot identify a configured internal URL. This release resolves an issue where the Exchange_CAS_Connectivity Knowledge Script failed with the error No Internal URL configured for some Outlook Web Access (OWA) virtual directories. With this release, AppManager for Exchange 2007 and 2010 correctly identifies the URL for OWA virtual directories. (ENG319988)
AppManager for Exchange 2007 and 2010 cannot initialize PowerShellHost server session. This release resolves an issue where the PowerShellHost server (MCPSHostServer) failed when reading a self-monitoring performance counter and reported the error Failed to initialize MCPSHostServer PowerShell session. With this release, AppManager for Exchange 2007 and 2010 handles the case where self-monitoring counters are not available, which allows the job to run without failing. (ENG316577)
This release resolved the following issues:
The CAS_Connectivity Knowledge Script does not support Outlook Web Access installations when the internal URL is disabled. This release resolves an issue in which the CAS_Connectivity Knowledge Script fails when the internal Outlook Web Access URL is disabled, particularly in environments where the web server uses load balancing. With this release, enhancements to the CAS_Connectivity script allow you to access either the internal or external Outlook Web Access URL. (ENG285412)
Discovery fails if previously installed PowerShellHost is not properly registered. This release resolves an issue where the Discovery_Exchange2007 Knowledge Script fails with the error Failed to instantiate the PowerShell host client, MCPSHostClient. This issue only occurs in situations where AppManager for Microsoft Windows 7.6 or later was previously installed on the computer, but the Discovery_NT Knowledge Script was not run. With this release, AppManager for Exchange 2007 and 2010 ensures that the PowerShell host client is installed and registered. (ENG310136)
Module upgrade appears successful, but does not update all components. This release resolves an issue during upgrade in which a running MCPSHostServer process prevents a newer version of MCPSHostServer.exe from properly installing. Even when the installation appears to complete successfully, the AppManager Software Inventory indicates that the module version has not changed. With this release, the installation program has an improved mechanism to stop all MCPSHostServer processes during upgrade. (ENG303166, ENG303177)
Exchange2007_MBS_DatabaseStateChange jobs fail with value conversion error. This release resolves an issue in which Exchange2007_MBS_DatabaseStateChange jobs fail with a Cannot convert value... error. This problem only occurs if you created the job using a version of the module earlier than 7.4.185, which added the Collect data for database mount state parameter. With this release, the Knowledge Script ignores the parameter for jobs created with older versions of the module. (ENG310172)
Discovery fails PowerShell host module error. This release resolves an issue where the Discovery_Exchange2007 Knowledge Script fails with the error Error loading AppManager PowerShell host module. With this release, AppManager for Exchange 2007 and 2010 completes discovery instead of reporting this error. (ENG313566)
This release resolved the following issues:
Jobs sometimes fail when running one of the Exchange2007_MBS Knowledge Scripts. This release resolves an issue in which running an MBS Knowledge Script, such as Exchange2007_MBS_DatabaseStatus, sometimes resulted in a System.TimeoutException error message. With this release, changes to the code of all of the MBS Knowledge Scripts improve the overall performance of the scripts and prevent the error messages from being generated. (ENG292710)
Running the PowerShell versions of the Exchange 2007 Knowledge Scripts generates error events. This release resolves an issue in which the PowerShell versions of the Exchange 2007 Knowledge Scripts generated an event message that said the communication object is in the Faulted state. With this release, the PowerShellHost now supports sending complex structures, such as large hashtables containing other large hashtables and arrays, from the server to the client. As a result, running the PowerShell scripts no longer generate errors related to the communication object. (ENG298606)
The CAS_Connectivity Knowledge Script raises an error event if the user and the mailbox servers are in different Active Directory sites. This release resolves an issue in which the CAS_Connectivity Knowledge Script raised an error event that said it cannot reset credentials if you ran the CAS_Connectivity script on Exchange servers found in different Active Directory sites. With this release, the script can now run on Exchange servers found in different Active Directory sites. (ENG298059)
The AppManager pre-installation check fails on an Exchange Server 2007 server. This release resolves an issue in which the pre-installation check used with the AppManager installation program did not properly check the 64-bit registry hive, preventing the installation of the managed object on an Exchange Server 2007 server. With this release, the pre-installation check now looks for Exchange keys in the 64-bit registry hive as well as the 32-bit registry hive, which prevents the check from failing on Exchange Server 2007 servers. (ENG294290)
Log files from the All_BestPracticesAnalyzer Knowledge Script do not get deleted after each iteration. This release resolves an issue in which the log files generated by the All_BestPracticesAnalyzer Knowledge Script created two log files that continued to grow without ever being deleted. With this release, the script creates the two log files in the NetIQ\Temp\netiq_debug folder, and the script deletes both log files with each iteration. (ENG295994)
Running the MBS_DatabaseStatus Knowledge Script causes slow CPU performance in some monitored Exchange servers. This release resolves an issue in which running the MBS_DatabaseStatus sometimes caused the server that executes the PowerShell scripts, MCPSHostServer.exe, to consume up to 30% of the CPU for some of the Exchange servers being monitored by the script. With this release, the addition of new code lets the MBS_DatabaseStatus script count the number of mailboxes per database and storage group, which improves CPU efficiency as a result. (ENG298152)
The MBS_DatabaseStatus Knowledge Script contains incomplete data collection parameters. This release resolves an issue in which the MBS_DatabaseStatus script did not collect sufficient data for the mailbox and public mount database status. This release includes a new parameter in the Monitor Database Mount State folder called Collect data for database mount state?. Data collection for the database mount status correctly generates data streams when you select this parameter. (ENG291236)
Jobs fail when running the MBS_DatabaseStatus PowerShell Knowledge Script. This release resolves an issue in which Exchange2007_MBS_DatabaseStatus.ps1 jobs failed with an error message that said An error occurred during parsing or execution of the PowerShell script. With this release, a change in the MBS_DatabaseStatus Knowledge Script fixes this issue and prevents the job from failing. (ENG301158)
This release provided the following enhancements:
Support for monitoring Exchange 2010 servers.
Support for monitoring Exchange 2007 and Exchange 2010 servers at the same time.
Support for the upgrade from AppManager for Microsoft Exchange Server 7.3 to 7.4 on any Exchange 2007 server.
Support for database availability groups (DAGs) on Exchange 2010. This module supports the discovery and monitoring of mailbox databases in DAGs.
Support for discovery of a clustered mailbox server (CMS) and a DAG using a FQDN. Before this release, when you discovered the AppManager virtual server object (a CMS) using a fully qualified domain name (FQDN), the Discovery_Exchange2007 Knowledge Script did not work for that object, and an event was raised. With this release, you can use a FQDN to successfully discover a CMS without raising an event. This release also includes support for using a FQDN to discover a database availability group (DAG) on Exchange Server 2010. (ENG288107)
This release also introduces the following new Knowledge Scripts:
Discovery_ExchangeDAG discovers the virtual object for a Microsoft Exchange Server 2010 DAG.
MBS_DatabaseStateChange monitors changes in the database state, such as active, passive, or suspended, of the mailbox databases on an Exchange Server in a DAG or a CMS.
Support for the following was added to this release of AppManager for Microsoft Exchange 2007:
Microsoft Exchange Server 2010 Service Pack 1.
Microsoft Exchange Server 2007 Service Pack 3.
Standby Continuous Replication (SCR) environments.
This release resolved the following issues:
MBS_DatabaseStatus does not monitor disk space usage for mount points. This release resolves an issue in which the MBS_DatabaseStatus Knowledge Script job does not monitor disk space usage for drives created on mount points. Instead, the script monitors only disk space usage for the root drive. For example, if you have mount points created on the E: drive, only disk space usage for the E: drive is monitored, not the disk space usage for any mount point created on the E: drive. After you install this release, a code change enables the MBS_DatabaseStatus script to monitor mailbox databases, public folder databases, and storage group log files when they are located on drives on mount points. (ENG276941, ENG282046)
Transport_BackPressure raises events when status is normal. This release resolves an issue in which the Exchange2007_Transport_BackPressure Knowledge Script job raises events when the status of back pressure is “normal.” After you install this release, a code change prevents the raising of events for normal back pressure. In addition, the Event severity when back pressure is normal parameter is removed from the Values tab of the Transport_BackPressure Knowledge Script. The script now raises events only when back pressure status is “medium” or “high.” (ENG284395)
This release resolved the following issue:
Transport_QueueStatus job may raise unrequested events for remote delivery queue. Before you install this release, the Exchange2007_Transport_QueueStatus Knowledge Script occasionally raises events for increase in queue size even when you do not select Yes for the Raise event if increase in queued messages exceeds threshold? parameter. After you install this release, a change in the script's code prevents the raising of events when events are not requested. (ENG280518)
This release resolved the following issues:
MBS_DatabaseStatus does not completely monitor Public Folder databases. Before you install this release, the Exchange2007_MBS_DatabaseStatus Knowledge Script does not monitor free disk space for disks holding Public Folder databases. Nor does it monitor the mount status of those databases. After you install this release, a code change allows the script to run on Public Folder database objects to monitor free disk space and database mount status. (ENG277607)
Discovery assigns mailbox databases to multiple storage groups. Before you install this release, for Exchange 2007 environments in which portions of storage group names are the same (such as storage groups “A” and “A1”), the Discovery_Exchange2007 Knowledge Script job may discover a mailbox database in every similarly named storage group, rather than only in the storage group that actually holds the mailbox database. This multiple discovery causes many instances of the same mailbox database to appear in the TreeView pane. Subsequently, MBS_DatabaseStatus or MBS_MailboxUsage Knowledge Script jobs running on the mailbox database raise error events. After you install this release, the Discovery job discovers mailbox databases only for the storage groups that hold those databases. (ENG278894)
NOTE:After installing this release, delete the incorrect MBS (Mailbox Server) objects from the TreeView. If you delete your entire MBS hierarchy, run Discovery_Exchange2007 to recreate the correct storage group and mailbox database objects.
Prerequisite check fails. Before you install this release, the prerequisite checking program (ckExchange2007.exe) may fail, although the maint.log file indicates all prerequisite checks passed. After you install this release, a code change in ckExchange2007.exe allows the prerequisite check process to continue successfully. (ENG278972)
This release introduced support for cluster awareness in Knowledge Scripts whose names begin with All and MBS. These scripts are described below. The cluster-aware Knowledge Scripts can monitor resources on each node in a cluster and on each CMS as it moves from node to node as a result of failover. For more information, see the AppManager for Microsoft Exchange Server 2007 Management Guide, included in the download package.
This release also provides many new Knowledge Scripts created to replace the consolidated functionality of existing scripts with more granular functionality for greater control over monitoring. In contrast to the few existing scripts, which can, for example, monitor every function of the Client Access server, each new script is specially designed to monitor a specific aspect of a Server Role. The prefix of each new script identifies the Server Role the script monitors. The All_* Knowledge Scripts can run on all Server Roles.
All_BestPracticeAnalyzer monitors the Windows Event Log for errors and warnings raised by the Exchange Best Practices Analyzer.
All_ClockSynchronization monitors the synchronization of clocks for one or more Domain Controllers.
All_EventLog monitors the Windows Application event log for errors and warnings related to Exchange 2007.
All_ServiceStatus monitors the status of Exchange 2007 services.
CAS_Activity monitors Client Access server services and functions: Availability Service, ActiveSync, Outlook Web Access, Outlook Web services, IMAP4, and POP3.
CAS_Connectivity monitors connectivity for Client Access server services: ActiveSync, Outlook Web Access, Outlook Web services, and the Autodiscover service.
CAS_OABAvailability monitors whether offline address books can be downloaded.
CAS_PublicFolderAvailability monitors the accessibility of public folders on the Client Access server.
ETS_ExternalMail monitors email sent to and from your Exchange environment.
ETS_MessageHygiene monitors message hygiene functions for the Edge Transport server.
HTS_Connectivity monitors the status of send, receive, and foreign connectors, monitors connectivity with a Mailbox server, and monitors the time of the last synchronization with the Edge Transport server.
HTS_SendersAndRecipients measures the number of messages in the mailbox and total message size for senders and recipients.
HTS_TransportDumpster monitors Transport Dumpster activity, availability, and the number of items in the Transport Dumpster.
MBS_ClusterOwner determines whether a selected Exchange Server is the owner of its node and whether the CMS is down.
MBS_DatabaseStatus monitors mailbox databases for mount status, size of online maintenance window, defragmentation time, free disk space, free log space, free file space, and number of mailboxes.
MBS_MailboxAccessibility monitors the ability of the Mailbox server to access individual mailboxes.
MBS_MailboxUsage measures the size of mailboxes by either the number of messages in the mailbox, or by total message size in MB.
MBS_MailFlow tests the flow of mail by sending test e-mail to local or remote Mailbox servers.
MBS_MessagingRecordsMgmt monitors message management tasks such as deleting, journaling, moving, and retention.
MBS_PublicFolderUsage measures the size of public folders by the number of messages in the folders or by total message size in MB.
MBS_Replication monitors replication status and performance for a Mailbox server.
Transport_BackPressure monitors the status of back pressure for the Hub Transport server.
Transport_QueueStatus monitors the status of queues on the Hub Transport server: submission queue, mailbox delivery queue, remote delivery queue, poison message queue, and unreachable destination queue.
UMS_CallActivity monitors call activity on the Unified Messaging server: voice fax, play on phone, auto attendant, subscriber access, and prompt editing.
UMS_Connectivity monitors connectivity to Hub Transport servers, Mailbox servers, Active Directory, and phones.
UMS_Failures monitors failures related to redirected calls, disconnected calls, and access to Active Directory, the Hub Transport server, and the Mailbox server.
UMS_Performance monitors user response latency, operation response time, queued messages, queued OCS user notifications, and disconnected calls.
RECOMMENDED_Exchange2007 Knowledge Script Group contains 14 of the new scripts available in this release. Run the KSG on your Exchange Server 2007 resources to run all recommended Knowledge Scripts at the same time.
This release also includes an Analysis Center report package that provides new report templates in several categories:
Client Access server reports. Three reports summarize the average number of login failures, the average login rate for user sessions, and the average number of users logged onto Outlook Web Access.
Hub Transport server report. Report summarizes average usage for the Transport Dumpster queue: number of items in the queue, size of items in the queue, insertion rate, deletion rate, and number of redeliveries.
Mailbox server reports. Seven reports summarize average disk usage, average mail flow response time, average size of copy queue, average size of replay queue, average number of messages specified mailboxes, average size of specified mailboxes, and the average use of File Share Witness.
Unified Messaging server reports. Three reports summarize average call activity by call time, average number of UMS operations, and average number of UMS-related failures.
General reports. Two reports summarize Exchange Server 2007 performance and event data.
Knowledge Scripts available in previous releases of the module are no longer available. Knowledge Script enhancement efforts will focus only on the new Knowledge Scripts. However, if you are already using some or all of these obsolete scripts, you can continue to use them.
Availability
BestPracticesAnalyzer
DataCollection
Health
Report Knowledge Scripts, which have been replaced by Analysis Center reports:
Report_CopyQueueLength
Report_DataLostInReplication
Report_DiskUsageStatus
Report_FileShareWitnessusage
Report_ReplayQueueLength
Report_TransDumpUsage
RECOMMENDED_ExchangeServer2007 Knowledge Script Group
Hotfix 71505 resolved the following issues:
Availability and DataCollection scripts fail when File Share Witness cannot be found. Before you install this release, the Exchange2007_Availability and Exchange2007_DataCollection Knowledge Script jobs fail if the File Share Witness resource on a clustered server has been renamed. Neither job is able to find a renamed resource. After you install this release, both jobs properly identify and find a renamed File Share Witness resource. (ENG258507)
Health script erroneously raises event for mailboxes on Mailbox servers. Before you install this release, the Exchange2007_Health Knowledge Script job raises an event indicating that no mailbox databases can be found on a Mailbox server. Some Mailbox servers exist only to provide Public folders and therefore would not contain mailbox databases. After you install this release, the Health job no longer raises an event if a Mailbox server contains no mailbox databases. (ENG262510)
Health script fails when monitoring remote sites. Before you install this release, the Exchange2007_Health Knowledge Script job sometimes fails when it attempts to monitor a Mailbox server that is in the same domain as others being monitored, but at a different site. After you install this release, two new parameters let you identify any Mailbox servers you want to exclude from monitoring and let you define the length of the monitoring attempt. (ENG263712)
Comma-separated list of Mailbox servers to ignore. For this parameter, provide the names of the Mailbox servers you want to exclude from monitoring. Separate multiple names with a comma.
Timeout for communicating with each Mailbox server. For this parameter, indicate how long the Health script should attempt to communicate with a Mailbox server before timing out and raising an event. The default timeout period is 60 seconds.
Health and BestPracticesAnalyzer scripts do not execute selected actions. Before you install this release, Action Knowledge Script jobs fail when associated Exchange2007_Health or Exchange2007_BestPracticesAnalyzer Knowledge Script jobs are running on clusters. After you install this release, a change to the code for the Exchange2007_Health and Exchange2007_BestPracticesAnalyzer Knowledge Scripts allows the Action Knowledge Script jobs to run successfully on clusters. (ENG264367)
Health script fails when attempting to find CAS mailbox databases. Before you install this release, the Exchange2007_Health Knowledge Script job fails when it attempts to find mailbox databases on Client Access Servers. The text of the error indicates that the script does not have permission to run the Get-MailboxDatabase command. After you install this release, a change to the code for the Exchange2007_Health Knowledge Script allows it to successfully run the Get-MailboxDatabase command. (ENG264732)
Health script fails when creating CAS mailbox. Before you install this release, the Exchange2007_Health Knowledge Script job fails when it attempts to create a mailbox while testing the Client Access Server. The script attempts to create a mailbox in the root domain, for which it does not have write permissions, rather than in the current domain, for which it does have write permissions. After you install this release, the Health job properly creates a mailbox in the current domain. (ENG264946)
Exchange2007 Knowledge Scripts raise invalid cluster failover event. Before you install this release, Exchange2007 Knowledge Script jobs incorrectly determine that a cluster failover is in progress for the passive node. After you install this release, a change to the code for all Exchange2007 Knowledge Scripts allow them to correctly determine cluster ownership and to raise a failover event only when failover is occurring. (ENG266128)
Hotfix 71422 resolved the following issues:
Excessive “active/passive” status events raised by four Knowledge Scripts. Before you install this release, the Availability, BestPracticesAnalyzer, DataCollection, and Health Knowledge Scripts, by default, raise informational events related to a cluster node's active or passive status. These events are raised with every job iteration and can overwhelm the contents of the Events view. After you install this release, the Health, Availability, and BestPracticesAnalyzer Knowledge Scripts no longer raise “active/passive” status events by default. A new parameter, Raise event indicating active/passive cluster state?, lets you control when to raise informational events. (ENG250661)
No means of monitoring subset of services, storage groups, transport queues, and mailbox databases. Before you install this release, you cannot run the Availability, DataCollection, and Health Knowledge Scripts on individual storage group or mailbox database objects, nor can you run the Health Knowledge Script on individual service and transport queue objects. In addition, the scripts do not provide a means of specifying a particular subset of objects to monitor. After you install this release, you can run the scripts on service, storage group, transport queue, or mailbox database objects (as appropriate) and then use the Objects tab of the scripts' Properties dialog box to specify which individual service, storage group, or mailbox database you want to monitor. (ENG257614)
Uninformative “mail flow failed” error from Health Knowledge Script. Before you install this release, when the Exchange2007_Health Knowledge Script job raises an event for a failed mail flow check, the event details do not indicate the reason for the failure. After you install this release, the event details for a mail flow error describe the cause of the failure. In addition, the Knowledge Script now waits longer for the mail flow check to complete, which helps prevent the Health Knowledge Script job from stopping before the mail flow check is complete. (ENG258258)
Hotfix 71193 resolved the following issues:
Health script causes Powershell exception. Before you install this release, the Exchange2007_Health Knowledge Script generates a Powershell exception when your screen resolution settings conflict with the settings of the output of the script. After you install this release, the Health script attempts to set the highest resolution possible without generating an exception. (ENG249034)
Health script does not properly monitor the Offline Address Book or HTS server communication. Before you install this release, the Exchange2007_Health Knowledge Script does not raise events when Offline Address Books cannot be downloaded or when the Hub Transport Server role cannot communicate with any mailbox servers. After you install this release, the Health script properly raises events for the indicated conditions. (ENG249423)
Health script fails when monitoring a Public Folder server. Before you install this release, the Exchange2007_Health Knowledge Script raises an event when it cannot find mailbox databases on a dedicated Public Folder server. However, dedicated Public Folder servers do not contain mailbox databases. After you install this release, the Health script properly detects the absence of mailbox databases and does not raise an event. (ENG249688)
This release offered the following enhancements:
New monitoring capability in the Health Knowledge Script:
Limiting Exchange Servers to test. A new parameter, Communicate only with Exchange Servers in the local domain?, allows the Health job to test only Exchange Servers in the same domain as the server on which you run the Health Knowledge Script. When this parameter is not set to Yes, health tests for the Client Access Server and the Hub Transport Server attempt to contact all Mailbox Servers in your organization. These tests will fail if the Exchange accounts in one domain do not have access to other domains.
Selecting Domain Controllers for clock synchronization test. A new parameter, Comma-separated list of Domain Controllers to test, allows you to select which Domain Controller clocks are tested for synchronization with the clock on the server on which you run the Health Knowledge Script. When this parameter is not set to Yes, the Health Knowledge Script tests synchronization for all Domain Controller clocks in your organization.
Service Pack 1. This release offered support for Microsoft Exchange Server 2007, Service Pack 1.
Reworded parameters for the Availability Knowledge Script. The reworded parameters provide a better explanation of the functions of the script. (ENG245034)
This version of AppManager for Exchange 2007 supported the monitoring of Exchange Server 2007 resources installed in clustered and non-clustered environments. The supported cluster environments are CCR (Cluster Continuous Replication), SCC (Single Copy Cluster), LCR (Local Continuous Replication), and distributed environment.
This release also introduced the following new Knowledge Scripts:
Availability monitors the availability of the Exchange Server Mailbox and Hub Transport Roles.
Report_CopyQueueLength generates graphs and charts of the copy queue messages per second depending on the specified period.
Report_FileShareWitness generates a report for the percentage usage of file share witness used at a given instance.
Report_ReplayQueueLength generates graphs and charts of the replay queue messages per second depending on the specified period.
Report_DiskUsageStatus generates a report about the graphs and charts for the percentage time required for the disk access, read, and write operations.
Report_TransDumpUsage generates a report about the number of emails in the dumpster at a given instance and also the space allocated for the transport dumpster.
The AppManager for Microsoft Exchange Server and Exchange Online product and all updates and modifications thereto (“Software”) is distributed with certain third-party software and open source software (as may be defined in the license agreement provided with the Software).
The following third-party and open source software are included with the Software and are licensed for distribution according to the terms described in this document and any use thereof must be in accordance with such terms, solely in conjunction with your internal use of the Software, and - unless explicitly contradicted below - consistent with the terms and conditions set forth in the applicable license agreement for the software. No further licenses are granted.
Log4net, Copyright 2001-2007 The Apache Software Foundation, Apache License Version 2.0, January 2004 http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
Definitions. “License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.
“Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
“Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means:
the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or
ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
beneficial ownership of such entity.
“You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License.
“Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.
“Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.
“Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).
“Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.
“Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.”
“Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:
You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a “NOTICE” text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.
Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.
Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information website.
For general corporate and product information, see the NetIQ Corporate website.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
For information about NetIQ legal notices, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.
Copyright (C) 2021 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see https://www.netiq.com/company/legal/. All third-party trademarks are the property of their respective owners.