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
NOTE: The Default Credential Profile is not specific to the console. If the Credential Profile is selected as default in
the current console, the other consoles will be non-default for the selected type.
● If you are creating a Windows Credential Profile, provide the domain details in Domain.
NOTE: While creating the credential profile for console enrollment, if the NETBIOS name is configured in Active
Directory (AD), provide the NETBIOS name as a Domain. If NETBIOS name is not configured in the AD, provide the
domain name with Top Level Domain (TLD) details.
For example, if the domain name is mydomain, and the TLD is com, provide the domain name in credential profile as:
mydomain.com
● If you are creating a Proxy Server Credentials, provide the proxy server URL http://hostname:port or http://
IPaddress:port format in Proxy Server URL.
6. To create the profile, click Finish.
NOTE: When you create a device type credential profile in SCVMM, it creates a corresponding RunAsAccount with name
that is prefixed with, Dell_. Ensure that the enrolled user has access to the corresponding RunAsAccount for operations
such as Operating System deployment, which consumes the created device credential profile.
Modify credential profile
Consider the following before modifying a credential profile:
● After creating, you cannot modify the type of a credential profile. However, you can modify other fields.
● You cannot modify a credential profile, if it is in use.
NOTE: The steps to modify any type of credential profile are the same.
1. Select the credential profile that you want to modify, click Edit, and update the profile.
2. To save the changes made, click Save.
To view the changes made, refresh the Credential Profile page.
Delete credential profile
Consider the following when you are deleting a credential profile:
● When a device type credential profile is deleted, the associated RunAsAccount from SCVMM is also deleted.
● When RunAsAccount in SCVMM is deleted, the corresponding credential profile is not available in OMIMSSC.
● To delete a credential profile that is used in discovering servers, delete the discovered server and then delete the credential
profile.
● To delete a device type credential profile that is used for deployment, first delete the servers that are deployed in the
SCVMM environment and then delete the credential profile.
● You cannot delete a credential profile if it is used in an update source.
NOTE: The steps to delete any type of credential profile are the same.
Select the credential profile that you want to delete, and then click Delete.
To view the changes made, refresh the Credential Profile page.
Hypervisor profile in SCVMM
A hypervisor profile contains a customized WinPE ISO (WinPE ISO is used for hypervisor deployment), host group, and host
profile taken from SCVMM, and LC drivers for injection. Only OMIMSSC console extension for SCVMM users, can create and
manage hypervisor profiles.
38
Manage Credential and Hypervisor profiles