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
OMIMSSC supports four types of credential profiles and there is one predefined credential profile. You can create the
following four types of credential profile:
● Device Credential Profile—use this profile to log in to iDRAC or Chassis Management Controller (CMC).
NOTE: When creating Device Credential Profile, select iDRAC, to make it as default profile for iDRAC, or CMC to
make it default profile for Chassis Management Controller (CMC). Select None if you choose not to set this profile
as a default profile.
○ When a device type credential profile is created, an associated RunAsAccount is created in SCVMM to manage the
server, and the name of the account is Dell_CredentialProfileName.
￭ Recommended to not edit or delete the RunAsAccount.
○ If you delete the device type credential profile, the associated RunAsAccount from SCVMM is also deleted. Hence,
the corresponding credential profile is not visible in OMIMSSC.
● Windows Credential Profile—use this profile for accessing shared folders in Windows.
● FTP Credential Profile—use this profile for accessing the FTP site.
NOTE: The default FTP credential profile that is available in Appliance is, System Default FTP.
● SYSTEM DEFAULT FTP—predefined credential profile of type FTP credentials, and the password field is not mandatory
for this type.
● Proxy Server Credentials—use this profile for providing proxy credentials for FTP sites for firmware updates.
3. In Domain, provide the domain details for the Windows credentials, in Proxy Server URL, provide the proxy server URL
http://hostname:port or http://IPaddress:port format, in Default Profile for, select to make this profile as
the default profile to log in to iDRAC or CMC. Select None, if you choose not to set the profile as a default profile.
NOTE: Default Profile for option is applicable only for the Device type credential profile.
4. To create the profile, click Finish.
Modifying credential profile
Consider the following when you are modifying a credential profile:
● After creating, you cannot modify the type of a credential profile. However, you can modify other fields. To view the
modifications, refresh the screen.
● You cannot modify a device type credential profile if it is being used.
● You cannot modify a credential profile, if it is in use.
1. Select the credential profile you want to modify, click Edit, and update the profile.
2. To save the changes made, click Save.
Deleting credential profile
Consider the following when you are deleting a credential profile:
● When a device type credential profile is deleted, the associated RunAsAccount from SCVMM is also deleted.
●
When RunAsAccount in SCVMM is deleted, the corresponding credential profile is not available in Appliance.
● To delete a credential profile that is used in server discovery, delete the discovered server information and then delete the
credential profile.
● To delete a device type credential profile that is used for deployment, first delete the servers deployed in the SCVMM
environment and then delete the credential profile.
● You cannot delete a credential profile if it is used in an update source.
Select the credential profile that you want to delete, and then click Delete.
About hypervisor profile
A hypervisor profile contains a customized WinPE ISO (WinPE ISO is used for hypervisor deployment), host group, and host
profile taken from SCVMM, and LC drivers for injection.
NOTE: Hypervisor profiles are applicable only for OMIMSSC console extension for SCVMM.
16 Profiles