Owner's Manual
Table Of Contents
- Dell Lifecycle Controller Integration For Microsoft System Center Configuration Manager Version 2.0.1 Installation Guide
- Introduction
- Prerequisites
- Configuring An Account For Use With Discovery And Handshake
- Configuring User Access To WMI
- Providing User Permissions For DCOM
- Providing User Permissions For DCOM Config WMI
- Setting Namespace Security And Granting Permissions
- Validating User Permissions From The Dell Provisioning Server
- Providing Share And Folder Permissions
- Enabling Remote PowerShell Commands For Dell Provisioning Server
- Software Prerequisites And Requirements
- Configuring An Account For Use With Discovery And Handshake
- Installing DLCI For Configuration Manager
- Troubleshooting
– 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% 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.
To configure NFS:
* For Windows 2008, see technet.microsoft.com/enus/ library/cc753302(v=ws.10).aspx
* For Windows 2008, R2 see technet.microsoft.com/enus/ library/dd758767(v=ws.10).aspx
– Status messages are received at port 4434. Confirm that a firewall exception is set for this port, else the
TaskViewer will 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 TaskViewer can get the status messages: In the DLCTaskManager.exe.config
configuration file, modify key= "NON_WIN_OSD_STATUS_PORT" and for example, value="4434".
Ensure that the new port is not in use.
– Connect the network adapter to the network for the server on which the operating system is deployed.
– Confirm that virtual disk is available on the target system.
– Servers with ESXi deployed are moved to another collection Managed Dell Lifecycle Controller (ESXi 5).
– If DHCP lookup fails while deployment then the server times out and it is not moved into Managed Dell
Lifecycle Controller (ESXi 5).
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 prerequisites and requirements, see
Component-Specific Prerequisites.
Component-Specific Prerequisites
The DLCI for Configuration Manager installer verifies the following prerequisites before installation:
During Initial Startup
• Regsrv32.exe
• WinRM
• Client for NFS
• PowerShell 2.0
• For Configuration Manager 2007
– Microsoft Windows Server 2003 SP1 or later
– Microsoft .NET version 3.5 SP1 or 4.0
• For Configuration Manager 2012
– Microsoft Windows Server 2008 R2 or later
– Microsoft .NET version 4.0
For DLCU
• Installation on primary Site Server or Configuration Manager Admin console
• Dell Server Deployment Pack 2.0 or later
• Windows Automation Install Kit (Windows AIK)
• For working with non-Windows operation system deployment feature, on a server running Red Hat Linux
operating system, preferably use Network File System version 3.0 (NFSv3).
11