When using iMonitor to browse an eDirectory tree for objects, an object with double-byte characters in the name might not correctly hyperlink to the object properties.
The Agent Health check feature in iMonitor shows a Warning icon in the Results column when run on a single server tree because of the Perishable Data status. This does not mean that the tree is not healthy or that the Agent Health check is not working as designed. Perishable Data indicates the amount of data that has not yet been synchronized to at least one replica. A single server tree, by its nature, means that the data is always at risk for catastrophic failure because there is no other place that the data is replicated. If you lose the hard disk, you lose the data.
If you don't want to view health check warnings about Perishable Data or Readable Replica Counts on your single server tree, you can turn off these health checks by editing the ndsimonhealth.ini file to change the following entries:
perishable_data-active: OFF
and
ring_readable-Min_Marginal: 1 or ring_readable-active: OFF
This turns off the warnings for Readable Replica Count and Perishable Data.
The custom reports feature in iMonitor is designed to place the URL specified by the user into the saved report (the saved HTML file) when the custom report is created. That means that when you open a saved custom report that has been run, you see the live (current) data instead of the data captured by the URL at the time the custom report is run. This issue will be resolved in a future release of iMonitor.
Because Linux platforms do not maintain the creation time of a file, iMonitor shows both the creation and modification times to be the same.
The navigation and assistant frames appear twice on Linux.
To work around this problem, refresh the page.
Linux: iMonitor displays error -672 if dsdump tool is running in parallel with iMonitor. To resolve this issue, exit the dsdump tool, before starting iMonitor.
Windows: iMonitor displays error -672 if the dsbrowse or dsedit tool is running in parallel with iMonitor. To resolve this issue, exit the dsbrowse and dsedit tool before starting iMonitor.
If you set a Time syntax attribute with a value prior to January 1, 1970, iMonitor displays the time stamp for the attribute in hexadecimal format instead of in standard date/time format. iMonitor displays all attributes with values after January 1, 1970, in date/time format.
Trace configuration in iMonitor does not work in Internet Explorer 10.
To work around this issue, launch Internet Explorer 10 in compatibility mode and iMonitor address to the list of Trusted Sites, then restart the browser.