Administrator Guide

Recreating user data in OMIMSSC
About this task
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:
Steps
1 Credential Proles—recreate credential prole by using information saved from DLCI for SCVMM.
For information about creating credential proles, see OpenManage Integration for Microsoft System Center User's Guide.
2 License—import the license le that is in .XML format saved from DLCI for SCVMM.
For information about importing the license le, 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:
• Predened update groups―you can only view, and maintain these server groups.
• Custom update groups―you can create, and maintain the server groups.
Predened 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 Proles—recreate hypervisor proles by using information captured from DLCI for SCVMM.
To create hypervisor proles, see OpenManage Integration for Microsoft System Center User's Guide.
7 Hardware Prole—in OMIMSSC, hardware prole is part of Operational Template. The Operational Template contains the following
components:
• Hardware prole
• Deployment template
• Hypervisor prole
• Update source
You can create an Operational Template by capturing the conguration of the reference server. After capturing the conguration, you
can directly save the template, or edit the attributes for update source, hardware conguration, and windows component as per the
requirement and then save the template. This template can be deployed on other PowerEdge servers that have similar congurations.
Operational Template—to recreate the hardware conguration use the same reference server as the one used in DLCI for SCVMM,
or create a conguration 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.
• Predened and default update sources
5
Recreating user data in OMIMSSC 9