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
Table 4. Virtual appliance (continued)
Port
Number
Protocol
s
Port
Type
Maximum
Encryptio
n Level
Directi
on
Destination Usage Description
443 HTTPS TCP 128-bit In ESXi server
to OMIMSSC
appliance
HTTPS server Used in operating system
deployment flow for post
installation scripts to
communicate with the
OMIMSSC appliance.
443 HTTPS TCP 128-bit In iDRAC to
OMIMSSC
appliance
Auto
Discovery
Provisioning server that is used
for auto discovering managed
nodes.
443 WSMAN TCP 128-bit In/Out OMIMSSC
appliance to or
from iDRAC
iDRAC
communicatio
n
iDRAC, or CMC, or OME-
Modular communication, used
to manage and monitor the
managed nodes.
111 HTTPS TCP None In iDRAC to
OMIMSSC
appliance
Remote
procedure call
Used to determine the address
of the RPC function.
4433 HTTPS TCP None In iDRAC to
OMIMSSC
appliance
Auto
discovery
Used for auto discovery.
445/139 SMB TCP 128-bit Out OMIMSSC
appliance to CIFS
CIFS
communicatio
n
To communicate with Windows
share.
2049 NFS UDP/
TCP
None In/Out OMIMSSC
appliance to NFS
Public Share NFS public share that
is exposed by OMIMSSC
appliance to the managed
nodes and used in firmware
update and operating system
deployment flows.
4001 to
4004
NFS UDP/
TCP
None In/Out OMIMSSC
appliance to NFS
Public Share These ports must be kept open
to run the statd, quotd, lockd,
and mountd services by the V2
and V3 protocols of the NFS
server.
User-
defined
Any UDP/
TCP
None Out OMIMSSC
appliance to proxy
server
Proxy To communicate with the proxy
server.
Table 5. Managed nodes (ESXi)
Port
Number
Protocols Port
Type
Maximu
m
Encrypti
on Level
Directio
n
Destination Usage Description
443 WSMAN TCP 128-bit In OMIMSSC
appliance to
ESXi
iDRAC
communic
ation
Used to provide information to the
management station. This port has to
open from ESXi.
443 HTTPS TCP 128-bit In OMIMSSC
appliance to
ESXi
HTTPS
server
Used to provide information to the
management station. This port has to
open from ESXi.
For more information about the iDRAC and CMC port information, see the Integrated Dell Remote Access Controller User's
Guide and Dell Chassis Management Controller User's Guide available at https://www.dell.com/support.
For more information about the OME-Modular port information, see the Dell EMC OME-Modular User's Guide available at
https://www.dell.com/support.
Support Matrix for OMIMSSC
19