Users Guide
Table Of Contents
- OpenManage Integration for Microsoft System Center Version 7.3 for Microsoft Endpoint Configuration Manager and System Center Virtual Machine Manager Unified User’s Guide
- Contents
- Introduction to OMIMSSC
- OMIMSSC license
- OMIMSSC components
- Support Matrix for OMIMSSC
- Deploy OMIMSSC
- Enroll Microsoft console in OMIMSSC
- Manage OMIMSSC and its components
- Backup and Restore OMIMSSC Appliance
- Uninstall OMIMSSC
- Upgrade OMIMSSC
- Manage Credential and Hypervisor profiles
- Discover devices and sync servers with OMIMSSC console
- Remove devices from OMIMSSC
- Views in OMIMSSC
- Manage Operational Templates
- Predefined Operational Templates
- About reference server configuration
- About reference Modular System configuration
- Create Operational Template from reference servers
- Create Operational Template from reference Modular Systems
- Create clusters using Operational Template
- View Operational Template
- Edit Operational Template
- Configure system specific values (Pool values) using Operational Template on multiple servers
- Assign Operational Template and Run Operational Template Compliance for servers
- Deploy Operational Templates
- Unassign Operational Template
- Delete Operational Template
- Deploy operating system using OMIMSSC
- Provision devices using OMIMSSC
- Update firmware using OMIMSSC
- Manage devices using OMIMSSC
- Deploy Azure Stack HCI cluster
- Troubleshooting
- Resources required for managing OMIMSSC
- Verifying permissions for using OMIMSSC console extension for MECM
- Verifying PowerShell permissions for using OMIMSSC console extension for SCVMM
- Install and upgrade scenarios in OMIMSSC
- Enrollment failure
- Failure of test connection
- Failure to launch OMIMSSC after installing MECM console extension
- 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
- Failure to auto discover iDRAC 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 MECM
- Empty cluster update group not deleted during autodiscovery or synchronization
- Failure to create cluster while applying cluster features
- Unable to retrieve the Cluster Aware Update job status
- Failure to perform maintenance-related tasks on rediscovered servers
- Generic scenarios in OMIMSSC
- Firmware update scenarios in OMIMSSC
- Failure of test connection for local update source
- Failure to create DRM update source
- Failure to create repository during firmware update
- 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 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 I: Time zone attribute values
- Appendix II: Populate Pool values
- Accessing support content from the Dell EMC support site
● OMIMSSC console extension for SCVMM supports modular and monolithic server models on 12
th
and later generations of
servers.
● For source configuration and destination configuration, use same type of disks—only Solid-state Drive (SSD), SAS, or only
Serial ATA (SATA) drives.
● For successful hardware profile RAID cloning, for destination system disks, use same or greater size and number of disks as
present in the source.
● RAID sliced virtual disks are not supported.
● iDRAC with shared LOM is not supported.
● RAID configured on external controller is not supported.
● Enable Collect System Inventory on Restart (CSIOR) in managed systems. For more information, see iDRAC documentation.
Discover servers using auto discovery
To automatically discover servers, connect servers to the network and power on the servers. OMIMSSC auto discovers the
unassigned servers by using the remote enablement feature of iDRAC. OMIMSSC works as a provisioning server and uses
iDRAC reference to auto discover servers.
1. In OMIMSSC, create a device type credential profile by providing the iDRAC credentials and make it as default for servers.
For information about creating a credential profile, see Creating a credential profile.
2. Disable the existing Administrator account in iDRAC settings in the managed device.
NOTE: It is recommended that you have a guest user account with operator privileges to log in to iDRAC in case auto
discovery fails and set a strong password.
3. Enable the auto discovery feature in managed device’s iDRAC settings. For more information, see iDRAC documentation.
4. In managed device's, iDRAC Settings, provide OMIMSSC Appliance IP in provision server IP, and then restart the server.
Discover servers using manual discovery
To manually discover PowerEdge servers by using an IP address or an IP range. To discover servers, provide the iDRAC IP
address and the device type credentials of a server. When you are discovering servers by using an IP range, specify an IP (IPv4)
range within a subnet by including the start and end range and the device type credentials of a server.
Ensure that a default credential profile is available.
1. In OMIMSSC console, perform any one of the following steps:
● In the dashboard, click Discover Servers.
● In the navigation pane, click Configuration and Deployment, click Server View, and then click Discover.
2. Click Discover.
3. In the Discover page, select the required option:
● Discover Using an IP Address—to discover a server using an IP address.
● Discover Using an IP Range—to discover all servers within an IP range.
4. Select the device type credential profile, or click Create New to create a device type credential profile.
The selected profile is applied to all the servers.
5. In iDRAC IP address, provide the IP address of the server that you want to discover.
6. In Discover Using an IP Address or IP Address Range, do any of the following:
● In IP Address Start Range, and IP Address End Range, provide the IP address range that you want to include, which
is the starting and ending range.
● Select Enable Exclude Range if you want to exclude an IP address range and in IP Address Start Range and IP
Address End Range, provide the range that you want to exclude.
7. Provide a unique job name, description for the job, and click Finish.
To track this job, the Go to the Job List option is selected by default.
The Jobs and Logs Center page is displayed. Expand the discovery job to view the progress of the job in Running tab.
After discovering a server, the server is added to Hosts tab, or Unassigned tab in the Server View page of Configuration
and Deployment section.
● When you discover a server with an operating system that is deployed on it, and the server is already present in MECM or
SCVMM console, and then the server is listed as a host server under the Hosts tab.
42
Discover devices and sync servers with OMIMSSC console