Release Notes

Known issues and resolutions
● Issue 1
Description:
System Center Administrator console will crash while importing OMIMSSC console extension in certain System Center
versions. System Center versions where the issue may be seen : SC2016 VMM RTM build 4.0.1662.0, SC2012 VMM UR5 or
later.
Workaround:
As a workaround for SC2016 VMM RTM build 4.0.1662.0 version, upgrade SCVMM using the 4094925 KB article
available at support.microsoft.com/kb/4094925, and then import the OMIMSSC console extension. For information
about this issue in SC2012 VMM UR5 or later and resolving the issue, see issue 5 in the knowledge base URL:
support.microsoft.com/kb/2785682.
● Issue 2
Description:
After logging in to OMIMSSC Console extension for MECM with different credentials used to login to Microsoft console, the
login activity fails with following error message: Failed to login. Ensure to use correct credentials or
check if account is locked in Active Directory.
Workaround: As a workaround, ensure to use correct credentials or check if account is locked in Active Directory. For more
information on Active Directory account lockout policies see, Microsoft Documentation.
● Issue 3
Description:
If user names are same and the passwords are different for the domain user account and local user account, then the test
connection between Microsoft console and OMIMSSC Appliance fails.
For example, domain user account is: domain\user1 and password is pwd1. And local user account is user1 and
password is Pwd2 . When you try to enroll with the above domain user account, the test connection fails.
Workaround:
As a workaround, use different user names for the domain user and local user accounts, or use a single user account as local
user and during Microsoft console enrollment in OMIMSSC Appliance.
● Issue 4
Description:
When accessing the OMIMSSC admin portal by using Mozilla Firefox browser, you get the following warning message:
“Secure Connection Failed”.
Workaround:
As a workaround, delete the certificate created from a previous entry of the admin portal in the browser. For information
about deleting certificate from Mozilla Firefox browser, see support.mozilla.org
● Issue 7
Description:
When a cluster is discovered in OMIMSSC, a cluster update group gets created in the Maintenance Center with all the
servers listed in the cluster update group. Later, if all the servers are removed from this cluster through SCVMM, and an
autodiscovery or synchronization with SCVMM operation is performed, the empty cluster update group is not deleted in
Maintenance Center.
Workaround:
As a workaround, to delete the empty server group, rediscover the servers.
● Issue 8
Description:
6
Known issues and resolutions 9