Administrator Guide

Recreating user data in OMIMSSC
This section provides information on how to migrate or re-create the user data captured in Saving all user data from DLCI for
SCVMM. Below is the information on steps required to migrate the user data:
1. Credential Profiles—recreate credential profile by using information saved from DLCI for SCVMM.
For information about creating credential profiles, see OpenManage Integration for Microsoft System Center User's Guide.
2. License—import the license file that is in .XML format saved from DLCI for SCVMM.
For information about importing the license file, see OpenManage Integration for Microsoft System Center User's Guide.
3. Synchronize with MSSC—synchronize OMIMSSC with SCVMM and get the list of hosts that are already managed by
SCVMM.
4. Discover servers—rediscover the unassigned servers using information saved from DLCI for SCVMM.
You can discover the Dell EMC servers using their iDRAC IP address by using one of the following methods:
● Auto discovery
● Manual discovery
For more information about auto and manual discovery, see OpenManage Integration for Microsoft System Center User's
Guide.
5. Update Groups—Recreate update groups after discovering servers or synchronizing OMIMSSC with SCVMM. Update
groups are a group of servers that require similar update management. There are two types of update groups available:
● Predefined update groups―you can only view, and maintain these server groups.
● Custom update groups―you can create, and maintain the server groups.
Predefined update groups—are automatically created after discovering servers. They are the default update groups,
Hence, no information is required for migration.
Custom update groups—recreate custom update groups by using information captured from DLCI for SCVMM.
To create custom update groups, see OpenManage Integration for Microsoft System Center User's Guide.
6. Hypervisor Profiles—recreate hypervisor profiles by using information captured from DLCI for SCVMM.
To create hypervisor profiles, see OpenManage Integration for Microsoft System Center User's Guide.
7. Hardware Profile—in OMIMSSC, hardware profile is part of Operational Template. The Operational Template contains the
following components:
● Hardware profile
● Deployment template
● Hypervisor profile
● Update source
You can create an Operational Template by capturing the configuration of the reference server. After capturing the
configuration, you can directly save the template, or edit the attributes for update source, hardware configuration, and
windows component as per the requirement and then save the template. This template can be deployed on other PowerEdge
servers that have similar configurations.
Operational Template—to recreate the hardware configuration use the same reference server as the one used in DLCI for
SCVMM, or create a configuration from a new reference server used in OMIMSSC.
For information about creating Operational Template, see OpenManage Integration for Microsoft System Center User's
Guide.
8. Update Source—there are two types of update source.
● Predefined and default update sources
● Custom update sources
Predefined and default update sources—are retained in OMIMSSC. The following are predefined and default update
sources:
● DELL ONLINE CATALOG—predefined update source of type FTP
● DELL ONLINE HTTP CATALOG—default update source available in OMIMSSC after a fresh installation or upgrade
5
Recreating user data in OMIMSSC 9