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
Redeploying Windows OS using OMIMSSC
To redeploy Windows OS on a server by using OMIMSSC console extension for SCCM or OMIMSSC console extension on
SCVMM, perform the following steps:
1. Delete the server from the Microsoft console. For more information, see Microsoft documentation.
2. Rediscover the server or synchronize OMIMSSC with the registered Microsoft console. The server is added as an
unassigned server in OMIMSSC. For more information about discovery, see Discovering servers using manual discovery. For
more information about synchronization, see Synchronizing with enrolled Microsoft console.
3. Create an Operational Template, by capturing all the details of the discovered server. For more information, see Creating
Operational Template from reference servers.
4. Assign an Operational Template on managed device, and check for the template compliance. For more information, see
Assigning Operational Template and running Operational Template compliance.
5. Deploy an Operational Template to make the device template compliant. For more information, see Deploying Operational
Template.
6. View the job status for operating system deployment in the Jobs and Logs Center page. For more information, see
Launching Jobs and Logs Center.
Deploying non-windows OS using OMIMSSC console extensions
To deploy non-windows OS using OMIMSSC, perform the following steps:
NOTE: Steps to deploy non-windows OS through OMIMSSC is common in both the Microsoft consoles.
1. Discover the reference server by using the Discovery page. For more information, see the Discovering servers using manual
discovery.
2. Create an Operational Template, by capturing all the details of the discovered server. For more information, see Creating
Operational Template from reference servers.
3. Assign an Operational Template on managed device, and check for the template compliance. For more information, see
Assigning Operational Template and running Operational Template compliance.
4. Deploy an Operational Template to make the device template compliant. For more information, see Deploying Operational
Template.
NOTE:
If the DHCP lookup fails while deployment, then the server times out and the server is not moved into Managed
Lifecycle Controller Lifecycle Controller (ESXi) collection in SCCM.
Creating Storage Spaces Direct clusters by using
predefined Operational Templates
To create clusters by using OMIMSSC, perform the following steps:
1. Discover the reference server by using the Discovery page. For more information, see the Discovering servers using manual
discovery.
2. Edit the predefined Operational Template. For more information, see Modifying Operational Template.
3. Create a logical switch. For more information, see Creating logical switch.
4. Create Storage Spaces Direct cluster. For more information, see Creating Storage Spaces Direct clusters.
Workflow for maintaining devices
Maintain the discovered devices in OMIMSSC.
Updating the firmware of servers and MX7000 devices
Here is a pictorial representation of the firmware update workflow.
82
Provisioning devices from OMIMSSC