Dell EMC OpenManage Integration for Microsoft System Center Version 7.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2018 - 2019 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Resources required for managing OMIMSSC...................................................................................5 2 Verifying permissions for using OMIMSSC console extension for SCCM........................................... 6 Configuring user access to WMI......................................................................................................................................... 6 3 Verifying PowerShell permissions for using OMIMSSC console extension for SCVMM.............
Failure of firmware update because of job queue being full........................................................................................... 17 Failure of firmware update when using DRM update source ........................................................................................ 18 Firmware update on components irrespective of selection............................................................................................
1 Resources required for managing OMIMSSC Use this guide to check for required privileges and solve any problems encountered in OMIMSSC. To troubleshoot any issues faced in OMIMSSC, ensure that you have the following resources: • Read-only user’s account details to login to OMIMSSC Appliance and perform various operations. • For logging in as a read-only user from OMIMSSC Appliance VM, enter user name as readonly with the same password used to login to OMIMSSC Appliance VM.
2 Verifying permissions for using OMIMSSC console extension for SCCM After installing OMIMSSC, verify that the enrolled user has the following permissions: 1. On the system where OMIMSSC is installed, provide the Write permissions for the \XmlStorage\Extensions\DLCPlugin folder using PowerShell commands.
a) b) c) d) Launch dcomcnfg.exe. Expand My Computer > DCOM Config. Right-click Windows Management and Instrumentation, and select Properties. On Security, from Launch and Activation Permission, click Edit and select the Remote Launch and Remote Activation permissions. 3. Set the namespace security and grant permissions. To set namespace security and grant permissions: a) b) c) d) e) f) Launch wmimgmt.msc In WMI Control pane, right-click WMI Control, select Properties, and then select Security.
3 Verifying PowerShell permissions for using OMIMSSC console extension for SCVMM Check if the PSRemoting status is enabled and ExecutionPolicy is set to RemoteSigned. If the status is different then perform the following steps in PowerShell: a) In PowerShell, run the command: PSRemoting. If the PSRemoting command is disabled, run enable the PSRemoting command using the following commands. 1. Run the command: Enable-PSRemoting 2. In the confirmation message, type Y.
4 Install and upgrade scenarios in OMIMSSC This section has all the troubleshooting information related to installing and upgrading OMIMSSC. Verifying OMIMSSC Appliance VM configuration To verify that the OMIMSSC Appliance VM is configured appropriately, select and then right-click the OMIMSSC Appliance VM, click Settings, and then perform the following tasks: 1.
• • Ensure that the SCVMM server is not registered with any other OMIMSSC Appliance. If you want to register the same SCVMM server with the OMIMSSC Appliance, then delete the OMIMSSC Registration Profile application profile from the SCVMM server. If you have applied SCVMM roll up update, then check the Indigo TCP port number of SCVMM console in registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager AdministratorConsole\Settings).
As a workaround, upgrade SCVMM using the 4094925 KB article available at support.microsoft.com/kb/4094925, and then import the OMIMSSC console extension.
5 OMIMSSC admin portal scenarios Error message while accessing OMIMSSC admin portal through Mozilla Firefox browser When accessing the OMIMSSC admin portal by using Mozilla Firefox browser, you get the following warning message: “Secure Connection Failed”. 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.
6 Discovery, synchronization and inventory scenarios in OMIMSSC Failure to discover servers When multiple Microsoft consoles are enrolled to an OMIMSSC Appliance, and you try to discover a server, if even one of the SCCM consoles are not reachable, then the server discovery job will fail. As a workaround, de-enroll the SCCM console that is not reachable, or fix the errors and ensure that the SCCM console is reachable from OMIMSSC Appliance.
2. Manually delete all the servers in the VRTX chassis group, and then rediscover the servers. Unable to synchronize host servers with enrolled SCCM During synchronization of OMIMSSC console extension with enrolled SCCM, the servers are not listed as sub tasks in synchronization job and hence does not get synchronized. As a workaround, launch SCCM console with "Run as Administrator Privilege" and update out of band configuration for a server. Then synchronize OMIMSSC console extension with enrolled SCCM.
7 Generic scenarios in OMIMSSC Failure to access CIFS share using hostname The modular servers are not able to access the CIFS share using the host name for performing any job in OMIMSSC. As a workaround, specify the IP address of the server having the CIFS share instead of the host name. Failure to display Jobs and Logs page in console extension The Jobs and Logs Center page is not displayed in OMIMSSC console extensions. As a workaround, re-enroll the console and then launch the Jobs and Logs page.
8 Firmware update scenarios in OMIMSSC Failure of creation of update source When the Domain Name System (DNS) network configuration of the Appliance is changed, creation of HTTP or FTP type of update source fails. As a workaround, restart the Appliance, and then create the update source of type HTTP or FTP.
Failure to display comparison report after upgrading or migrating OMIMSSC After upgrading to the latest version of OMIMSSC, if the connection to ftp.dell.com or downloads.dell.com fails, the default Dell online FTP, or Dell HTTP update source cannot download the catalog file. Hence, the comparison report is not available.
Failure of firmware update when using DRM update source Firmware update job may fail if you are using DRM update source with insufficient access to the share folders. If the Windows credential profile provided while creating DRM update source is not a part of domain administrator group or the local administrator group, the following error message is displayed: Local cache creation failure. As a workaround, perform the following: 1.
Failure of firmware update on 11th generation of servers Firmware updates applied on 11th generation of PowerEdge servers may fail due to incompatible versions of iDRAC and LC with the following error: WSMan command failed to execute on server with iDRAC IP . As a workaround, upgrade the iDRAC and LC to the latest versions, and then apply the firmware updates. The table lists out the latest versions of LC and iDRAC. Table 1.
9 Operating system deployment scenarios in OMIMSSC Operating system deployment generic scenarios This section has all the generic troubleshooting information related to operating system deployment. Failure to deploy Operational Template After deploying the Operational Template on the selected servers, the attributes or attribute values are not appropriate for the selected .CSV file, or the iDRAC IP or iDRAC credentials are changed due to the configurations in the template.
Failed to add servers into Managed Lifecycle Controller Lifecycle Controller ESXi collection in SCCM If the DHCP lookup fails while operating system deployment, then the server times out and the server is not moved into Managed Lifecycle Controller Lifecycle Controller (ESXi) collection in SCCM. As a workaround, install the SCCM client server, and then perform a synchronization to add the servers in Managed Lifecycle Controller Lifecycle Controller (ESXi) collection.
SCVMM error 21119 while adding servers to Active Directory While adding servers to Active Directory, SCVMM error 21119 is displayed. Error 21119: The physical computer with did not join Active Directory in time. The comptuer was expected to join Active Directory using the computer name . As a workaround, do the following: 1. 2. 3. 4. Wait for some time to see if the server is added to the Active Directory.
10 Server profile scenarios in OMIMSSC Failure to export server profiles After scheduling an export server profile job, the server profile is not exported, and the following error message is displayed: The selectors for the resource are not valid. As a workaround, reset iDRAC, and then schedule the export server profile job. For more information, see iDRAC documentation available at dell.com/support.
11 LC Logs scenarios in OMIMSSC Failure to export LC logs in .CSV format When you try to download the LC log files to .CSV format, the download operation fails. As a workaround, add the OMIMSSC Appliance FQDN in the browser under local intranet site. For information about adding the OMIMSSC Appliance in local intranet, see Viewing LC logs section in Dell EMC OpenManage Integration for Microsoft System Center Version 7.
12 Accessing documents from the Dell EMC support site You can access the required documents using the following links: • • • • • • • • For Dell EMC Enterprise Systems Management documents — www.dell.com/SoftwareSecurityManuals For Dell EMC OpenManage documents — www.dell.com/OpenManageManuals For Dell EMC Remote Enterprise Systems Management documents — www.dell.com/esmmanuals For iDRAC documents — www.dell.com/idracmanuals For Dell EMC OpenManage Connections Enterprise Systems Management documents — www.
