OpenManage Integration Version 7.
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. Copyright © 2009 - 2017 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents 1 Introduction....................................................................................................................................................7 OMIMSSC features............................................................................................................................................................7 2 About OMIMSSC components.......................................................................................................................
Server discovery in OMIMSSC console extension for SCVMM................................................................................ 23 System requirements for managed systems ............................................................................................................... 23 Discovering servers using auto discovery..................................................................................................................... 24 Discovering servers using manual discovery...............
Applying updates on servers.....................................................................................................................................42 Recovery........................................................................................................................................................................... 49 Protection vault......................................................................................................................................................
16 Accessing documents from the Dell EMC support site............................................................................... 65 Contacting Dell.................................................................................................................................................................
1 Introduction OpenManage Integration for Microsoft System Center (OMIMSSC) provides integrations into the System Center suite of products that enable full lifecycle management of the Dell EMC servers by using the integrated Dell Remote Access Controller (iDRAC) with Lifecycle Controller (LC). OMIMSSC offers operating system deployment, hardware patching, firmware update, and server maintenance.
Microsoft Cluster-Aware Updating (CAU) Automate the firmware update process through the CAU feature of Microsoft. Export inventory After comparing the servers inventories against the update source, you can export the comparison report to .CSV or .XML file.
2 About OMIMSSC components The following is the list of the OMIMSSC components and their names that have been used in this guide: • • • OpenManage Integration for Microsoft System Center Appliance virtual machine, also known as Appliance is hosted 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.
3 About Admin Portal The Admin Portal allows you to log in to OMIMSSC as an administrator to view all jobs started in OMIMSSC by various users, view license details, console details, download the required components, and to upgrade OMIMSSC. Following are the use cases in admin portal along with licensing.
Repairing OMIMSSC console extension for SCCM To repair the OMIMSSC files in case they are corrupt, perform the following steps: 1 Run the OMIMSSC console extension for SCCM 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.
4 Launching OMIMSSC from enrolled MSSC console Launch OMIMSSC from enrolled SCCM or SCVMM console.
5 Use cases You can deploy OS only on servers whose hardware configuration is compatible with OMIMSSC. Before deploying OS, make sure you upgrade the firmware versions to the latest versions available at ftp.dell.com or downloads.dell.com, and then continue with OS deployment.
OS deployment using OMIMSSC console extension for SCVMM About this task To deploy OS on the selected servers, perform the following steps: Steps 1 Download the latest Dell Deployment ToolKit (DTK) and create a Windows Preinstallation Environment (WinPE) boot ISO image. For more information, see the WinPE update. 2 Create a physical computer profile in SCVMM. For more information, see the SCVMM documentation. 3 Create a target host group in SCVMM. For more information, see the SCVMM documentation.
Steps 1 Before you begin updates, view information about update sources and update groups. For more information about update source, see Update source. Ensure that there is an update source created. For more information, see Creating an update source. 2 Discover or synchronize servers with registered MSSC. For more information, see Device discovery and synchronization .Ensure that the servers inventory is up-to-date. For more information, see Launching configuration and deployment.
6 Profiles Profiles allow you to manage your credentials and customize WinPE images for deployment. The various types of profiles supported in OMIMSSC are: Topics: • About credential profile • About hypervisor profile About credential profile 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.
• During auto discovery, if there is no credential profile available for iDRAC, then the default iDRAC factory settings is used. The default user name is root, and password is calvin. Steps 1 In OMIMSSC, do any of the following to open Credential Profile: • 2 In the OMIMSSC dashboard, click Create Credential Profile. • In the navigation pane, click Profiles > Credential Profile, and then click Create. In Credential Profile, select the credential profile type that you want to use.
Deleting credential profile About this task 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 Appliance. • To delete a credential profile that is used in server discovery, delete the discovered server information and then delete the credential profile.
c 7 Select the hypervisor version Hypervisor Version. In Summary, click Finish. Modifying hypervisor profile About this task Consider the following when you are modifying a hypervisor profile: • You can modify host profile, host group, and drivers from Lifecycle Controller. • You can change the WinPE ISO name. However, you cannot modify the ISO image. Steps 1 Select the profile that you want to modify and click Edit. 2 Provide the details, and click Finish.
7 Launching Configuration and Deployment The Configuration and Deployment page lists all unassigned and host servers. By using the host name or IP address of a server, you can view the server details such as the iDRAC IP address or host name, server identifier, cluster FQDN, chassis service tag, server model, server generation, CPU, memory, and compliance status. On hovering with your mouse over the Hardware Compatibility column, you can view the versions of BIOS, iDRAC, LC, and driver packs.
Steps In the OMIMSSC console extension, click Configuration and Deployment. NOTE: All the server groups that exist in registered MSSC are listed in OMIMSSC because this page is not userspecific. Make sure you have access to perform any operations on those servers. All the servers discovered or synchronized with the registered MSSC are listed under the Unassigned Servers or Hosts tab.
8 Discovering servers and synchronizing with MSSC console Discovery is the process of adding supported PowerEdge bare-metal server or host servers in OMIMSSC, and synchronization with MSSC console allows you to add host servers from SCCM or SCVMM console into OMIMSSC.
• • If the host is a modular server, then the service tag of the chassis containing the server is also displayed on the Configuration and Deployment page. When you discover a PowerEdge server that is not listed in SCCM or SCVMM, then the server is listed as an unassigned server under the Unassigned tab in all the enrolled OMIMSSC console extensions.
Discovering servers using auto discovery To automatically discover the servers, connect the PowerEdge servers to the network and power on the servers for OMIMSSC. OMIMSSC auto discovers the unassigned Dell EMC servers by using the remote enablement feature of iDRAC. OMIMSSC works as the provisioning server and uses the iDRAC reference to auto discover Dell EMC servers. 1 In OMIMSSC, create a device type credential profile (by specifying the iDRAC credentials and marking it as default) for Dell EMC servers.
• Update the Dell Default Collection before synchronizing OMIMSSC with SCCM. However, if an unassigned server is discovered in SCCM, it is added to Import Dell server collection. To add this server in Dell Default Collection, add the server's iDRAC IP address in the OOB page.
Steps 1 In OMIMSSC, click Configuration and Deployment and then click Resolve Sync Errors. 2 Select the servers for resyncronization, and select the credential profile, or to create a credential profile click Create New. 3 Provide a job name, and if necessary select the Go to the Job List option to view the job status automatically once the job is submitted. 4 Click Finish to submit the job. Deleting servers from OMIMSSC About this task After you delete a server, the consumed license is relinquished.
9 OMIMSSC licensing 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.
If there are already multiple licenses uploaded, the number of supported servers are the sum of the servers in the licenses at the time the last license was uploaded. Replacement of licenses If there is a problem with your order, or when you try to upload a modified or corrupt file, an error message is displayed for the same. You can request for another license file from the Dell Digital store.
Importing license in to OMIMSSC About this task After purchasing a license, import it in to OMIMSSC by performing the following steps: Steps 1 In Admin Portal, click License Center. 2 Click Import License and browse to select the license file downloaded from the Dell Digital store. NOTE: You can import only valid license files. If the file is corrupt, or tampered, then an error message is displayed accordingly.
10 Operational Template Operational Template deploys operating systems and updates firmware versions on PowerEdge servers within MSSC environment . You can capture the complete server configuration from a reference server, and then configure the hardware configurations, set firmware update attributes and OS parameters in an Operational Template and deploy this template across servers.
Lifecycle Controller. While using the latest version of DTK for creating a WinPE ISO image, use the WinPE version of the DTK files. DTK file contains the necessary firmware versions required for servers on which you are deploying the operating systems. Prerequisites NOTE: While using the latest version of DTK for creating a WinPE ISO image, use the Dell OpenManage Deployment Toolkit for Windows file.
• Install the latest BIOS version on the system. • Install the latest version of Lifecycle Controller on the system. • Install the latest version of iDRAC firmware on the system. NOTE: Always launch the Configuration Manager console with administrator privileges. Creating a task sequence You can create a task sequence in two ways which will be used for server configurations: • Create a Dell-specific task sequence using OMIMSSC Deployment template. • Create a custom task sequence.
7 Review your settings and click Next. 8 Click Close in the confirmation message box that is displayed. Editing a task sequence About this task NOTE: While editing task sequence on SCCM 2016, the missing objects references messages does not list Setup windows and ConfigMgr package. Add the package and then save the task sequence. Steps 1 Launch the Configuration Manager. The Configuration Manager screen is displayed. 2 In the left pane, select Software Library > Operating Systems > Task Sequence.
4 Under Default Share Location for Custom Lifecycle Controller Boot Media, click Modify to modify the default share location of the custom Lifecycle Controller boot media. 5 In the Modify Share Information window, enter a new share name and share path. 6 Click OK. Creating a task sequence media bootable ISO 1 In Configuration Manager under Software Library, right-click Task Sequences, and select Create Task Sequence Media.
• (Optional) In OMIMSSC for SCCM: • Create a task sequence. For more information, see Creating task sequence. • • For non-Windows OS deployment, have a device type credential profile. For more information, see Creating credential profile. • Create an unattended boot media. For more information, see Creating LC boot media. (Optional) In OMIMSSC for SCVMM: • Create a hypervisor profile. For information about creating hypervisor profile, see Creating hypervisor profile.
3 • Stage ISO to vFlash and Reboot—downloads the ISO to vFlash and reboots. • Reboot to vFlash—reboots to vFlash. Ensure that the ISO is present in the vFlash. NOTE: To use the Reboot to vFlash option, the label name of the partition created on vFlash must be ISOIMG. (Optional) to use the image present in the network share if the image present in vFlash is corrupt select the Use Network ISO as Fallback option. 4 Provide an LC boot media image file, and (optional) use Enable LC Drivers Injection.
NOTE: Network File System (NFS) and Common Internet File System (CIFS) share types are supported for nonWindows OS deployment. Viewing Operational Template To view Operational Template templates: In OMIMSSC console, click Profiles and Templates, and then click Operational Template. All the Operational Template templates created are listed here.
Non-Windows component for OMIMSSC console extensions While editing Operational Template, perform the following steps mentioned in Non-Windows OS component for OMIMSSC console extensions. Deleting Operational Template To delete an Operational Template, perform the following steps: About this task Before deleting an Operational Template, ensure that: • The selected Operational Template is not associated with any server.
Steps 1 In OMIMSSC, click Configuration and Deployment. Select the servers on which you want to deploy a template on, and then click Deploy Operational Template. The Deploy Operational Template page is displayed. 2 (Optional) To export all the attributes marked as pool values in the selected template to a .CSV file, click Export Pool Attributes, else, go to step 3.
11 Integration with Dell Repository Manager(DRM) OMIMSSC is integrated with DRM version 2.2 onwards providing the server inventory information of the existing servers from the OMIMSSC Appliance to DRM. By using the inventory information, you can create a custom repository in DRM and set it as an update source in OMIMSSC Appliance for performing firmware update jobs on the servers, or group of servers. For more information about creating a repository in DRM, see Dell Repository Manager documents.
12 Maintenance Using Maintenance Center page you can export server inventory, and schedule jobs for upgrading the servers, recovering servers to an earlier state by exporting its earlier configuration, applying the same configurations as that of the old component on replaced components, and exporting LC logs for troubleshooting.
• • Integration with Dell Online Catalog—connect to Dell FTP and download the catalog file in the cache directory if it is an FTP update source, or connect to downloads.dell.com if it is an HTTP update source, and then make it as a reference inventory. • View the comparison report against the update source, select the relevant servers or server components, and then initiate an update on the servers.
NOTE: Updates for cluster update group happen through cluster update coordinator that is present on the same system where the IG is installed. The update job is submitted to Microsoft Cluster-Aware-Update (CAU) feature, irrespective of the selection made from the Update Method drop-down menu. For more information, see Updates using CAU.
Update source overview Update source enables you to select and apply updates from Dell’s update sources. You can create, view, and manage the update sources. The types of update sources supported are DRM repository, FTP, and HTTP. You can create a DRM, HTTP, or FTP update source and set it as a default update source.
3 Extract the catalog.xml file, and change the baseLocation to your local HTTP URL, and compress the file with .gz extension. For example, change the baseLocation from downloads.dell.com to host name or IP address such as hostname.com. 4 Place the catalog file with the modified catalog file, and the DUP files in your local HTTP folder replicating the same structure in downloads.dell.com. Viewing update source 1 In OMIMSSC, click Maintenance Center.
• • • You cannot change the type of an update source and the location after the update source is created. You can modify an update source even if the update source is in use by an in-progress or a scheduled job, or if it is used in a deployment template. A warning message is displayed while modifying the in-use update source. Click Confirm to continue with the changes. When a catalog file is updated in the update source, the locally cached catalog file is not automatically updated.
Default host update group—this group consists of all the discovered hosts that are not part of any other update group. This group is of the type host update group. Chassis update group—modular servers belonging to a chassis and not part of any cluster group are classified as chassis update group. 12th or 13th generation of PowerEdge servers are discovered along with their CMC information. By default, a group is created with the naming format, Chassis-Service-tag-of-Chassis-Group.
4 To add servers in the update group, search for the servers by using their service tag, and to add servers into the Servers Included in the Update Group table, click the right arrow. 5 To create the custom update group, click Save. Modifying custom update groups About this task Consider the following points when you are modifying a custom update group: • You cannot change the type of an update group after it is created.
Viewing and refreshing firmware inventory You can view and refresh the firmware inventory of servers or a specific group of servers. You can view comparison report of a server or chassis inventory against a selected update source. You can change the update source, and view the comparison report of inventory information of the selected servers, server groups, or chassis against the changed update source.
Creating protection vault Prerequisites Ensure that vault location is accessible. Steps 1 In OMIMSSC, click Maintenance Center, and then click Maintenance Settings. 2 In Maintenance Center, click Protection Vault, and then click Create. 3 Select a type of protection vault you want to use and provide the details. • If you are creating a protection vault of type Network Share, provide a location to save the profiles, credentials to access this location and a passphrase to secure the profile.
About this task NOTE: Ensure that the Automatic Backup job in iDRAC is not scheduled at the same time. NOTE: You cannot export server profiles after applying the filters. To export server profiles, clear all the applied filters. NOTE: To export server profiles, you must have the iDRAC Enterprise license. NOTE: Before exporting the server profile, make sure the IP address of the server is not changed.
Steps 1 In OMIMSSC, under Maintenance Center, select the servers’ whose profiles you want to import, and click Import Server Profile. 2 Provide the details, select the Import Server Profile Type you want. NOTE: Preserve Data is selected by default and preserves the existing RAID configuration in the server. Clear the check box if you want to apply the RAID settings stored in the server profile. 3 To import the server profile, click Finish.
• Complete LC logs—these logs contain active and archived LC log files. They are large and hence compressed to .gz format and exported to the specified location on a CIFS network share. Steps 1 In OMIMSSC, click Maintenance Center. Select a server or a group of servers, and then click Collect LC Logs. 2 In LC Log Collection, select one of the following options, and click Finish: • Export Complete LC Logs (.
NOTE: Before downloading the LC logs, add Appliance in the Local intranet site. To add Appliance in the Local intranet site in Internet Explorer: a Launch a browser, click Tools, and then click Internet Options. b Click Security > Local intranet > Sites. The Local intranet page is displayed. c Click Advanced, type Appliance URL, and then click Add.
13 Viewing information in OMIMSSC You can view all information about the activities initiated in OMIMSSC along with a job's progress status, and its subtask through the Jobs and logs center page. Also, you can filter and view jobs for a particular category. You can view the jobs from the OMIMSSC Admin Portal and OMIMSSC console extension.
Steps 1 In OMIMSSC, click Jobs and Log Center. 2 To view a specific category of jobs, such as Scheduled, History, or Generic, click the required tab. Expand the job to view all the servers included in the job. Expand further to view the log messages for that job. NOTE: All the job-related generic log messages are listed under the Generic tab and not under the Running or History tab. 3 (Optional) apply filters to view different category of jobs and you can view it is status in Status column.
14 Troubleshooting Topics: • Deploy option not visible in task sequence • Duplicate VRTX chassis group gets created • Empty cluster update group does not get deleted during autodiscovery or synchronization • Failure of creation of update source • Failure of firmware update because of job queue being full • Failure of firmware update on cluster update group • Failure of firmware update on 11th generation of servers • Failure of firmware update while using DRM update source • Failure of sched
2 Select Restart in Windows PE. In the Description section, type any character and delete it so the change is not saved. 3 Click OK. This re-enables the Apply option. Duplicate VRTX chassis group gets created When modular servers that were previously in another chassis are added to a VRTX chassis and discovered, the modular servers carry previous chassis service tag information and create a duplicate VRTX chassis group in the Appliance.
As a workaround, delete all the files in Dell folder, and then schedule a firmware update job. Failure of firmware update on 11th generation of servers A firmware update job started on 11th generation of PowerEdge servers may fail due to incompatible versions of iDRAC and LC with the following error: WSMan command failed to execute on server with iDRAC IP . As a workaround, upgrade the iDRAC and LC to the latest versions and then start the firmware update job.
To access the FTP site using Dell Online Catalog as an update source edit, and add the proxy credentials. Failure to create a repository during a firmware update Creation of a repository may fail during a firmware update because of network issues, improper credentials, or server not reachable, and so on. As a workaround, ensure that the FTP server is reachable from where the Appliance is hosted, there are no network issues, and provide the right credentials during a firmware update.
As a workaround, reset iDRAC, and then collect and view the LC Logs. For more information, see iDRAC documentation available at dell.com/support. Firmware update on a few components irrespective of the selection Same components on identical servers get updated during a firmware update irrespective of the selection of components made on individual servers. This behavior is seen for 12th and 13th generation of PowerEdge servers with Enterprise license of iDRAC.
Now, you can deploy operating systems. Hypervisor deployment failure for 11th generation PowerEdge blade servers when using Active Directory Hypervisor deployment fails on the 11th generation PowerEdge blade servers when using the Active Directory user credentials. The 11th generation PowerEdge blade servers use the Intelligent Platform Management Interface (IPMI) protocol for communication. However, the IPMI standard is not supported for using credentials from the Active Directory setup.
After performing the following steps, schedule the export server profile job and use the same to complete the import server profile job successfully. Latest inventory information is not displayed even after firmware update Even though the firmware update job is complete on an 11th generation of PowerEdge server, in the Appliance, the inventory does not display the latest firmware versions.
15 Appendix 64 Appendix
16 Accessing documents from the Dell EMC support site You can access the required documents using the following links: • For Dell EMC Enterprise Systems Management documents — Dell.com/SoftwareSecurityManuals • For Dell EMC OpenManage documents — Dell.com/OpenManageManuals • For Dell EMC Remote Enterprise Systems Management documents — Dell.com/esmmanuals • For iDRAC and Dell EMC Lifecycle Controller documents — Dell.
