Users Guide
Table Of Contents
- OpenManage Integration for Microsoft System Center Version 7.2.1 for System Center Configuration Manager and System Center Virtual Machine Manager Unified User’s Guide
- Introduction to OMIMSSC
- OMIMSSC components
- System requirements for OMIMSSC
- Deploy OMIMSSC
- OMIMSSC licensing
- Enrolling Microsoft console in OMIMSSC
- Managing OMIMSSC and its components
- Backup and Restore OMIMSSC Appliance
- Uninstalling OMIMSSC
- Upgrading OMIMSSC for SCVMM
- Rebooting OMIMSSC Appliance
- Logging out of OMIMSSC Appliance
- Managing profiles
- Discovering devices and synchronizing servers with MSSC console
- Views in OMIMSSC
- Managing Operational Templates
- Predefined Operational Templates
- About reference server configuration
- Creating Operational Template from reference servers
- Creating Operational Template from reference Modular Systems
- Viewing Operational Template
- Modifying Operational Template
- Configuring system specific values (Pool values) using Operational Template on multiple servers
- Deleting Operational Template
- Assigning Operational Template and running Operational Template compliance for servers
- Deploying Operational Template on servers
- Assigning Operational Template for Modular Systems
- Deploying Operational Template for Modular System
- Unassigning Operational Template
- About reference Modular System configuration
- Preparing for operating system deployment
- Creating clusters using Operational Template
- Firmware update in OMIMSSC
- Managing devices in OMIMSSC
- Provisioning devices from OMIMSSC
- Configuration and deployment
- Use cases
- Creating Operational Templates
- Installer folders
- Assign Operational Templates
- Deploy Operational Templates
- Windows OS component for the OMIMSSC console extension for SCCM
- Windows component for the OMIMSSC console extension for SCVMM
- Non-Windows component for the OMIMSSC console extension for SCCM/SCVMM
- Discovery in enrolled MSSC
- Importing server profile
- Export server profile
- Viewing LC logs
- Collect LC logs
- Part replacement
- Polling and notification
- Launch iDRAC
- Launch Input Output Module
- Resolving synchronization errors
- Synchronizing OMIMSSC with enrolled Microsoft console
- Deploy Azure Stack HCI cluster
- Trouble shooting scenarios
- Resources required for managing OMIMSSC
- Verifying permissions for using OMIMSSC console extension for SCCM
- Verifying PowerShell permissions for using OMIMSSC console extension for SCVMM
- Install and upgrade scenarios in OMIMSSC
- Enrollment failure
- Failure of test connection
- Failure to connect to OMIMSSC console extension for SCVMM
- Error accessing console extension after updating SCVMM R2
- IP address not assigned to OMIMSSC Appliance
- SCVMM crashes while importing OMIMSSC console extension
- Failed to login to OMIMSSC console extensions
- SC2012 VMM SP1 crashing during update
- OMIMSSC admin portal scenarios
- Discovery, synchronization and inventory scenarios in OMIMSSC
- Failure to discover servers
- Discovered servers not added to All Dell Lifecycle Controller Servers collection
- Failure to discover servers due to incorrect credentials
- Creation of incorrect VRTX chassis group after server discovery
- Unable to synchronize host servers with enrolled SCCM
- Empty cluster update group not deleted during autodiscovery or synchronization
- Failure to perform maintenance-related tasks on rediscovered servers
- Generic scenarios in OMIMSSC
- Firmware update scenarios in OMIMSSC
- Failure of creation of update source
- Failure to connect to FTP using system default update source
- Failure of test connection for local update source
- Failure to create DRM update source
- Failure to create repository during firmware update
- Failure to display comparison report after upgrading or migrating OMIMSSC
- Failure to update firmware of clusters
- Failure of firmware update because of job queue being full
- Failure of firmware update when using DRM update source
- Firmware update on components irrespective of selection
- Failure to display latest inventory information after firmware update
- Failure to delete a custom update group
- Failure to update WinPE image
- Changing of polling and notification bell color after updating the frequency
- Operating system deployment scenarios in OMIMSSC
- Server profile scenarios in OMIMSSC
- LC Logs scenarios in OMIMSSC
- Appendix
- Appendix 2
- Accessing documents from the Dell EMC support site
Managing profiles
Profiles contain all the data that is required for performing any operations in OMIMSSC.
Topics:
• About credential profile
• About hypervisor profile (for SCVMM users)
About credential profile
Credential profiles simplify the use and management of user credentials by authenticating the role-based capabilities of the user.
Each credential profile contains a user name and password for a single user account.
OMIMSSC uses credential profiles to connect to the managed systems’ iDRAC. Also, you can use credential profiles to access
the FTP site, resources available in Windows shares, and to work with different features of iDRAC.
You can create four types of credential profiles:
● Device Credential Profile—used to log in to iDRAC or CMC. Also, you can use this profile to discover a server, resolve
synchronization issues, and deploy operating system. This profile is specific to a console. You can use and manage this profile
only in a console where it is created.
● Windows Credential Profile—used for accessing share folders in Windows operating system
● FTP Credential Profile—used for accessing an FTP site
● Proxy Server Credentials—used for providing proxy credentials for accessing any FTP sites for updates.
NOTE:
All profiles other than device profile are shared resources. You can use and manage these profiles from any of
the enrolled consoles.
Predefined credential profile
SYSTEM DEFAULT FTP account is a predefined credential profile available in OMIMSSC. The predefined credential profile is of
type FTP, having User Name, and Password as anonymous. Use this profile to access ftp.dell.com
Creating credential profile
When creating a credential profile, consider the following points:
● During auto discovery, if a default credential profile is not available for iDRAC, and then the default iDRAC credentials is
used. The default iDRAC user name is root, and password is calvin.
● To get information about the modular systems, the modular server is accessed with default CMC profile. The default CMC
profile user name is root and password is calvin.
● (Only for SCVMM users) When a device type credential profile is created, an associated RunAsAccount is created in
SCVMM to manage the device, and the name of the RunAsAccount is Dell_CredentialProfileName.
● Ensure that you do not edit, or delete the RunAsAccount in SCVMM.
1. In OMIMSSC, perform any of the following steps to create a Credential Profile:
● In OMIMSSC dashboard, click Create Credential Profile.
● In the navigation pane, click Profiles > Credential Profile, and then click Create.
2. In Credential Type, select the credential profile type that you want to use.
3. Provide a profile name and description.
NOTE: Default Profile for option is applicable only for a Device type credential profile.
4. In Credentials, provide the user name and password.
13
Managing profiles 35