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
Verifying PowerShell permissions for using OMIMSSC
console extension for SCVMM
Check if the PSRemoting status is enabled and ExecutionPolicy is set to RemoteSigned. If the status is different then
perform the following steps in PowerShell:
a. In PowerShell, run the command: PSRemoting.
If the PSRemoting command is disabled, run enable the PSRemoting command using the following commands.
i. Run the command: Enable-PSRemoting
ii. In the confirmation message, type Y.
b. In PowerShell, run the command: Get-ExecutionPolicy.
If the policy is not set to RemoteSigned, then set it to RemoteSignedusing the following commands.
i. Run the command: Set-ExecutionPolicy RemoteSigned.
ii. In the confirmation message, type Y.
Install and upgrade scenarios in OMIMSSC
This section has all the troubleshooting information related to installing and upgrading OMIMSSC.
Verifying OMIMSSC Appliance VM configuration
To verify that the OMIMSSC Appliance VM is configured appropriately, select and then right-click the OMIMSSC Appliance VM,
click Settings, and then perform the following tasks:
1. Check if the allocation of memory for the OMIMSSC Appliance is as per the requirement mentioned in the Common
requirements section of Dell EMC OpenManage Integration for Microsoft System Center Version 7.2.1 for System Center
Configuration Manager and System Center Virtual Machine Manager User Guide. Else provide the memory in Startup RAM,
and click Apply.
2. Check if the processor count is as per the requirement mentioned in the Common requirements section of Dell EMC
OpenManage Integration for Microsoft System Center Version 7.2.1 for System Center Configuration Manager and System
Center Virtual Machine Manager User Guide. Else provide the number of processor counts in Number of Virtual
processors count under Processors.
3. Check if the Virtual hard disk field under IDE Controller: IDE Controller 0 > Hard Drive the Virtual hard disk referring to
the OMIMSSC—v7 file else, click Browse and navigate to the location where the VHD file is unzipped and select the
OMIMSSC—v7 file and click Apply.
4. Check if Network Adapter > Virtual Switch is connected to a physical NIC card, else configure the NIC card, and select
the appropriate NIC card from the Virtual Switch drop-down menu and click Apply.
If the newly created virtual machine with the selected virtual hard disk of OMIMSSC Appliance fails to boot with any kernel
panic exception, edit the virtual machine settings, and enable the dynamic memory option for this virtual machine.To enable the
dynamic memory option for a virtual machine, perform the following tasks:
1. Right-click the OMIMSSC Appliance VM, click Settings, and then click Memory.
2. Under Dynamic Memory, select the Enable Dynamic Memory check box, and provide the details.
Enrollment failure
If the test connection or enrollment fails, then you get an error message.
As a workaround, perform the following steps:
● Ping from OMIMSSC Appliance to enrolled SCCM or SCVMM server FQDN by logging in to OMIMSSC Appliance VM as a
read-only user. If there is a response, then wait for some time and then continue with the enrollment.
To launch the OMIMSSC Appliance VM as a read-only user, enter user name as readonly with the same password used to
log into the OMIMSSC Appliance VM.
● Ensure that the SCCM or SCVMM server is running.
Trouble shooting scenarios
95