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
Viewing Operational Template
To view Operational Template templates:
In OMIMSSC console, click Profiles and Templates, and then click Operational Template. All the Operational Template
templates created are listed here.
Editing Operational Template
You can edit an Operational Template to modify the update source, hardware configurations, and operating system components
of the reference server.
NOTE: Some attributes may depend on other attributes values. If these attributes are not updated, then applying hardware
configuration may fail. Hence, it is recommended to not edit the reference configuration.
NOTE: While editing task sequence on SCCM 2016 the missing objects references messages does not list the Setup
windows and ConfigMgr package. Add the package, and save the task sequence.
1. Select the template you want to modify and click Edit.
The Operational Template page is displayed.
2. Edit the name and description of the template (if required), and then click Next.
3. To view the available attributes and their values in Server Components, click a component.
4. Modify the values of the available attributes if necessary.
NOTE: Select the check box against each component since only the selected component’s configurations are applied on
the target system, when the Operational Template is applied.
NOTE: Irrespective of the selection made in the checkbox against each component, all the configurations are captured
in the template.
5. For the OS component, perform either of the following tasks depending on your requirement:
● For Windows OS deployment on SCCM, see Windows component for the OMIMSSC console extension for SCCM.
● For Windows OS deployment on SCVMM, see Windows component for the OMIMSSC console extension for SCVMM.
● For non-Windows OS deployment, see Non-Windows component for the OMIMSSC console extensions.
6. To save the profile, click Finish.
Windows component for OMIMSSC console extension for SCCM
While editing Operational Template, perform the following steps mentioned in Windows OS component for OMIMSSC console
extension for SCCM.
Windows component for OMIMSSC console extension for SCVMM
While editing Operational Template, perform the following steps mentioned in Windows OS component for OMIMSSC console
extension for SCVMM.
Non-Windows component for OMIMSSC console extensions
While editing Operational Template, perform the following steps mentioned in Non-Windows OS component for OMIMSSC
console extensions.
Deleting Operational Template
To delete an Operational Template, perform the following steps:
Before deleting an Operational Template, ensure that:
● The selected Operational Template is not associated with any server. If it is associated with a server, then, unassign the
template and then delete the template.
34
Operational Template