Known issues

This section details the known issues in version 2.1.0, along with possible workarounds (if workarounds are available).

Note:

For comprehensive information about known issues in Microsoft System Center Operations Manager 2007 R2, see the Microsoft System Center Operations Manager 2007 R2 online release notes.
For comprehensive information about known issues in Microsoft System Center Operations Manager 2012, see the Microsoft System Center Operations Manager 2012 online release notes.

Ticket ID	Description
SCOM-238811	The detection of IBM® DS8000® storage systems stops if volumes on these systems have names with non-ASCII characters. Currently there is no workaround for this limitation (SCOM-238811).
SCOM-260923	In some cases, the monitoring host can not be discovered after a certain IBM management pack is manually deleted and then and imported again. To resolve this issue, delete the same management pack again and then import it again. Alternatively, you can shorten the management pack object discovery interval to 30 seconds or less (for more information, refer to the relevant Microsoft SCOM documentation).
SCOM-261133	After upgrading to version 2.1.0 by installing it over version 1.1.0, the configuration that was made with version 1.1.0 is no longer valid. To resolve this issue, run the upgrade_config.cmd CLI utility after version 2.1.0 is installed. For more information, refer to the user guide.
SCOM-261154	For XIV® storage systems, only one volume is displayed as a logical component in SCOM if there are two or more volumes that share the same name with different uppercase and lowercase letters. Currently there is no workaround for this limitation (SCOM-261154).
SCOM-261147	For SAN Volume Controller and Storwize® systems, the same event might be displayed several times under Events, each time with a different timestamp. This occurs if the event is reported by the storage system each time with an updated timestamp. This is a design behaviour that might be changed in a future management pack version. No workaround is available.
SCOM-261151	Physical drives with an empty enclosure ID are not displayed for Storwize V3500 or Storwize V3700 systems. Currently there is no workaround for this limitation (SCOM-261151).