Users Guide
Table Of Contents
- OpenManage Integration Version 7.0 for Microsoft System Center User’s Guide
- Contents
- Introduction
- About OMIMSSC components
- About Admin Portal
- Launching OMIMSSC from enrolled MSSC console
- Use cases
- Profiles
- Launching Configuration and Deployment
- Discovering servers and synchronizing with MSSC console
- About reference server configuration
- Discovering servers in OMIMSSC
- Server discovery in OMIMSSC console extension for SCCM
- Server discovery in OMIMSSC console extension for SCVMM
- System requirements for managed systems
- Discovering servers using auto discovery
- Discovering servers using manual discovery
- Synchronizing OMIMSSC console extensions with enrolled SCCM
- Synchronizing OMIMSSC console extension with enrolled SCVMM
- Synchronizing with enrolled MSSC
- Resolving synchronization errors
- Deleting servers from OMIMSSC
- Launching iDRAC console
- OMIMSSC licensing
- Operational Template
- Preparing for deployment
- Managing Operational Template
- Integration with Dell Repository Manager(DRM)
- Maintenance
- Viewing information in OMIMSSC
- Troubleshooting
- Deploy option not visible in task sequence
- Duplicate VRTX chassis group gets created
- Empty cluster update group does not get deleted during autodiscovery or synchronization
- Failure of creation of update source
- Failure of firmware update because of job queue being full
- Failure of firmware update on cluster update group
- Failure of firmware update on 11th generation of servers
- Failure of firmware update while using DRM update source
- Failure of scheduled job on an update group
- Failure to apply Operational Template
- Failure to access CIFS share using hostname
- Failure to connect to FTP using system default update source
- Failure to create a repository during a firmware update
- Failure to delete a custom update group
- Failure to display Jobs and Logs
- Failure to export LC logs in CSV format
- Failure to export server profiles
- Failure to display Dell EMC logo in OMIMSSC Admin Portal
- Failure to view LC logs
- Firmware update on a few components irrespective of the selection
- Hypervisor deployment failure
- Hypervisor deployment failure due to driver files retained in library share
- Hypervisor deployment failure for 11th generation PowerEdge blade servers when using Active Directory
- Incorrect credentials during discovery
- IG installation issue while running multiple instances of the installer on the same server
- Importing server profile job gets timed out after two hours
- Latest inventory information is not displayed even after firmware update
- SCVMM error 21119 while adding servers to active directory
- Appendix
- Accessing support content from the Dell EMC support site
versions required for systems on which you are deploying the operating systems. Use the latest version of the file, and do
not use the Dell OpenManage Deployment Toolkit Windows Driver Cabinet file for the WinPE update.
1. Add the PXE server to the OMIMSSC Appliance.
2. After adding the PXE server, copy the boot.wim file from the PXE server to OMIMSSC IG for the SCVMM share WIM
folder. The boot.wim is present in the following path: C:\RemoteInstall\DCMgr\Boot\Windows\Images
NOTE: Do not change the filename of the boot.wim file.
Extracting DTK drivers
DTK is a self-extracting executable file.
To work with DTK:
1. Double click the DTK executable file.
2. To extract the DTK drivers, select the folder, for example C:\DTK501.
3. Copy the extracted DTK folder to the IG's DTK share folder. For example \\OMIMSSC IG Share\DTK\DTK501
NOTE: If you are upgrading from SCVMM SP1 to SCVMM R2, then upgrade to Windows PowerShell 4.0. and create a
WinPE ISO image.
Updating WinPE image
1. In OMIMSSC, select WinPE Update, under Image Source, for Custom WinPE Image Path, provide the WinPE image
path.
For example, \\OMIMSSC IG Share\WIM\boot.wim.
2. Under DTK Path, for DTK Drivers Path, provide the location for the Dell Deployment Toolkit drivers.
For example, \\OMIMSSC IG Share\DTK\DTK501
3. Provide either of the files for:
● Provide WIM file name for SCCM.
● Provide ISO file name for SCVMM.
4. To view the job list, select Go to the Job List.
A unique job name is assigned to each Windows Preinstallation Environment (WinPE) update.
5. Click Update.
WinPE ISO with the name provided in the preceding step is created under \\OMIMSSC IG Share\ISO.
Task sequence
Task sequence is used to capture the operating system image, or deploy an operating system on SCCM console.
Before creating Operational Template, it is recommended that you complete the following prerequisites.
● In Configuration Manager, ensure that the system is discovered and present under Assets and Compliance > Device
Collections > All Dell Lifecycle Controller Servers. For more information, see Server discovery.
● Install the latest BIOS version on the system.
● Install the latest version of Lifecycle Controller on the system.
● Install the latest version of iDRAC firmware on the system.
NOTE: Always launch the Configuration Manager console with administrator privileges.
Creating a task sequence
You can create a task sequence in two ways which will be used for server configurations:
● Create a Dell-specific task sequence using OMIMSSC Deployment template.
● Create a custom task sequence.
Operational Template
29