Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In

Dell Lifecycle Controller Integration Version 3.3 for Microsoft System Center Configuration Manager Installation Guide

PDF

Software pre-requisites and requirements

About this task

Before you install DLCI for Configuration Manager, complete the following pre-requisites:

Steps

  1. Install Microsoft System Center Configuration Manager Version 1610, Microsoft System Center 2012 SP2 Configuration Manager, Microsoft System Center 2012 R2 SP1 Configuration Manager, Microsoft System Center 2012 R2 Configuration Manager, Microsoft System Center 2012 SP1 Configuration Manager, or Microsoft System Center 2012 Configuration Manager. For details on how to download and install Configuration Manager, see technet.microsoft.com
  2. Ensure that at least 40 MB of free disk space is available on the system to install DLCI.
  3. Install .NET version 4.0 on systems running Microsoft System Center Configuration Manager Version 1610, Microsoft System Center 2012 SP2 Configuration Manager, Microsoft System Center 2012 R2 SP1 Configuration Manager, Microsoft System Center 2012 R2 Configuration Manager, Microsoft System Center 2012 SP1 Configuration Manager, or Microsoft System Center 2012 Configuration Manager.
  4. Install Windows Remote Management (WinRM) and .NET 4.0, if you are installing DPS on systems running Microsoft Windows Server 2008 and 2008 R2.
  5. Ensure that you have installed the Configuration Manager Console (admin console) before you install DPS.

    Before installing DPS, the DLCI installer checks if the admin console is installed. If the admin console is not installed, the installer displays an error message. The installation does not continue until the admin console is installed.

    • NOTE: The DLCI installer only checks for the installation of Configuration Manager admin console. It does not check whether the same version of Configuration Manager is installed on the site server where DPS drops the discovery records. Ensure that you have installed the correct version of the admin console.
  6. Ensure that the required KB articles are available: If you are installing DLCI on a system running Windows Server 2008 R2 64–bit, then do this update: KB981506 — "SSL Certificate add failed, Error: 1312" error message when you try to add a CTL in Windows Server 2008 R2 or in Windows 7. See support.microsoft.com/kb/981506.
  7. For DLCI for Configuration Manager, agent-free configuration, updates, and bare-metal OS deployment, continue as node-based licensed features. A configuration manager requires a node-based license to manage Dell PowerEdge servers. A configuration manager lists the number of nodes consumed. To view the nodes consumed: In Configuration Manager , select Assets and Compliance > Overview > Device Collections > All Dell Lifecycle Controller Servers, and check the node Count. You require sufficient licenses to manage Dell PowerEdge servers (nodes). If the number of nodes increase in a data center and you require license with additional node capacity, contact a Dell sales representative.
  8. If you do not have the administrator privileges and you want to automatically configure Dell Provisioning Server and in addition you are planning on installing DPS on one server and Dell Lifecycle Controller Integration on another server, consider the following:
  9. For working with deploying non-Windows operating systems on target systems task, complete the following pre-requisites:
    • For deploying non-Windows operating systems, you require Network File System (NFS). The NFS can be either Client for NFS or Services for Network File System.
    • Install Client for NFS on the system where site server/admin console or Dell Lifecycle Controller Integration is installed. NFS share name is case-sensitive.
    • NFS is configured to have Anonymous/Unmapped read access for all systems. The NFS has read and write access for site server and admin console. Confirm that the site server, admin console, and the system on which the NFS share is present are in the same domain. NFS must contain at least 60 percent of free space. It is recommended that NFS share is hosted on a private network with no access to internet. However, make NFS accessible from site server, admin console, and all the iDRACs.
    • Status messages are received at port 4434. Confirm that a firewall exception is set for this port, else the Task Viewer does not receive any operating system deployment status messages from the server on which the operating system is being installed.

      To change the port on which Task Viewer can get the status messages: In the DLCTaskManager.exe.config configuration file, modify key= "NON_WIN_OSD_STATUS_PORT" and value="4434".

      Ensure that the new port is not in use.

    • Confirm that virtual disk is available on the target system.
    • Servers, where ESXi are deployed, are moved to another collection Managed Dell Lifecycle Controller (ESXi).
    • If DHCP lookup fails while deployment, then the server times out and it is not moved into Managed Dell Lifecycle Controller (ESXi).
It is recommended that the network adapter is connected to the network port in the server on which the operating system is being deployed. For information on component-specific software pre-requisites and requirements, see Component-specific pre-requisites .

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\