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. © 2009 - 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......................................................................................................................................
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.........................................................................................18 Failure to display latest inventory information after firmware update.
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 About this task After installing OMIMSSC, verify that the enrolled user has the following permissions: Steps 1 On the system where OMIMSSC is installed, provide the Write permissions for the \XmlStorage\Extensions\DLCPlugin folder using PowerShell commands.
• 2 From Launch and Activation Permission, click Edit Limits and select Local Launch, Remote Launch, and Remote Activation. To access the DCOM Config Windows Management and Instrumentation (WMI) components, provide user permissions to the enrolled user. To grant user permissions for DCOM Config WMI: a b c d 3 Launch dcomcnfg.exe. Expand My Computer > DCOM Config. Right-click Windows Management and Instrumentation, and select Properties.
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 b 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.
• The Microsoft account used to enroll the console should be a delegated admin or an administrator in System Center, and a local administrator for the System Center server. • Specific for SCVMM users: – 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.
As a workaround, check if the virtual switch is mapped to a physical switch, if the switch is configured correctly, and then connect to OMIMSSC Appliance. SCVMM crashes while importing OMIMSSC console extension SC2016 VMM RTM build 4.0.1662.0 Administrator console may crash when importing OMIMSSC console extension. 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 This section has all the troubleshooting information related to OMIMSSC’s admin portal 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.
6 Discovery, synchronization and inventory scenarios in OMIMSSC This section has all the troubleshooting information related to credentials issues, discovering servers, grouping servers, synchronizing enrolled Microsoft console with OMIMSSC when using 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.
Creation of incorrect VRTX chassis group after server discovery When modular servers that were previously in another chassis are added to a VRTX chassis and discovered in OMIMSSC, the modular servers carry previous chassis service tag information. Hence, a VRTX chassis group with old chassis information is created in the Appliance instead of the latest chassis information. As a workaround, do the following: 1 Enable CSIOR, and reset iDRAC on the newly added modular server.
7 Generic scenarios in OMIMSSC This section contains troubleshooting information which are independent of any workflow 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.
8 Firmware update scenarios in OMIMSSC This section has all the troubleshooting information related to update sources, update groups, repositories, and inventory after updates. 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.
As a workaround, ensure that the update source is reachable from where the OMIMSSC Appliance is hosted, and provide the correct credentials while creating an update source. 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.
Failure to update WinPE image When you try to update the WinPE image, update job may fail with the following error message: Remote connection to console failed. As a workaround, run the DISM command to clean up all previously mounted images in Microsoft console, and then retry to update the WinPE image.
9 Operating system deployment scenarios in OMIMSSC This section has all the troubleshooting information related to operating system, or hypervisor (for SCVMM) deployment using Operational Template in OMIMSSC. Operating system deployment generic scenarios This section has all the generic troubleshooting information related to operating system deployment.
1 Right-click the task sequence, and select Edit. 2 Select Restart in Windows PE. In the Description section, type any character and delete it so the change is not saved. 3 Click OK. This re-enables the Apply option.
To remove files from library share: 1 From SCVMM console, select Library > Library Servers and then select the IG server that was added as the library server. 2 In the library server, select and delete the library share. 3 After the library share is deleted, connect to the IG share using \\\LCDriver\. 4 Delete the folder that contains the driver files. After this, you can deploy the hypervisors.
As a workaround, clear the storage pool and disk configuration having existing cluster details and then create the Storage Spaces Direct cluster. For more information on clearing the storage pool, see Troubleshoot Storage Spaces Direct health and operational states section from Microsoft documentation.
10 Server profile scenarios in OMIMSSC This section has all the troubleshooting information related to exporting, and importing the server profiles 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.
11 LC Logs scenarios in OMIMSSC This section has all the troubleshooting information related to exporting, and viewing LC logs. 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.
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/esmmanuals • For Dell EMC OpenManage documents — www.dell.com/openmanagemanuals • For Dell EMC Remote Enterprise Systems Management documents — www.dell.com/esmmanuals • For iDRAC and Dell Lifecycle Controller documents — www.dell.
