OpenManage Integration for Microsoft System Center Version 7.3 for Microsoft Endpoint Configuration Manager and System Center Virtual Machine Manager Unified User’s Guide September 2021 Rev.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2009 - 2021 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents Chapter 1: Introduction to OMIMSSC............................................................................................ 9 What’s new?.........................................................................................................................................................................9 Chapter 2: OMIMSSC license....................................................................................................... 11 Supported options for license feature......................
Modify MECM and SCVMM accounts in OMIMSSC admin portal....................................................................... 30 Repair or modify installers......................................................................................................................................... 30 Chapter 8: Backup and Restore OMIMSSC Appliance.................................................................. 32 Backup OMIMSSC Appliance .........................................................................
OpenManage Enterprise Modular console............................................................................................................ 49 Input/Output Modules............................................................................................................................................... 49 Cluster View.......................................................................................................................................................................
Configure replaced components....................................................................................................................................74 Export and import server profiles..................................................................................................................................74 Chapter 18: Update firmware using OMIMSSC.............................................................................75 About update groups..........................................
IP address not assigned to OMIMSSC Appliance................................................................................................93 SCVMM crashes while importing OMIMSSC console extension..................................................................... 94 Failed to login to OMIMSSC console extensions................................................................................................. 94 SC2012 VMM SP1 crashing during update..........................................................
Chapter 23: Appendix II: Populate Pool values............................................................................107 Chapter 24: Accessing support content from the Dell EMC support site.....................................
1 Introduction to OMIMSSC This document is the unified user's guide which provides all the information related to usage, installation, and best practices of OMIMSSC. OpenManage Integration for Microsoft System Center (OMIMSSC) is delivered as an appliance with integration for the Microsoft System Center suite of products. OMIMSSC enables full lifecycle management of Dell EMC PowerEdge servers by using integrated Dell Remote Access Controller (iDRAC) with Lifecycle Controller (LC).
● Support for RHEL operating system deployment versions 7.9, 8.0, 8.3, and 8.4. ● Restructured user document. (Installation guide, User's guide, and Troubleshooting information consolidated in a single unified document). ● Support for deploying the Dell EMC OMIMSSC appliance for OpenManage Integration for Microsoft Endpoint Configuration Manager (MECM) and System Center Virtual Machine Manager (SCVMM) version 7.3 on the following VMware ESXi versions using .ova file: ○ Version 6.5 ○ Version 6.7 ○ Version 7.
2 OMIMSSC license OMIMSSC has two types of licenses: ● Evaluation license—this is a trial version of the license containing an evaluation license for five servers (hosts or unassigned) which is auto imported after the installation. This is applicable only for 11th and later generations of the Dell EMC servers. ● Production license—you can purchase production license from Dell EMC for any number of servers to be managed by OMIMSSC. This license includes product support and OMIMSSC Appliance updates.
Reimport licenses If you try to import the same license file, an error message is displayed. Purchase a new license, and import the new license file. Import multiple licenses You can import multiple license files with different entitlement ID to increase the number of servers that you can discover and maintain in OMIMSSC. Upgrade licenses You are allowed to work with OMIMSSC with the existing license file for all the supported server generations.
Managing Licenses—displays each license file imported along with the details such as entitlement ID, product description, date when the license file was imported, date from when the license file is valid, and list of all the server generations supported by the license.
3 OMIMSSC components The following is the list of the OMIMSSC components and their names that have been used in this guide: Table 1. Components in OMIMSSC Components Description OpenManage Integration for Microsoft System Center Appliance virtual machine, also known as OMIMSSC Appliance. Host the OMIMSSC Appliance on a Hyper-V as a virtual machine based on CentOS and performs the following tasks: ● Interacts with the Dell EMC servers through iDRAC by using Web Services Management (WSMan) commands.
OMIMSSC architecture OMIMSSC components 15
4 Support Matrix for OMIMSSC Topics: • • • • • Supported System Center versions Network Requirements Infrastructure administration using Microsoft System Center Console System requirements for OMIMSSC System requirements of OMIMSSC console extension for SCVMM Supported System Center versions All the available MECM and SCVMM versions for OMIMSSC are as follows: OMIMSSC Supported System Center ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● ● Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Microsoft Micr
Table 2. Supported Devices (continued) Dell EMC System Supported Version ● Lifecycle Controller Version and Integrated Dell EMC Remote Access Controller Version for supported AMD platforms: ○ R750, R750xa, and R650 - 4.40.20.00 and higher ○ R450, R550, R650xs, and R750xs - 4.40.20.00 and higher ○ XR11 and XR12 - 4.40.35.00 and higher ○ XE2420 - 4.40.10.00 ○ C6520 - 4.40.20.0 or higher ○ MX750c - 4.40.20.0 or higher ● Dell EMC OpenManage Server Driver Pack version 10.0.1 ● MECM ○ R6515 and R7515 - 3.40.40.
Table 3. Supported Operating Systems (Deployment): (continued) Operating Systems Supported Version Non windows Operating System ● RHEL 8.0, 8.3, 8.4 ● RHEL 7.2, 7.3, 7.4, 7.5 ● RHEL 6.9 VMWare ESXi ● ● ● ● ● ● ● ● ● ESXi 7.0 U2 - A00 ESXi 7.0 U1 - A05 ESXI 6.7 U3 - A10 ESXi 6.7 - A06 ESXi 6.5 U3 ESXi 6.5 U1 - A11 ESXi 6.5 - A03 ESXi 6.0 U3 - A15 ESXi 6.0 - A02 NOTE: Download the image from https://www.dell.
Table 4. Virtual appliance (continued) Port Protocol Number 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.
Infrastructure administration using Microsoft System Center Console Microsoft System Center user account privileges All the required account privileges to use OMIMSSC are as follows: User must be member of the following groups in System Center Consoles for Account privileges to use OMIMSSC console extension. Table 6. User accounts with required privileges Users Privileges/Roles For enrollment ● Account used to enroll the MECM console with OMIMSSC should be a full admin or an administrator in MECM.
○ ○ ○ ○ Internet Explorer 10 or later Mozilla Firefox 30 or later Google Chrome 23 or later Microsoft Edge System requirements of OMIMSSC console extension for SCVMM To install OMIMSSC console extension for SCVMM: ● ● ● ● Install the same versions of SCVMM admin console and SCVMM server. Failover clustering feature is enabled on SCVMM server. Enrolled user should have administrative rights on SCVMM server. Enrolled user should have administrative rights on the managed cluster.
5 Deploy OMIMSSC Topics: • • • • • Download OMIMSSC from web Set up OMIMSSC Appliance on Hyper-V Set up OMIMSSC Appliance on ESXi Enroll multiple Microsoft consoles Launch OMIMSSC admin portal to download OMIMSSC components Download OMIMSSC from web To download OMIMSSC, from https://www.dell.com/support perform the following steps: 1. Click Browse all products > Software > Enterprise Systems Management > OpenManage Integration for Microsoft System. 2. Select the required version of OMIMSSC. 3.
ii. In Settings, select Processor, and set Number of virtual processors to 4. 2. Perform the following tasks once OMIMSSC Appliance starts: NOTE: It is recommended that you wait for five minutes before you log in as an Admin so that all services are initiated. a. In localhost login: Type admin. b. In Enter new Admin password: Type a password. NOTE: Dell EMC recommends to configure and use strong passwords to authenticate appliance admin user and console extension. c.
c. Select VMware Tools > Time > Synchronize guest time with host. Enroll multiple Microsoft consoles Manage OMIMSSC Appliance resources when multiple Microsoft consoles are enrolled with OMIMSSC. Based on number of Microsoft consoles you plan to enroll with OMIMSSC Appliance, ensure that the hardware requirements are met. For more information, see Common system requirements for OMIMSSC. To configure resources for multiple Microsoft consoles, perform the following steps: 1.
3. On the License Agreement page, select I accept the terms in the license agreement, and then click Next. 4. In the Destination Folder page, by default an installation folder is selected. To change the location, click Change and traverse to a new location, and then click Next. 5. On the Ready to Install the Program page, click Install. The following folders are created after installing the console extension: ● Log—this folder consists of console-related log information.
6 Enroll Microsoft console in OMIMSSC Ensure that the following prerequisites and the required account privileges are met: ● For MECM users, OMIMSSC console extension for MECM console is installed. ● For SCVMM users, OMIMSSC console extension for SCVMM is installed. Ensure the following information is available: ● User credentials of the system on which Microsoft System Center is set up, see required account privileges. ● FQDN of MECM or FQDN of SCVMM.
3. Clear the Do not save encrypted pages to disk option, and click OK. Launch OMIMSSC console extension for MECM View the user privileges table mentioned in Account privileges. In MECM console, click Assets and Compliance, click Overview, and then click the OMIMSSC console extension for MECM. NOTE: If you are connecting to MECM console using Remote Desktop Protocol (RDP), and then the OMIMSSC session may be logged out if the RDP is closed. Hence, log in again after reopening the RDP session.
7 Manage OMIMSSC and its components Topics: • • • • • • • View OMIMSSC Appliance details View OMIMSSC user management Manage HTTPS certificate View or refresh enrolled consoles Change OMIMSSC Appliance password Reboot OMIMSSC Appliance Modify MECM and SCVMM accounts in OMIMSSC admin portal View OMIMSSC Appliance details 1. Launch the OMIMSSC admin portal from a browser. 2.
For more information about HTTPS certificate management in OMIMSSC,, see the OpenManage Integration for Microsoft System Center Version 7.3 for Microsoft Endpoint Configuration Manager and System Center Virtual Machine Manager 7.3 User`s Guide available at https://www.dell.com/support. Generate a Certificate Signing Request (CSR) Generating a new CSR prevents certificates that were created with the previously generated CSR from being uploaded to the appliance.
3. To view the latest list of enrolled consoles, click Refresh. Change OMIMSSC Appliance password To change the password of OMIMSSC Appliance VM console, perform the following steps: 1. Launch OMIMSSC Appliance VM console, and login using the old credentials. 2. Navigate to Change Admin Password, and press Enter. The screen to change password is displayed. 3. Provide your present password, and then provide a new password matching the listed criteria. Re-enter the new password and press Enter.
Repair OMIMSSC console extension for MECM To repair the OMIMSSC files in case they are corrupt, perform the following steps: 1. Run the OMIMSSC console extension for MECM installer. The Welcome screen is displayed. 2. Click Next. 3. In Program Maintenance, select Repair, and then click Next. The Ready to Repair the Program screen is displayed. 4. Click Install. A progress screen displays the progress of installation. After installation is complete, the InstallShield Wizard Completed window is displayed. 5.
8 Backup and Restore OMIMSSC Appliance Using Backup Appliance Data option from OMIMSSC Appliance, save OMIMSSC information such as enrolled Microsoft consoles, discovered devices, profiles, update sources, Operational Templates, licenses and completed jobs in OMIMSSC console extensions. Topics: • • Backup OMIMSSC Appliance Restore OMIMSSC Appliance Backup OMIMSSC Appliance This functionality enables OMIMSSC appliance database and important configurations to be backed up.
● Before upgrading to a new version of OMIMSSC ● Before migrating from one OMIMSSC Appliance to another OMIMSSC Appliance Pre-requisites: Ensure that you restore the data before performing any operations on the new OMIMSSC Appliance. Perform the following steps for restoring old OMIMSSC Appliance data on a fresh OMIMSSC Appliance: 1. From the OMIMSSC admin portal, click Settings, and then click Restore Appliance 2. There are two options available for restoring appliance data.
9 Uninstall OMIMSSC To uninstall OMIMSSC: 1. De-enroll the OMIMSSC console from the OMIMSSC admin portal. For more information, see De-enrolling OMIMSSC console. 2. Uninstall the OMIMSSC console extension for the registered Microsoft console. For information, see Uninstalling OMIMSSC console extension for MECM or Uninstalling OMIMSSC console extension for SCVMM. 3. Remove OMIMSSC Appliance VM. For more information, see Removing OMIMSSC Appliance VM. 4. Remove Appliance-specific accounts.
● Select Console Add-in for SCVMM, and then click Uninstall. 2. Remove the console extension in SCVMM. ● In the SCVMM console, click Settings. ● Right-click OMIMSSC and select Remove. Other uninstallation steps To remove the OMIMSSC console extension from SCVMM, delete the following accounts and profiles: ● Appliance-specific RunAsAccounts ● OMIMSSC Application Profile Delete Appliance-specific RunAsAccounts To delete the Appliance-specific RunAsAccounts from the SCVMM console. 1.
10 Upgrade OMIMSSC You can upgrade the OMIMSSC appliance to the latest version by backing up the OMIMSSC appliance data (including settings and configurations), and then restoring the backed-up file in the latest version of the OMIMSCC appliance. For more information about backup and restore of OMIMSSC appliance, see the Back up OMIMSSC Appliance section and Restore OMIMSSC Appliance section. The following table provides upgrade path for OMIMSCC Appliance version 7.3.
11 Manage Credential and Hypervisor profiles Profiles contain all the data that is required for performing any operations in OMIMSSC. Topics: • • Credential profile in MECM and SCVMM Hypervisor profile in SCVMM Credential profile in MECM and SCVMM Credential profiles simplify the use and management of user credentials by authenticating the role-based capabilities of the user. Each credential profile contains a user name and password for a single user account.
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.
Create hypervisor profile Create a hypervisor profile and use the profile to deploy hypervisors. ● Update the WinPE ISO image, and have access to the share folder where the image is saved. For information about updating the WinPE image, see WinPE update. Update the WinPE ISO image, and have access to the share folder where the image is saved.
To view the changes made, refresh the Hypervisor profile page. Delete hypervisor profile Select the hypervisor profile that you want to delete, and click Delete. To view the changes made, refresh the Hypervisor profile page.
12 Discover devices and sync servers with OMIMSSC console Discovery is the process of adding supported modular systems and PowerEdge bare-metal servers or host servers or nodes in to OMIMSSC. Sync with MSSC console is the process of adding host servers from registered Microsoft console (MECM or SCVMM) in to OMIMSSC. Hence, using any one of the processes, you can add devices in to OMIMSSC . Only after discovering the devices, you can manage them in OMIMSSC.
● 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.
● When you discover a PowerEdge server that is not listed in MECM or SCVMM, and then the server is listed as an unassigned server under the Unassigned tab in all the OMIMSSC console extensions, in case of multiple Microsoft consoles enrolled to single OMIMSSC Appliance. After discovering a server, the server is marked as hardware compatible when it contains supported versions of LC firmware, iDRAC, and BIOS to work with OMIMSSC.
Sync of OMIMSSC console extension with enrolled MECM You can synchronize all servers (hosts and unassigned) from enrolled MECM to OMIMSSC. Also, you get the latest firmware inventory information about the servers after sync. Before synchronizing OMIMSSC and the enrolled MECM console, ensure that the following requirements are met: ● Have details of default iDRAC credential profile for servers. ● Update the Dell Default Collection before synchronizing OMIMSSC with MECM.
5. Click Finish to submit the job. View System Lockdown Mode The System Lockdown Mode setting is available in iDRAC for 14 th generation of servers and later. The setting when turned on locks the system configuration including firmware updates. After the System Lockdown mode is enabled, users cannot change any configuration settings. This setting is intended to protect the system from unintentional changes.
13 Remove devices from OMIMSSC When any of the listed servers is no longer required to be managed, it can be removed from the list of managed servers. If the server is removed from the system center from management, the same can be removed from OMIMSSC appliance. To remove a server, perform the following steps: Consider the following points before removing a server: ● After you remove a server, the consumed license is relinquished.
14 Views in OMIMSSC View all the devices discovered in OMIMSSC in Configuration and Deployment page along with their hardware and firmware inventory information. Also, view all the jobs with status in Jobs and Logs Center page. Topics: • • • • • Server View Modular Systems view Cluster View Maintenance Center view Jobs and Logs Center Server View The Server View page lists all unassigned and host servers that are discovered in OMIMSSC under Unassigned Servers and Hosts tabs.
● The Operational Template column is displayed as Not Assigned, after the servers are discovered. To update firmware and deploy operating system on these servers, assign and deploy Operational Templates. For more information, see Assign Operational Template for servers and Deploy Operational Template for servers. ● The discovered servers are added to predefined groups in OMIMSSC. You can create custom update groups based on functional requirements. For more information, see About update groups.
● To view all the storage devices present in the Modular System, click Storage Devices tab. After discovering Modular Systems, consider the following points: ● The Operational Template column is displayed as Not Assigned, after the Modular Systems are discovered. To update firmware and deploy operating system on these Modular Systems, assign and deploy Operational Templates. For more information, see Managing Operational Templates.
2. To view information about specific type of clusters, expand the cluster type. All the clusters of this type are listed on the left pane. 3. To view servers present in a cluster, click a cluster name. Maintenance Center view The Maintenance Center page lists all the discovered devices in groups and the resources that are required for maintaining devices in OMIMSSC.
For example, if a firmware update job is in-progress for a group of servers, the tab displays log messages that belong to creating the Server Update Utility (SUU) repository for that job. The various states of a job that is defined in OMIMSSC are as follows: ● ● ● ● ● Canceled—job is manually canceled, or after OMIMSSC Appliance restarts. Successful—job is completed successfully. Failed—job is not successful. In Progress—job is running. Scheduled—job has been scheduled for a future date and time.
15 Manage Operational Templates Operational Templates contain complete device configuration and are used for deploying operating system and update firmware for PowerEdge servers and Modular Systems within Microsoft environment. Operational Template replicates hardware and firmware of a reference server (golden server) on to many other servers while provisioning for operating systems.
Predefined Operational Templates Predefined templates have all the configurations that are required to create Windows server HCI clusters or Windows Server Software-Defined (WSSD). OMIMSSC supports creating clusters on AX-6515, AX-740XD, AX-640, RN740XD, RN740XD2, and RN640, Windows server HCI Ready Node models along with their specific network adapters. Table 10.
Create Operational Template from reference servers Before creating Operational Template, ensure that you complete the following tasks: ● Discover a reference server by using the Discovery feature. For information about discovering servers, see Discovering servers using manual discovery. ● For MECM users: ○ Create a task sequence. For more information, see Creating task sequence. ○ Create a task sequence. For more information, see OpenManage Integration for Microsoft System Center Unified User's Guide.
● Operating system—select either Windows, or ESXi, or RHEL 6. Use the horizontal scroll bar to locate a component. Select the component, expand a group, and then edit its attribute values. Use the vertical scroll bar to edit a groups and attributes of a component. 7. Select the check box against each component, because, the configurations of selected components are applied on the managed device, when the Operational Template is applied.
Select Hypervisor Profile, Credential Profile, and Server IP from. NOTE: Host Name, and Server Management NIC are always pool values. For server management NIC, provide the MAC address of the network port through which you want the operating system to communicate to SCVMM.
3. Enter a name and description for the template. 4. In Device Components, click a component to view the available attributes and their values. The components are as follows: ● Firmware update ● Management Module Embedded NOTE: Ensure that the Web Server attribute is enabled. If this component is not enabled, and then the MX7000 Modular Systems cannot be accessed through OMIMSSC after deploying the Operational Template.
● Ensure that the managed servers configurations match the Windows server HCI solution firmware and driver versions requirements. For more information, see Dell EMC Windows server HCI Ready Nodes PowerEdge R740XD , R740XD2, and PowerEdge R640 Support Matrix documentation.
Consider the following before modifying an Operational Template: ● The values of few attributes depend on the values of other attributes. When you change attribute values manually, ensure that you also change the interdependent attributes. If these interdependent values are not changed appropriately, and then applying the hardware configurations may fail.
4. Expand the Attribute Group. If the value of the attribute is Pool Value, the attribute is identified to be system specific attribute. For information on attribute group and component for all system specific attributes see, table 13 in System specific attributes in Operational Template section. 5. If you do not want to apply these system specific attributes, identify these attributes (mentioned in step 4) and unselect them while editing Operational Template. 6.
The AssignOperational Template page is displayed. 2. Select the required Modular Systems, and click Assign Operational Template and Run Compliance. The AssignOperational Template page is displayed. 3. Select the template from Operational Template drop-down menu, enter a job name, and then click Assign. If the device is compliant to the template, and then a green color box with a check mark is displayed.
You can deploy Windows and non-Windows operating system—ESXi and RHEL by deploying the Operational Template assigned to servers. NOTE: Download and install appropriate drivers from Dell.com/support if a yellow bang is displayed under Device Manager after you deploy Windows 2016 or Windows 2019 operating system on 12 th generation of the servers. NOTE: Deploying Operational Template on servers would be blocked if lock-down mode is enabled in the servers.
To track this job, the Go to the Job List option is selected by default. Unassign Operational Template 1. In OMIMSSC, perform any one of the following tasks: ● Click Configuration and Deployment, and click Server View. ● Click Configuration and Deployment, and click Modular System View. Select the required devices and click Assign Operational Template and Run Compliance. The Assign Operational Template and Run Compliance page is displayed. 2.
16 Deploy operating system using OMIMSSC Before deploying Windows operating system on the managed servers, update the WinPE image, create a task sequence, LC boot media file, and task sequence media bootable ISO file. The steps vary for MECM and SCVMM console users. Refer the bellow section for more details. For deploying non-windows operating system remember the points mentioned in Preparing for non-Windows OS deployment section.
Extract drivers from OpenManage server driver pack Dell EMC OpenManage Server Driver Pack DVD is a publicly released package from Dell EMC which packages OS drivers for all the platforms. From the current version onwards OMIMSC should help administrators to create the WinPE image by using OpenManage driver pack only. To download OpenManage driver pack, launch https://www.dell.
Prepare for operating system deployment on MECM console Before deploying operating system on managed servers discovered using OMIMSSC in MECM console, create a Dell EMC specific or a custom task sequence, an LC boot media file, and task sequence media bootable ISO file. Task sequence-MECM Task sequence is a series of commands that is used to deploy operating system on the managed system using MECM. Before creating Operational Template, Dell EMC recommends that you complete the following prerequisites. 1.
11. Click Close in the confirmation message box that is displayed. Create a custom task sequence 1. Launch the Configuration Manager. The Configuration Manager console is displayed. 2. In the left pane, select Software Library > Overview > Operating Systems > Task Sequences. 3. Right-click Task Sequences, and then click Create Task Sequence. The Create Task Sequence Wizard is displayed. 4. Select Create a new custom task sequence, and click Next. 5.
NOTE: OMIMSSC does not support the Standalone Media method to create Task Sequence Media. 2. From the Task Sequence Media Wizard, select Bootable Media, select Allow unattended operating system deployment option, and click Next. 3. Select CD/DVD Set, and click Browse and select the location to save the ISO image. 4. Click Next. 5. Clear the Protect Media with a Password check box and click Next. 6. Browse and select PowerEdge server Deployment Boot Image. NOTE: Use the boot image created using DTK only. 7.
17 Provision devices using OMIMSSC This chapter covers high-level details for discovering, deploying operating system, creating clusters, and maintaining Dell EMC devices using OMIMSSC.
Provision devices using OMIMSSC
Deploy Windows OS using OMIMSSC console extension for MECM To deploy Windows OS through MECM console using OMIMSSC, perform the following steps: NOTE: Before deploying OS on a host server, ensure that in MECM, the Client status of the server is No. 1. Download the latest Dell EMC OpenManage server driver pack and create a Windows Preinstallation Environment (WinPE) boot WIM image. For more information, see the WinPE update. 2. Import this .WIN image into the MECM console, and create a boot image in MECM.
Redeploy Windows OS using OMIMSSC To redeploy Windows OS on a server by using OMIMSSC console extension for MECM 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.
Provision devices using OMIMSSC 73
You can update the selected devices by using online sources or local sources (DRM/HTTPS) 1. Create or select a default update source. For more information about update source, see Update source. NOTE: Ensure that you update the update source with the latest catalog by using the polling and notification feature. For more information about polling and notification, see Polling and notification.
18 Update firmware using OMIMSSC Maintain Dell EMC devices up-to-date by upgrading to the latest firmware to use security, issue fixes, and enhancements, using OMIMSSC. Update the firmware of devices using Dell EMC update repositories. Updating firmware is supported only on hardware compatible devices. For using the features available in OMIMSSC on the managed devices, the managed devices must have the minimum required firmware versions of iDRAC, Lifecycle Controller (LC), and BIOS.
View update groups To view update groups: 1. In OMIMSSC, click Maintenance Center and then click Maintenance Settings. 2. In Maintenance Settings, click Update Groups. All the custom groups created are displayed with name, group type, and number of servers in the group. Create custom update groups 1. In OMIMSSC console, click Maintenance Center, and then click Maintenance Settings. 2. In Maintenance Settings, click Update Groups, and then click Create. The Firmware Update Group page is displayed. 3.
You can create an update source or a repository, and set it as a default update source for generating a comparison report, and receiving alerts when new catalog files are available at the repository. Using OMIMSSC, you can keep the devices firmware up-to-date using online or offline update sources. Online update sources are repositories that are maintained by Dell EMC. Offline update sources are local repositories and used when there is no Internet connection.
Validating data using test connection To verify if the location of the update source is reachable by using the credentials that are mentioned while creating the update source, use Test Connection. Only after the connection is successful, you are enabled to create an update source. Setup local HTTPS To set up local HTTPS: 1. Create a folder structure in your local HTTPS that is an exact replica of downloads.dell.com. 2. Download the catalog.
Edit update source Consider the following points before, modifying an update source: ● To edit UPDATE CATALOG FOR MICROSOFT HCI SOLUTIONSupdate source, edit the respective predefined update source, and save the changes. This update reflects in UPDATE CATALOG FOR MICROSOFT HCI SOLUTIONS update source. ● You cannot change the type of an update source and the location after the update source is created.
5. After selecting the required option click Connect. The available system and model will be displayed in the Integration Type section. 6. Select Add to create the repository. The repository is displayed in the repository dashboard available in the home page. NOTE: While selecting bundle types or DUP formats, ensure to select Windows 64-bit and Operating System independent, if Dell PowerEdge MX7000 chassis is part of the inventory in OMIMSSC.
The Maintenance Center page is displayed with a comparison report for all the devices that are discovered in OMIMSSC against the selected update source. 2. (Optional) To view a comparison report only for specific group of devices, select only the required devices. 3. (Optional) To view a comparison report, for another update source, change the update source by selecting an update source from Select Update Source drop-down list. 4.
NOTE: Select UPDATE CATALOG FOR MICROSOFT HCI SOLUTIONS update source or DELL EMC MX SOLUTION CATALOG update sources, for applying firmware updates on Windows server HCI clusters or MX7000 Modular Systems since, these update sources see a modified reference to catalog that contains recommended firmware versions of components for Windows server HCI clusters and Modular Systems. ● iDRAC or Management Module (MM) job queue is cleared before applying the updates, on the managed devices.
● Availability of failover clusters. ● Check for cluster update readiness and ensure that there are no major errors and warnings in the Cluster Readiness report for applying the CAU method. For more information about CAU, see Requirements and Best Practices for Cluster—aware Updating section at Technet.microsoft.com. ● Ensure that Windows Server 2012 R2 or Windows 2016 or Windows 2019 operating system is installed on all failover cluster nodes to support the CAU feature.
19 Manage devices using OMIMSSC Maintain servers and Modular Systems up-to-date by scheduling jobs for upgrading firmware for server and Modular Systems components. Manage servers by recovering servers to an earlier state by exporting its earlier configuration, applying the configurations of the old component on replaced component, and exporting LC logs for troubleshooting.
Remove protection vault You cannot delete a protection vault in the following circumstances: ● The protection vault is associated with a server or a group of servers. To delete such a protection vault, delete the server or group of servers, and then delete the protection vault. ● There is a scheduled job associated with the protection vault. However, to delete such a protection vault, delete the scheduled job, and then delete the protection vault. 1.
● You can import a server profile from a list of exported server profiles for that server only. You cannot import the same server profiles for different servers or server groups. If you try to import server profile of another server or server group, the import server profile job fails.
○ Do not change the value on the server—the existing configuration of the component is retained. ● Part configuration update—restores or upgrades the component configuration based on the selection made. ○ Disabled—the part configuration update is disabled and the saved configuration of the old component is not applied on the replaced component. ○ Apply always—the part configuration update is enabled and the saved configuration of the old component is applied on the replaced component.
1. In OMIMSSC, click Maintenance Center. Select a server or a group of servers, click LC Logs drop-down menu and click View LC Logs. 2. Select the servers’ whose logs you want to view, click LC Logs drop-down menu, and then click View LC Logs. 3. All the servers in the selected group and the servers for which LC logs are collected are listed with their LC log files. Click a file name to view all the log entries in the LC log file specific to that server. For more information, see File description. 4.
20 Deploy Azure Stack HCI cluster Following are the steps to deploy Azure Stack HCI cluster: 1. Create the required Windows and device credential profiles. 2. Create WinPE image a. Install the WDS feature on SCVMM, and then configure it. b. Add PXE server in SCVMM server using add resources and specify the same server name (SCVVM hostname) PXE server. c. Create the shared folder within SCVMM server and then copy Boot.wim from C: \RemoteInstall\DCMgr\Boot\Windows\Images to a share folder. d.
21 Troubleshooting Topics: • • • • • • • • • • • 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 OMIMSSC admin portal scenarios Discovery, synchronization and inventory scenarios in OMIMSSC Generic scenarios in OMIMSSC Firmware update scenarios in OMIMSSC Operating system deployment scenarios in OMIMSSC Server profile scenarios in
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. 2. Configure user access to Windows Management Instrumentation (WMI).
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.
○ Ensure that the SCVMM server is not registered with any other OMIMSSC Appliance. If you want to register the same SCVMM server with the OMIMSSC Appliance, then delete the OMIMSSC Registration Profile application profile from the SCVMM server. ○ If you have applied SCVMM roll up update, then check the Indigo TCP port number of SCVMM console in registry (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager AdministratorConsole\Settings).
SCVMM crashes while importing OMIMSSC console extension SC2016 VMM RTM build 4.0.1662.0 Administrator console may crash when importing OMIMSSC console extension. As a workaround, upgrade SCVMM using the 4094925 KB article available at support.microsoft.com/kb/4094925, and then import the OMIMSSC console extension. Failed to login to OMIMSSC console extensions OMIMSSC console extension login fails with following error message: Failed to login.
Discovery, synchronization and inventory scenarios in OMIMSSC This section has all the troubleshooting information related to credentials issues, discovering servers, grouping servers, synchronizing enrolled Microsoft console with OMIMSSC when using OMIMSSC. Failure to discover servers When multiple Microsoft consoles are enrolled to an OMIMSSC Appliance, and you try to discover a server, if even one of the MECM consoles are not reachable, then the server discovery job will fail.
Unable to synchronize host servers with enrolled MECM During synchronization of OMIMSSC console extension with enrolled MECM, the servers are not listed as sub tasks in synchronization job and hence does not get synchronized. As a workaround, launch MECM console with "Run as Administrator Privilege" and update out of band configuration for a server. Then synchronize OMIMSSC console extension with enrolled MECM.
Generic scenarios in OMIMSSC This section contains troubleshooting information which are independent of any workflow in OMIMSSC. Failure to access CIFS share using hostname The modular servers are not able to access the CIFS share using the host name for performing any job in OMIMSSC. As a workaround, specify the IP address of the server having the CIFS share instead of the host name.
Firmware update scenarios in OMIMSSC This section has all the troubleshooting information related to update sources, update groups, repositories, and inventory after updates. Failure of test connection for local update source After proving the details of a local update source, the test connection may fail as the required files may be not accessible. As a workaround, ensure that catalog.gz file is present in the following folder structure: ● For local DRM update source: \\IP address\\catalog\.
● If Lifecycle Controller (LC) is busy with other operations, then firmware update task on a cluster node fails. To check if the update failed because of LC being busy, check for the following error message in each node of the cluster at the following path: C:\dell\suu\invcolError.log Inventory Failure: IPMI driver is disabled. Please enable or load the driver and then reboot the system. As a workaround, shut down the server, remove the power cables, and then restart the server.
Changing of polling and notification bell color after updating the frequency If a managed server is not discovered in OMIMSSC, and you change the frequency of polling and notification option, the bell color changes to yellow after sometime, even if there are no changes in the catalog. As a workaround, discover managed servers and then change the frequency of polling and notification option.
Operating system deployment scenarios for MECM users This section has all the troubleshooting information related to operating system deployment using OMIMSSC in MECM console. Deploy option not visible in task sequence The Deploy option is not displayed in an existing task sequence after uninstalling and reinstalling OMIMSSC console extension for MECM. As a workaround, open the task sequence for editing, re-enable the Apply option, and click OK. The Deploy option is displayed again.
Hypervisor deployment failure due to driver files retained in library share Hypervisor deployment fails displaying the following error message in activity log: ● Error: Error while applying Hypervisor Profile to host . Failed with error : For input string: "" ● Information: Successfully deleted drivers from library share sttig..com for ● Error: Deleting staging share (drivers) for failed.
As a workaround, reset iDRAC, and then schedule the export server profile job. For more information, see iDRAC documentation available at dell.com/support. Importing server profile job gets timed out after two hours After submitting the import server profile job in OMIMSSC , the job gets timed out after two hours. As a workaround, perform the following steps: 1. Start the server, press F2, and then enter BIOS Settings. 2. Click System Setup, and select Miscellaneous Settings. 3.
22 Appendix I: Time zone attribute values Provide the time zone attribute values manually in MX7000 devices by referring to the bellow table: Table 12.
Table 12.
Table 12.
23 Appendix II: Populate Pool values Populating Pool value CSV file. Table 13. Pool value file format serviceTag(auto populated) FQDD(auto populated) poolAttributeName poolAtrributeValue Service Tag of the device(s) from which the system specific attributes are exported Identifies the component associated to the system specific attribute Identifies the system specific attribute to be configured Set the value for the specified system specific attribute Table 14.
Table 14.
Table 14.
Table 14.
Table 16.
24 Accessing support content from the Dell EMC support site Access supporting content related to an array of systems management tools using direct links, going to the Dell EMC support site, or using a search engine. ● Direct links: ○ For Dell EMC Enterprise Systems Management and Dell EMC Remote Enterprise Systems Management—https:// www.dell.com/esmmanuals ○ For Dell EMC Virtualization Solutions—https://www.dell.com/SoftwareManuals ○ For Dell EMC OpenManage—https://www.dell.