Dell Lifecycle Controller Integration Version 2 0 1 For Microsoft System Center Configuration Manage Owners Manual Manager Readme

: Dell Dell-Lifecycle-Controller-Integration-Version-2-0-1-For-Microsoft-System-Center-Configuration-Manage-Owners-Manual-117711 dell-lifecycle-controller-integration-version-2-0-1-for-microsoft-system-center-configuration-manage-owners-manual-117711 dell pdf

Open the PDF directly: View PDF .
Page Count: 7

Dell Lifecycle Controller

Integration for

Microsoft System Center

Configuration Manager

Version 2.0.1

Readme

Dell Lifecycle Controller Integration (DLCI) for Microsoft System Center Configuration Manager enables the

administrators to use the Configuration Manager console to leverage the remote enablement capabilities of

Dell Lifecycle Controller (LC), available as part of the integrated Dell Remote Access Controller (iDRAC).

What’s New

•

Support for Dell's 12th Generation PowerEdge Servers

•

Support for Microsoft System Center 2012 Configuration Manager

•

Support for deployment of Red Hat Enterprise Linux Version 6.2, VMware ESXi 5 HDD, and

VMware ESXi 5 U1 HDD

Software Requirements

•

System Center 2012 Configuration Manager or System Center Configuration Manager 2007

•

Dell Server Deployment Pack 2.0 (DSDP 2.0)

•

On Microsoft Windows Server 2008 and Microsoft Windows Server 2008 R2 systems where

you have installed the provisioning server, Install Windows Remote Management (WinRM).

Installation

For installation instructions, see Dell Lifecycle Controller Integration Version 2.0.1 for Microsoft System Center

Configuration Manager Installation Guide.

Supported Target Systems and Operating Systems

For the list of Dell systems and operating systems deployable on the target systems, see the User Guide of Dell

Lifecycle Controller Integration Version 2.0.1 for Microsoft System Center Configuration Manager.

Notes

•

When you deploy an operating system on a target system with iDRAC configured in a shared

network mode, the Windows PE environment may fail to startup on the network drivers,

causing the system to restart before reaching the task sequence.

•

If the Lifecycle Controller of a system is in use, the system is not discovered.

•

If the iDRAC version is older than the supported versions in any of the target systems, the

Boot to vFlash option in the Deploy Operating Systems workflow may fail.

•

When you are deploying an operating system using the Launch Config utility, the

advertisements of the task sequence are not displayed on the screen.

•

If the target system has an older version of BIOS that does not support a particular method,

the following error message is displayed in the DLCTaskManager.log file:"Installed BIOS

version does not support this method."

•

If the Lifecycle Controller of the target system is locked by another process, the following

error message is displayed in the DLCTaskManager.log file: "Lifecycle Controller is being

used by another process."

•

If you do not enter the service tag name of the target system correctly, the discovery and

handshake fails and the following error message is displayed:

•

"[Server Name] - Handshake - getCredentialsInternal():[Server Name]: NOT AUTHORIZED: No

credentials returned."

•

To deploy Microsoft Windows Server 2003 operating systems using the Apply Drivers from

LC option, ensure that there is a fallback step to install drivers from Configuration Manager,

else the deployment fails.

•

During Discovery and Handshake, the DPS.log displays an empty "Site code:" followed by a

cryptography exception.

•

During Discovery and Handshake, the DPS.log displays numerous messages

"createDellCollecions() Either Connection Mgr param is NULL or Collection not yet created."

•

The System Viewer utility does not display the latest RAID configuration. To view the latest

configuration re-launch the System Viewer utility.

•

The modular systems cannot use the hostname in the path to the Common Internet File

System (CIFS) share but monolithic systems can use the hostname. Use the IP address

instead of hostname.

•

After deploying Non-Windows Operating System using DLCI the service tag of system name

is displayed as Hostname in configuration manager console.

Open Issues and Resolutions

Issue 1

Description - During installation of DLCI, the Configuration Manager credentials specified are not validated.

Installation will succeed and an error in import.log will indicate the same. Use DPS configure utility

(import.exe) to specify the correct credentials before proceeding with discovery of servers.

Issue 2

Description -

The Advertise option does not appear in an existing task sequence after uninstalling and

reinstalling DLCI for Configuration Manager. To advertise the task sequence, edit the task sequence and

correct if there are any errors.

Fixed Issues/def

Issue 3

Description - If Active Directory(AD) authentication is used for communicating with iDRAC on modular

servers, ensure the iDRAC version is upgraded to 3.32.

Versions Affected - DLCI 2.0.1 with 11G iDRAC 3.30 (or earlier).

Issue 4

Description -

If the host system has Lifecycle Controller version 1.5, ensure that while configuring username

as part of iDRAC configuration, the username length is less than 16.

Versions Affected - DLCI 2.0.1 with 11G Lifecycle Controller 1.5

Issue 5

Description -

If the host system is 11G server and has Lifecycle Controller version 1.5, RAID configuration of

H200 controller using DLCI 2.0.1 does not work correctly.

Resolution -

Upgrade to Lifecycle Controller firmware version 1.5.1.

Versions Affected - DLCI 2.0.1 with 11G Lifecycle Controller 1.5

Issue 6

Description -

To perform firmware updates from ftp.dell.com for PowerVault NX300 systems ensure that 1G

Lifecycle Controller version is 1.5.1 or higher.

Issue 7

Description - While performing Import Dell Servers if the Dell Connections License Manager has Unlimited

number of licenses then soon after Authentication to iDRACs the next page on Import Dell Server Wizard

shows all non licensed servers as Licensed. But completing the Import Process does not acquire more than

one license for any server.

Resolution

Versions Affected

Issue 8

Description - While applying minimum bandwidth on Qlogic Partitionable NIC cards, if the summation of

minimum bandwidth on all partitions of a port reaches more than 100 the apply operation will fail. Ensure

that you apply 0 on all partitions as minimum bandwidth before applying any other values.

Resolution

Versions Affected

Issue 9

Description -

BIOS Configuration will fail when it is done for the second time if 11G server has either 1.9

(monolithic) or 3.4 (modular) version of iDRAC firmware. Ensure you upgrade the iDRAC firmware level to

1.92(monolithic) or 3.42 (modular).

Issue 10

Description -

In DLCI for Configuration Manager version 1.3 or version 2.0, if Platform Restore is run on a

collection where servers are identified by hostname (instead of service tag) and the server profiles are

exported to a share, then to import the server profiles after upgrading to DLCI 2.0.1.

1. Open the share location where profiles are exported.

2. For the filename formats <prefix>-<hostname>. Rename the filename format to <prefix>-<servicetag>.

3. Do step 2 to all exported files.

Issue 11

Description -

In DLCI for Configuration Manager 1.3 or version 2.0, in the System Viewer utility, the cached

network paths in the Export Lifecycle Controller Logs, Firmware Update, and Platform Restore workflows

saved after hostname is changed are not retained after upgrading to DLCI 2.0.1.

Issue 12

Description -

If you have scheduled a firmware update in DLCI for Configuration Manager version 1.3 or

version 2.0, and the hostname is changed (due OS deployment), then after upgrade to DLCI 2.0.1, the

firmware update schedule will not run.

Resolution - Configure the firmware update schedule and run the schedule again.

Issue 13

Description -

In case of remote installation of DPS if "Repair" action is executed then to perform Auto

Discovery of servers:

1. Uninstall and install the DPS component.

OR

2. You can edit the registry entry. Open REGEDIT and traverse to "HKLM\SOFTWARE\DELL\Provisioning

Service\Repository"(For 32-bit systems) or "HKLM\SOFTWARE\Wow6432Node\DELL\Provisioning

Service\Repository" (for 64-bit systems) set the value of "RemoteInstallPath" to "<Configuration

Manager Admin Console Install Directory>\XmlStorage\Extensions\DLCPlugin"

Issue 14

Description -

Before installing Dell Provisioning Server for Configuration Manager 2012 component of DLCI

on a system having Windows Server 2008 or a lower version of the Windows operating system, ensure

that .NET version 3.5 is installed.

Issue 15

Description -

(Recommended) To install a non-Windows operating system on a server that is already

installed with Windows operating system and Configuration Manager Client is configured; before installing

the Non-Windows OS, delete and reimport the server from Configuration Manager.

Corrected Problems

The following problems were reported in earlier releases of <XXX> and have been corrected in this release:

Issue 1

Description -

Before starting Hardware Configuration and Operating System Deployment or a Firmware

Update task on a collection or a system, ensure that there are no tasks currently running for the collection.

Issue 2

Description -

If servers are discovered using Autodiscovery method with Dell Connections License Manager

configured and acquired licenses from an admin console for the first time (site server did not acquire any

license) then Managed collection does not get created. Servers are moved out of Unmanaged collection

(OS unknown) to All Dell Lifecycle controller collection but Managed collection does not get created.

Ensure that you run acquired licenses on site server.

Global Support

For information on technical support, visit www.dell.com/contactus.

For more information on the resolutions for the above issues, see the Issues and Resolutions section of the

Dell Lifecycle Controller Version 2.0.1 For Microsoft System Center Configuration Manager User's Guide,

available on the Dell Support site at support.dell.com/manuals.

For information on documentation support, visit support.dell.com/manuals. On the Manuals page, click

Software ->Systems Management. Click on the specific product on the right-side to access the documents.

Information in this document is subject to change without notice.

© 2012 Dell Inc. All rights reserved.

Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc. is strictly forbidden.

Trademarks used in this text: Dell™, the Dell logo, Dell Boomi™, Dell Precision™ , OptiPlex™, Latitude™, PowerEdge™, PowerVault™,

PowerConnect™, OpenManage™, EqualLogic™, Compellent™, KACE™, FlexAddress™, Force10™ and Vostro™ are trademarks of Dell Inc.

Intel®, Pentium®, Xeon®, Core® and Celeron® are registered trademarks of Intel Corporation in the U.S. and other countries. AMD®is a

registered trademark and AMD Opteron™, AMD Phenom™ and AMD Sempron™ are trademarks of Advanced Micro Devices, Inc. Microsoft®,

Windows®, Windows Server®, Internet Explorer®, MS-DOS®, Windows Vista® and Active Directory® are either trademarks or registered

trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat® and Red Hat®Enterprise Linux® are registered

trademarks of Red Hat, Inc. in the United States and/or other countries. Novell® and SUSE® are registered trademarks of Novell Inc. in the United

States and other countries. Oracle® is a registered trademark of Oracle Corporation and/or its affiliates. Citrix®, Xen®, XenServer® and

XenMotion® are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/or other countries. VMware®, Virtual

SMP®, vMotion®, vCenter®, and vSphere® are registered trademarks or trademarks of VMware, Inc. in the United States or other countries.

IBM® is a registered trademark of International Business Machines Corporation.Other trademarks and trade names may be used in this publication to

refer to either the entities claiming the marks and names or their products. Dell Inc. disclaims any proprietary interest in trademarks and trade names

other than its own.

2012 - 10 Rev. A00