Administrator Guide

Saving all user data from DLCI for SCVMM
Before migrating to OMIMSSC, ensure that you save all user data details from DLCI for SCVMM. The user data and its information to be
captured from DLCI for SCVMM for successful migration are listed in the following table.
Table 1. Information required to be captured
Data Actions
Credential proles Note the credential prole name and credential details of the
prole such as user name, password, and default for: prole will be
used to log in to iDRAC or Chassis Management Controller
(CMC).
License Download the purchased .XML le (license key) of DLCI for
SCVMM from the Dell Digital Store and save a local copy of the
le.
Servers and predened update groups
• Note down the credential prole information used to access
the server’s iDRAC.
• For hosts—no details are required to be saved if the following
conditions are met:
• The servers are already managed in SCVMM.
• Baseboard Management Controller (BMC) of the
managed servers are congured.
NOTE:
Managed servers are the servers managed using
OMIMSSC.
• For unassigned servers—note down the iDRAC IP or IP
address ranges of servers that are listed in Unassigned tab of
Device Inventory page.
Custom update groups Note the group name and service tags of those servers that are
added to the group.
Hypervisor prole Note all required information from the Hypervisor proles with
details such as hypervisor prole name, customized WinPE ISO
(WinPE ISO is used for hypervisor deployment), host group and
host prole taken from SCVMM, and LC drivers for injection.
NOTE: WinPE ISO image is saved in the IG share.
Hardware Prole Note the reference server iDRAC IP used to create the hardware
proles.
Update Source
• Note the update source location and credentials to access the
source.
• Note the proxy credential prole for FTP Update Source if
proxy is congured.
Polling and Notications Note the polling and notications policy settings.
2
Saving all user data from DLCI for SCVMM 5