Reproduction of these materials in any manner whatsoever without the written permission of Dell Inc.
is strictly forbidden.
Trademarks used in this text: Dell™, PowerEdge™, and Dell OpenManage™ are trademarks of Dell
Inc.; Microsoft
Microsoft Corporation in the United States and/or other countries.
Other trademarks and trade names may be used in this document 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.
2011 - 09
®
, Windows®, and W indo ws Vista® are either trademarks or registered trademarks of
This document describes the activities that you can perform with Dell Client
Integration Pack for Microsoft System Center Configuration Manager (DCIP
for ConfigMgr).
What is New in This Release of DCIP for
ConfigMgr
This release of DCIP for ConfigMgr supports the following features:
Table 1-1.New Features
FeatureDescription
OMCI IntegrationThis feature enables ConfigMgr to use the features
available on Dell OpenManage Client Instrumentation
(OMCI) such as remote management applications,
accessing managed node information, manage client
state, receiving alerts for client events. For more
Importing OMCI
.
Dell Warranty
Information Utility
Intel AMT vPro OOB
Management
information on OMCI integration, see
This feature monitors warranty information of all Dell
client computers on your network by collecting the
warranty information of Dell Client computers from the
Dell support website and storing them on the ConfigMgr.
For more information on the Dell Warranty Information
Utility, see
This is an Out-of-band (OOB) management feature using
Intel AMT. It is supported through a standalone
application running on the SCCM server. This feature
provides the core functionality, to manage client systems
remotely and automatically regardless of the state of the
operating system. For more information on Intel AMT
vPro OOB Management, see
Extensions
Dell Warranty Information Utility
Intel vPro OOB Management
.
.
Introduction7
Table 1-1.New Features
FeatureDescription
Client Configuration
Toolkit 2.0
Dell Client Configuration Toolkit (CCTK) is a packaged
software offering that provides BIOS configuration
capability to Dell client systems such as OptiPlex,
Latitude, and Precision in an operating system present
environment. The configuration of target machine can be
setup using a Graphical User Interface (GUI) or a
Command Line Interface (CLI). CCTK is designed to
run under various operating systems environment
namely-, Microsoft Windows Pre-installation
Environment (Windows PE), Microsoft Windows XP,
Windows Vista, and Windows 7 in an unattended
manner. Starting with CCTK version 2.0, end users can
create a self-contained executable (SCE) package using
CCTK GUI interface for configuring target systems in a
one to many environment. DCIP version 2.0 allows end
users to import custom generated SCE Packages for use
within their deployment task sequence. For more
information on CCTK integration, see
Key Features and Functionalities
Table 1-2.Key Features and Functionalists
Importing CCTK
.
FeatureDescription
Configuring Windows
Pre-Installation (PE)
environment
Creating and Importing
Dell Client Driver
Packages
This feature enables ConfigMgr to configure and push
your customized operating system image on your client
system using the features available on DCIP. For more
information on configuring your Windows PE
environment, see
This feature enables ConfigMgr to configure and push
your customized driver packages onto your client system.
For more information on creating Dell client driver
packages, see
8Introduction
Creating Dell Windows PE Boot Image
Creating Dell Client Driver Packages
.
.
Table 1-2.Key Features and Functionalists
FeatureDescription
OMCI IntegrationThis feature enables ConfigMgr to use the features
available on Dell OpenManage Client Instrumentation
(OMCI) such as remote management applications,
accessing managed node information, manage client
state, receiving alerts for client events. For more
Importing OMCI
.
Dell Warranty
Information Utility
Intel AMT vPro OOB
Management
information on OMCI integration, see
This feature monitors warranty information of all Dell
client computers on your network by collecting the
warranty information of Dell Client computers from the
Dell support website and storing them on the ConfigMgr.
For more information on the Dell Warranty Information
Utility, see
This is an Out-of-band (OOB) management feature using
Intel AMT. It is supported through a standalone
application running on the SCCM server. This feature
provides the core functionality to manage client systems
remotely and automatically regardless of the state of the
operating system. For more information on Intel AMT
vPro OOB Management, see
Extensions
Dell Warranty Information Utility
Intel vPro OOB Management
.
.
Introduction9
Table 1-2.Key Features and Functionalists
FeatureDescription
Client Configuration
Toolkit 2.0
Dell Client Configuration Toolkit (CCTK) is a packaged
software offering that provides BIOS configuration
capability to Dell client systems such as OptiPlex,
Latitude, and Precision in an operating system present
environment. The configuration of target machine can be
setup using a Graphical User Interface (GUI) or a
Command Line Interface (CLI). CCTK is designed to
run under various operating systems environment
namely-, Microsoft Windows Pre-installation
Environment (Windows PE), Microsoft Windows XP,
Windows Vista, and Windows 7 in an unattended
manner. Starting with CCTK version 2.0, end users can
create a self-contained executable (SCE) package using
CCTK GUI interface for configuring target systems in a
one to many environment. DCIP version 2.0 allows end
users to import custom generated SCE Packages for use
within their deployment task sequence. For more
information on CCTK integration, see
Importing CCTK
Supported Operating Systems and Dell Devices
For information, on the supported configurations for ConfigMgr, see
http://technet.microsoft.com/en-us/library/cc161860.aspx.
.
Supported Operating Systems for DCIP
•Windows 7 32-bit Professional English
•Windows 7 64-bit Professional English
•Windows 7 32-bit Ultimate English
•Windows 7 64-bit Ultimate English
•Windows Vista 32-bit Business English
•Windows Vista 32-bit Ultimate English
•Windows Server 2003 Enterprise Edition English
•Windows Server 2003 R2 Enterprise Edition English
•Windows Server 2003 Small Business Server R2 Premium Edition English
10Introduction
•Windows Server 2003 Small Business Server Premium Edition English
•Windows Server 2003 Windows Storage Server 32bit English
•Windows Server 2008 Standard Edition
•Windows Server 2008 Enterprise Edition
•Windows Server 2008 DataCenter Edition
•Windows XP Professional English
•Windows XP x64 Professional Client English
Supported Dell Client Computers
Table 1-3.
Latitude SeriesOptiPlex SeriesDell Precision Series
Latitude XT2
Latitude XT2 XFR
Latitude 2120
Latitude Z600
Latitude E5410
Latitude E5510OptiPlex XEDell Precision M6600
Latitude E5400OptiPlex 980Dell Precision M2400
Latitude E5420OptiPlex 780Dell Precision M6300
Latitude E5420mOptiPlex FX160Dell Precision M2300
Latitude E5520mOptiPlex 160Dell Precision M6400
Latitude E5520OptiPlex 960Dell Precision 390
Latitude E4310OptiPlex 760Dell Precision 690
Latitude E6320OptiPlex 360Dell Precision R5400
Latitude E6420 ATGDell Precision R5500
Latitude E6420 XFRDell Precision T7500
Latitude E6520Dell Precision T5400
Latitude E6510Dell Precision T5500
Latitude 2110Dell Precision T3500
OptiPlex 380Dell Precision M4500
OptiPlex 580Dell Precision M4300
OptiPlex 970Dell Precision M6500
OptiPlex 990Dell Precision M4400
OptiPlex 390Dell Precision M4600
Introduction11
Table 1-3.
Latitude SeriesOptiPlex SeriesDell Precision Series
Latitude XT3Dell Precision T1600
Latitude E6410Dell Precision T3400
Latitude E6410 ATGDell Precision T1500
Latitude E6400 XFRDell Precision T7400
Latitude E6220
Latitude 2100
Latitude 13
Latitude E5400
Latitude E5500
Latitude E4300
Latitude E6500
Latitude E4200
Latitude XT
Latitude E6400
Latitude E6400 ATG
Latitude D530
12Introduction
2
Using DCIP
Before you begin using DCIP for ConfigMgr, ensure that the target Dell
client systems are auto-discovered and present under All Systems on the
ConfigMgr console. For more information on auto-discover through
ConfigMgr, see the Microsoft TechNet article at
http://technet.microsoft.com/en-us/library/cc507089.aspx.
You can use DCIP for ConfigMgr to perform the following tasks:
•Create Dell Windows PE boot image
•Create Dell client driver packages
•Import Dell client packages
•Create a task sequence
•Reboot to PXE or USB custom action
See also:
Creating Dell Windows PE Boot Image
Creating Dell Client Driver Packages
Importing Dell Client Packages
Creating a Task Sequence
Reboot To PXE / USB Custom Action
Creating Dell Windows PE Boot Image
To create a Dell Windows PE boot image:
Go to
1
2
3
4
5
support.dell.com
Select your product, which should ideally be the client system you are
targeting.
Select your operating system.
In the
Category
Click
Download
Preinstallation Environment (WinPE)
field, select
against
Drivers & Downloads
Systems Management
Driver Pack for Microsoft Windows
option.
.
.
Using DCIP13
6
Download the
site at
support.dell.com
7
On the ConfigMgr console, go to
Management
8
Right-click
WinPE CAB package
The
Dell Client WinPE Boot Image Wizard
9
Select
Dell Deployment Boot Image (x00)
operating system architecture you want to select.
10
Under
Path to WinPE drivers cab file:
Windows PE driver
If a Dell Windows PE boot image already exists, a message is displayed
stating that the image exists and that it will be overwritten if you continue.
Click
OK
A progress bar displays the import status.
11
Click
Close
A
Dell Client Win7PE Boot Image(<CAB version) x86
created under
12
Right-click on
click
Manage Distribution Points
The
Manage Distribution Point Wizard
through the wizard to manage the distribution points.
Dell WinPE Driver CAB
.
Operating System Deployment
Boot Images Dell WinPE Import Package
.
CAB
file and click
to continue.
.
Boot Images
Dell Client Win7PE Boot Image(<CAB version) x86
.
file from the Dell Support
Site Database
, where 00 stand for the type of
click
Open
.
screen is displayed. Proceed
Computer
screen is displayed.
Browse
and select the Dell
.
boot image is
Import Dell
and
NOTE: The WinPE image needs to be distributed to the SMSPXEIMAGES$ in
addition to the regular distribution point. Without distributing to the
SMSPXEIMAGES$ the target client systems will not be able to load the WinPE
image.
You have successfully created a Dell Windows PE boot image. Proceed to
create Dell client driver packages.
Creating Dell Client Driver Packages
To create Dell client driver packages:
1
Download the operating system
14Using DCIP
CAB
file from
support.dell.com
.
2
On the ConfigMgr console, go to
ConfigMgrSite Database
Computer ManagementOperating System Deployment
Driver Packages
CAB Package
The
Dell Client Driver Import Wizard
3
Browse
and select the system driver
architecture for creating driver packages, and click
NOTE: On the Dell Client Driver Package Import wizard, if you select the XP
Driver CAB, a checkbox Create WinXP Storage Driver Packages is displayed.
It is recommended that you select this checkbox. This creates XP Storage
Driver Package under the Dell XP Storage Driver Packages folder under the
Driver Packages in ConfigMgr console.
•
For the
XP Driver CAB
Driver CAB
folder. In this case, leave the checkbox
Storage Driver Package
this step in the task sequence.
•
For Microsoft Windows XP operating systems, the
in the
Task Sequence Editor
during Microsoft Windows XP system deployment to avoid a continuous reboot
with the following error: 0x0000007B (INACCESSIBLE_BOOT_DEVICE). For more
information on the appropriate storage driver selection, see the Dell Tech Center
www.delltechcenter.com
site at
The
Dell Client Driver Import Wizard
packages are created and stored under the
Dell Client CAB Package Import Dell Client
.
screen is displayed.
CAB
and the operating system
Finish
, if there are no drivers within the
category, the
Import Drivers
step deselected. Select the
is enabled. Select the appropriate storage driver
step imports drivers within the
Select Mass Storage Driver
.
Storage
XP Driver Package
Storage Driver Package
progress is displayed. Driver
System CAB Driver Packages
.
folder according to the operating systems architecture selected. For
example, Vista
Driver Packages
system, architecture, and the version of the Vista driver
CAB
driver packages are stored under the
System CAB
folder with the relevant name specifying the operating
CAB
folder in the
Chipset
in the
Apply
and apply
option
file selected.
4
Click
Close
to exit the wizard.
NOTE: Importing of drivers may take a long time. During this period, the
progress bar may not be updated.
5
To update and manage distribution points for the driver packages you
imported, on the DCIP for ConfigMgr console, go to
Dell System CAB Driver Packages<
Dell driver pack name>.
Driver Packages
The driver packages window is displayed.
Using DCIP15
6
Right-click the newly imported driver packages, and update and manage
the distribution points.
You have successfully created a Dell client driver packages. Proceed to manage
and update distribution points.
Importing Dell Client Packages
You can import several client packages like CCTK and OMCI.
CCTK Self-Contained-Executable (SCE) file
CCTK SCE file allows you to:
NOTE: CCTK SCE files are only available in Dell Client Configuration Toolkit Version
2.0 and higher.
•customize your configurations
•export a customized configuration to apply the same settings on a target
client system
•export both supported and unsupported options
•customized your BIOS configuration
Importing CCTK
To import CCTK SCE packages:
1
On the DCIP for ConfigMgr console, go to
Management
2
Right click
3
Click
Browse
Software Distribution
Packages Dell Import Dell CCTK Package
and navigate to the location of the CCTK SCE file.
Site Database
Computer
NOTE: The CCTK SCE file is generated when CCTK is installed on the system.
For more information, see Dell Client Configuration Toolkit Version 2.0 User’s Guide on support.dell.com\manuals.
4
Click OK.
If a package already exists on the ConfigMgr, a message is displayed asking
if you would like to recreate or continue. If you select
process does not recreate the package, otherwise the package is dropped
from the ConfigMgr and repackaged with the new SCE file.
16Using DCIP
Continue
, the
NOTE: If the following error message is displayed: Invalid SCE file. Please
select another .exe to continue, repeat step 3.
5
Click
Close
.
After the process is complete, a new package is created.
NOTE: To see the details of the newly created package, browse to Packages
Dell Client Packages on the ConfigMgr console. The newly created package is
under the Dell Client packages node.
You can apply the SCE files on target systems after you distribute them.
Once the Wizard Complete you will have a SCE Software Package create
under Dell Client packages. You can associate these packages with their
task sequence for pre-OS deployment or use them as software package during
post-OS configuration.
Importing OMCI
To import OMCI:
1
Go to
support.dell.com
2
Select your product, which should ideally be the client system you are
targeting.
3
Select your operating system.
4
In the
Category
5
Click
Download
6
Download the application on the local drive of the system that runs the
field, select
against
ConfigMgr Site Server.
7
On the DCIP for ConfigMgr console, go to
Management
8
Right click
The
Dell OMCI Package Import Wizard
Software Distribution
Package s Dell Import Dell OMCI Package
Drivers & Downloads
Systems Management
.
.
OpenManage Client Instrumentation
Site Database
Computer
screen is displayed.
.
9
Under
Path to MSI file:
click
browse
navigate to the location where you
have downloaded the installer file to, select it and click
10
Click Ok.
A progress bar is displayed.
11
Click
Close
.
Open
.
Using DCIP17
The
OMCI
12
Right click
13
The
Manage Distribution Point Wizard
through the wizard to manage the distribution points.
package is installed under
OMCI
and click
Manage Distribution Points
Dell Client Packages
screen is displayed. Proceed
.
.
Managing and Updating Distribution Points
You should update the distribution points before creating a task sequence.
To update and manage distribution points:
client system is able to access the driver packages during an operating
system installation.
You have successfully updated and managed the distribution points for the
Dell client packages. Proceed to create a task sequence.
Client Custom Reboot Script
. The
Manage Distribution Point Wizard
Next
and proceed through the wizard to manage the distribution
Client Custom Reboot Script
Confirm Update Distribution Points
.
, two packages are available —
and
Client Custom Reboot Script
Client Custom Reboot Script
.
ConfigMgrSite Database
. Repeat step 3 and step 4 to ensure that the
ConfigMgrSite Database
Client
. For this use
.
and click
and click
screen is displayed. Click
Manage Distribution
is displayed.
Yes
to
Creating a Task Sequence
Task sequences are used to capture an operating system image, configure its
settings, and deploy the image on a set of Dell client systems. You can create a
task sequence in two ways:
18Using DCIP
•Create a Dell-specific task sequence, which has a set of pre-specified
actions, using the
Dell Client Deployment
template.
•Create a custom task sequence where you can add custom actions to the
task sequence.
Creating a Task Sequence Using the Dell Client Deployment Template
To create a task sequence using the Dell Client Deployment template:
1
Launch ConfigMgr by clicking
Center
Configuration Manager 2007Configuration Manager
Console
2
On the DCIP for ConfigMgr console, go to
Management
3
Right-click
. The ConfigMgr Console is displayed.
Operating System Deployment
Tas k Se que nce s
Create a Dell Client Deployment Template
The
Create Dell Client Deployment Task Sequence
4
Enter the name of the task sequence in
5
Under
Client Hardware Configuration,
you want to configure in this task sequence.
NOTE: If you select the Configure BIOS check box and a CCTK package has
been previously created, then a task sequence template is created while
configuring your system BIOS. The CCTK package is selected by default and
the command line to run the SCE on the target system is populated
automatically. However, if a CCTK package has not been created then a
message No CCTK package has been detected. Please import CCTK SCE to be
able to change BIOS configuration is displayed. You can still configure your
system BIOS but a package will not be selected.
If you do not select the Configure BIOS check box, the
BIOS
option is unavailable.
6
Under
Network (Admin) Account
name and password.
7
Under
Operating System Installation
installation type. The options are:
•Use an OS WIM image
•Scripted OS install
StartAll Programs Microsoft System
Site Database
Computer
.
, then
Bare Metal Client Deployment
.
window is displayed.
Task Sequence Name
field.
select the hardware items that
Configuring your System
, enter your domain admin account
, select the operating system
Using DCIP19
8
Select an operating system package from the
use
drop-down menu.
9
Select a
drop-down menu.
10
Click
You have successfully created a Dell-specific task sequence using the
This loads the custom action for your Dell client system deployment.
3
Click Ok to continue or
4
If you click OK, the
is displayed.
You can now make changes to the task sequence accordingly.
Cancel
to quit.
Create Client Deployment Task Sequence
.
window
Configuring your System BIOS
The Configure BIOS option is enabled on the task sequence after adding the
Dell Client Configuration. Ensure that CCTK version 2.0 or later is installed
on a the target system to create a BIOS Package.
NOTE: While configuring your BIOS, if more than one CCTK package exists then
the latest CCTK package is selected. The older packages are available under Dell
Client Packages, to select an older package click Browse and select the older
package while configuring the Task sequence.
Exporting the BIOS configuration file
Launch the CCTK standalone application. For more information,
see the Dell Client Configuration Toolkit Version 2.0 User’s Guide on support.dell.com\manuals.
Prerequisites for Exporting
The following are the prerequisites for exporting:
•The option must be configured.
•The
You can export the configuration in the following formats:
•
Apply Settings
Self-Contained Executable
Create Configuration
(.exe file).
A
Validation Password dialog box is displayed prompting the user to
provide a password. If you have configured the system or setup password in
the target system, type the same system or setup password in the
Val id a ti on Pas swo rd
optional.
check box of the option must be selected.
— Click
screen to export the configuration settings as a SCE
dialog box. This option to set the password is
Export Configuration.exe
on the
Using DCIP21
•
Report
read-only .html file. If you have configured the system or setup password in
the exporting file, see Password Protection Dialog box.
•
Configuration file
configuration settings as a .cctk or .ini file. If you have configured the
system or setup password in the exporting file, see Password Protection
Dialog box.
•
Shell script
shell script is generated at the same location where SCE file is exported
and contains the same configuration as that of the SCE file.
Exporting Options Without Setting Values
You can export certain options without specifying any values. The options are
asset and propowntag.
To exp ort asset and propowntag without specifying any values, select the
Apply Settings check box of the corresponding option and export.
Password Protection Dialog box
If you have configured the system or setup password in the exporting file
(configuration file or report), a password protection dialog box is displayed.
To export the file with the password as clear text, click Continue. To hide the
password and export, click Mask. If you have chosen to hide the password, in
the configuration (.cctk or .ini) file, the setuppwd is displayed as <password removed> indicating that password is hidden.
— Click
Export Report
— Click
— The shell script is used to configure a Linux system.The
to export the configuration settings as
Export Configuration
to export the
Applying SCE on the Target System
You can apply SCE on the target system in one of the following ways:
•Using the ConfigMgr application package. For more information, see
Importing CCTK.
Or
•Using the CCTK standalone application. For more information, see Using
the Standalone Application.
22Using DCIP
Using the Standalone Application
You can apply SCE on the target system using the CCTK standalone
application in one of the following ways:
•Double-click the SCE, or
•From the command prompt, navigate to the directory where SCE is
located, and type
the name of the SCE file.
Example:
C:\Windows\CCTK\SCE>"<filename>"
SCE silently installs the settings on the target system. When the installation
completes, SCE generates a text file with the same name at the same
location. The text file contains all the applied options and the status of
execution for the SCE file.
If you have configured a setup or system password on the target system, and
while exporting SCE if you have not provided the same password in the
Validation Password dialog box (for more information, see
BIOS configuration file
), SCE cannot be applied on the target system.
Exporting the
However, while applying SCE from the command prompt, you can provide
the setup or system password of the target system.
NOTE: Before you begin this task, ensure that you have the required operating
system image file (.wim file) under the Operating System Images tree in ConfigMgr.
To apply operating system image:
1
From the left-hand side of the
Operating System
2
You can choose from the following options:
, click
Tas k Se que nce Edi tor
, under
Apply Operating System Image.
Deploy
•Apply operating system from a captured image
Using DCIP23
•Apply operating system from an original installation source
3
After selecting from the above options, click Ok.
You have successfully applied an operating system image.
Apply Driver Packages
To apply driver packages:
1
From the left hand side of the
Operating System
2
Browse
and select the
click
Dell Client Driver Packages
packages available in the
3
Select a package for Dell client system and click
Tas k Se que nce Edi tor
Apply Driver Package
Dell Deployment Pack
, under
.
. The list of driver
is displayed.
Apply
.
Deploy
You have successfully added drivers.
Advertising a Task Sequence
After saving the task sequence, assign it to the collection of systems by
advertising it.
To advertise a task sequence:
1
Right-click on the task sequence and select
Advertisement Wizard
2
Follow the steps in the wizard to advertise the task sequence.
window is displayed.
For more information on advertising a task sequence, see the
ConfigMgr
Online Help.
Advertise
. The
New
NOTE: In the New Advertisement Wizard, ensure that you select the Make
this task sequence available to boot media and Preboot Execution
Environment (PXE) option.
Best Practices For Advertising a Task Sequence
The following settings are recommendations for advertising a task sequence.
Always configure advertisements with the following settings when using PXE:
•General: Make this task sequence available to boot media and PXE
•General: Browse to select the collection of the target system
•Schedule:
24Using DCIP
Mandatory assignment
: “As soon as possible”
•Distribution Points: Access content directly from a distribution point
when needed by the running task sequence
•Interaction: Show task sequence progress
Always configure Windows PE boot images with the following settings:
•Windows PE: Enable command support (testing only)
Deploying a Task Sequence
When the task sequence is ready, use any of the following methods to deploy
the task sequence you have created:
•Deploy using a CD
•Deploy using a USB
•Deploy using PXE
For more information on how to deploy a task sequence using the above
methods, see the ConfigMgr Online Help.
Importing System Information
Use the Import Computer Information when you right click on
Computer Association option to import new client system information into
the ConfigMgr database. This allows you to deploy an operating system to a
new client system.
Computer Association
A computer association organizes the migration of user state and
settings from a reference client system to a client destination system.
The reference client system is an existing client system that is managed by
ConfigMgr 2007 SP1. This system contains, state and settings of your system
that will be migrated to the specified destination client system.
The Computer Association node displays a list of the computer associations
that have been created. It also displays specific actions that can be run for
that computer association when you select a computer association from the
Computer Association results pane.
To import computer information:
Using DCIP25
1
On the DCIP for ConfigMgr console, under
Deployment
Information
2
The
Select Source
, right-click
. The
Computer AssociationImport Computer
Import Computer Information Wizard
window displays the following options:
Operating System
is displayed.
•Import computers using a file,
•Import single computer
3
Select Import Computers Using a File or Import single computer based on
your requirement
Import Computers Using a File
To import computers using a database file containing the details of the
computers in your network:
1
On the
2
Click
3
Click
The
4
Click
5
From the list of systems displayed, select the systems your want to
Select Source
Browse
to browse to the location of the database file and open it.
Next
.
Data Preview
Next
.
window, select
Import single computer.
Click
lists the details of the systems in the database file.
associate.
6
Click
Finish
.
Next
.
Import single computer
To import computers using a file:
1
On the
2
Specify information relating to the computer you are importing in the
Select Source
window, select
Import single computer.
following fields:
•Computer name
•MAC address (12 hex characters)
•SMBIOS GUID (32 hex characters) - (optional)
3
Click
Next
.
NOTE: Ensure that the computer name you enter starts with a letter.
Otherwise, the deployment will fail.
26Using DCIP
Click
Next
.
4
The
Data Preview
information you have entered. Click
5
The
Choose Target Collection
window opens where you can verify the configuration
Next
.
window opens. The following options
are available:
•Add new computers only to the All Systems collection
•Add computers to the following location
6
To add the computer to the all systems collection:
a
On the
only to the All Systems
b
Click
Choose Target Collection
collection.
Next
.The
Summary
window with details of the imported system
window, select
setting is displayed.
c
Click
Finish
to apply settings.
7
To add the computer to a specific location:
a
On the
to the following location
b
Browse
c
Click
Choose Target Collection
window, select the
option.
to the location of the computer collection you want to add to.
Next
.The
Summary
window with details of the imported system
setting is displayed.
d
Click
Finish
to apply settings.
Add new computers
Add computers
Reboot To PXE / USB Custom Action
Windows PE may have an issue when you add a system hardware
configuration action to a task sequence. Windows PE does not correctly
recognize any newly-created disk partitions or any significant change to the
disk structure created after the initial Windows PE boot. This causes the task
sequence to fail during any task that writes data to the disk (including the
standard ConfigMgr reboot task).
To resolve this issue, you must insert custom reboot actions after you create
and partition a disk. If you are using
instead of boot media, you must reset the PXE advertisement in order to
reboot back into PXE.
You can insert the
Reboot to PXE/USB Custom Action
in one of the following ways:
Pre-boot eXecution Environment (
into a task sequence
Using DCIP27
PXE)
•Create a task sequence using the
Reboot to PXE/USB Custom Action
•Edit a task sequence for
created automatically. For more information, see “Editing a Task Sequence."
•Click
For more information on
Administrator Guide in the the Installation Directory.
AddDell DeploymentReboot to PXE/USB
Reboot to PXE/USB Custom Action
Reboot to PXE/USB Custom Action
Reboot to PXE/USB Custom Action,
Dell Client Deployment
to be created automatically.
to create the
manually.
template for
see the
to be
28Using DCIP
Using DCIP29
30Using DCIP
3
Dell Warranty Information Utility
Overview
The Dell Warranty Info Tool helps to retrieve the Dell Warranty Information
for a list of systems. The systems are specified with their service tags.
You can use DCIP Warranty Information Utility to perform the following
tasks:
•Generate Reports
•Copy CSV results containing warranty information to a database
•Export service-tags from ConfigMgr database to a CSV File
See also:
Generating Reports
Copying CSV Results to a Database
Exporting Service-Tags From ConfigMgr to a CSV File
Configuring the Warranty Utility
Before you run the Warranty utility, you must configure certain parameters to
gather the warranty information. The parameters are:
1
Proxy User Name of the server (if set).
2
Proxy Password of the server (if set).
3
Proxy domain (if set).
4
Proxy server address (if set).
NOTE: Proxy server address can be entered as
http://proxyserver<:portnumber>/ where the port number is optional.
5
Connection string for the ConfigMgr inventory
6
WMI Namespace
7
Desired output format -
and
WMI computer
.csv, .xml
to connect for WQL
, or database (
Dell Warranty Information Utility31
.rdl
)
NOTE: These parameters can either be configured in a file or in a registry
using the setup_config command. For more information on configuring
registry, see
8
Input the service tags to the utility. You can input the service tags through:
Configuring the Registry
.
•A Comma-separated values (CSV) file containing service tags, one
service tag per line. Run the command
DellWarrantyInfo.exe get_info MyTags.csv
in the warranty utility to get warranty information of the service tags
listed in the .csv file named MyTags.csv.
•Service tags contained in the ConfigMgr inventory.
Run the command
internal_sccm
DellWarrantyInfo.exe get_info
in the warranty utility to get warranty information
of service tags listed in the ConfigMgr database.
Configuring the Registry
To configure the warranty utility in the registry, enter the following command
DellWarrantyInfo.exe setup_config in the warranty
utitlity.Enter all the configuration information required to setup the
warranty utility, for more information, see
NOTE: If a certain setup parameters like Proxy Domain needs to be skipped, simply
press enter key without any input.
The configuration parameters are stored in the HKEY_CURRENT_USER
\Software\Dell\DellClientIntegrationPack\Warranty registry location.
Configuring the Warranty Utility
.
NOTE: The password is stored in an encrypted form.
Configuring A Database File
To configure the warranty utility through a database file, enter the following
command
DellWarrantyInfo.exe setup_config config_file=
admin.cfg (where admin.cfg is the name of your configuration file).
Enter all the configuration information required to setup the warranty utility,
for more information, see
32Dell Warranty Information Utility
Configuring the Warranty Utility
.
To get warranty information of service tags that are present in the ConfigMgr
inventory by using configuration options present in admin.cfg, run the
following command:
NOTE: For the get_info command, if the config file is not specified, the
configuration options from the registry are used.
Generating Reports
There are three report templates stored in the same location where you have
installed the Dell Warranty utility.: ActiveSystem.rdl, AllSystems.rdl, and SystemsWithWarranty.rdl. These reports have the following placeholders for
the database connection string:
<!--PROVIDER-->, <!--CONNECTION_STRING-->, and
<!--INTEGRATED_SECURITY-->.
NOTE: The templates are in rdl (Report Definition Language) format. To view or edit
the file on systems running Windows 2008 R2 server install Microsoft Report
Viewer.
NOTE: The SRS Templates generated by the Dell Warranty Module are compatible
with the Reportbuilder v2.0 or greater.
You can use the generate_srs_templates command to generate the
report definition files using the report templates. The placeholders are
substituted with the database connection string specified by you either in the
registry or the config file.
•To run the report by using a database connection string from the registry,
enter the command
generate_reports
•To run the report by using the database connection string from a .cfg file
enter the command
generate_reports config_file=admin.cfg
You can view these reports using the reporting services of the ConfigMgr or
using the Report Builder services. For more information, see
Services of the ConfigMgr
DellWarrantyInfo.exe
.
DellWarrantyInfo.exe
.
Reporting
.
Dell Warranty Information Utility33
Reporting Services of the ConfigMgr
To use the reporting services of ConfigMgr:
1
Install SQL Server Reporting Services (SSRS).
a
On the ConfigMgr console, go to
Management
b
Right-click on your target system and click
c
Select
system on the internet
(site_name)Site Settings Site Systems.
Specify a fully qualified domain name (FQDN) for this site
check box and enter your domain name under
Site Database Site
New Roles
.
it.
d
Click
Next
.
e
Under
Available roles:
Next
.
f
Under
Report folder:
g
On the
h
The
Click
2
Navigate to reports using http://<servername>/reports.
3
Import RDL Template provided with the plug-in. Provide a suitable name
Summary
New Role Wizard Completed Successfully
Close
.
, select the
Reporting point
check box and click
, enter your reporting folder name and click
tab click
Next
.
screen is displayed.
to the report.
4
Assuming you have ran the Warranty Service on your ConfigMgr, the
DellWarrantyInformation
5
When you run the reports the Custom Reports provided by Dell are
table is created on the ConfigMgr database.
generated.
Next
.
Viewing Reports Using Report Builder
To view reports using report builder:
1
Download
2
Open the report using this installed Report Builder and Run the report to
SQL Server Report Builder version 2.0
or higher.
view the data.
34Dell Warranty Information Utility
Copying CSV Results to a Database
You may run the Dell Warranty utility to get output results in a .CSV format
and then later copy the .CSV result file to a database. This can be achieved
using csv_to_db command. The connection string specified in the config
file or registry is used.
•To copy contents of a
registry config parameters, enter the following command
Exporting Service-Tags From ConfigMgr to a CSV
File
In order to retrieve a list of service tags present in the ConfigMgr inventory
and export them to a .csv file, you can use export_svc_tags command
can be used.
NOTE: The WMI parameters specified in the config file or registry are used.
•To retrieve the service tags present in ConfigMgr inventory from
file using registry config parameters, enter the following command
DellWarrantyInfo.exe export_svc_tags tags.csv
•To retrieve the service tags present in ConfigMgr inventory from the
tags.csv
file file using config parameters in
following command
tags.csv config_file=admin.cfg
DellWarrantyInfo.exe export_svc_tags
admin.cfg
file, enter the
tags.csv
Disabling Logging
By default, logs for Dell Warranty Information tool are generated under
%USERPROFILE%\AppData\Local\Dell\ClientIntegrationPack\log\ folder.
You can turn off the logging by setting the registry value DisableLogging to 1
under HKEY_CURRENT_USER\Software\Dell\DellClientIntegrationPack\Warranty.
Dell Warranty Information Utility35
36Dell Warranty Information Utility
4
Intel vPro OOB Management
Extensions
Overview
Intel vPro OOB management extensions provides an out-of-band
management solution through a stand-alone application on the system
running on Dell Client Integration Pack (DCIP) for ConfigMgr. The
application allows you to remotely manage client systems regardless of the
state, the system power or operating system is in.
You can use Dell Client Integration Pack for ConfigMgr with the Intel vPro
OOB management utility to perform the following tasks:
•USB Provisioning
•Perform client configuration like
–Configuring power profile
–Configuring the boot order
–Configuring the BIOS settings
–Configuring BIOS passwords
•Perform remote operations and KVM sessions
•Generate reports
•Enable client logs across the network and collect hardware inventory
•Monitor task progress and details
See also:
USB Provisioning
Client Configuration
Operations
Generating Reports
Application Preferences
Intel vPro OOB Management Extensions37
Tas k Qu eue
Software Prerequisites
Before setting up Intel vPro OOB on your computer:
•Prepare Active Directory Domain Services for out-of-band management.
For more information see the Microsoft TechNet article at
•Provision your system running DCIP for ConfigMgr to run Intel Active
Management Technology (AMT). For more information on AMT
provisioning see the Microsoft TechNet article at
•Export the provisioning certificate hash to all the AMT client systems you
want to manage through your system running DCIP for ConfigMgr. For
more information, see USB Provisioning.
•For In-Band shutdown to work correctly the system running DCIP for
ConfigMgr needs to have Windows Powershell version 2.0 installed and
WinRM configured. For more information on configuring WinRM, see
Configuring WinRM.
•When using DCIP for ConfigMgr out-of-band provisioning for clients,
verify the Microsoft System Center Configuration Manager (SCCM)
agent is not installed on those clients. If the SCCM agent has been
installed on client systems and the agent has been detected by SCCM,
then you can use SCCM in-band provisioning with those client systems.
.
NOTE: You can perform the check by using the SCCM console to view the
client column of SCCM collections.
38Intel vPro OOB Management Extensions
Launching the AMT Plug-in
You can launch the AMT plug-in by:
•Clicking
Client Integration Pack for Microsoft ConfigMgr
Or
•From within ConfigMgr:
–Select
Start
choose
or
All ProgramsDell
Computer Management
Dell - Intel AMT Plugin
and then click the
from the drop down list.
Dell AMT Plugin.
Action
menu and
–Right click
Computer Management
Dell - Intel AMT Plugin
.
Database and Password Configuration
The Dell Intel AMT Plug-in Database and Password Configuration window
is displayed the first time you launch the Dell AMT Plugin. You can
configure the following settings:
1
Retrieve and select the available
down list.
2
Select the type of SQL Server Security (Integrated or Username /
Password) you want to set.
3
Retrieve and select the available
list.
4
Configure your
5
Configure your
Windows Account
AMT ME Account
SCCM SQL Server
SCCM Database
settings.
settings.
from the drop-down
option from drop-
USB Provisioning
Before Intel Active Management Technology-based client systems can be
managed out-of-band by DCIP for ConfigMgr, you must provision them for
AMT. For more information on AMT Provisioning see, the Microsoft KB
article at http://technet.microsoft.com/en-us/library/cc161806.aspx.
Intel vPro OOB Management Extensions39
Provisioning Using your USB Device
Deploying Intel vPro OOB management platforms using remote
configuration requires a digital provisioning certificate to be procured by the
client systems.
To export your certificate hash to the client systems using a USB storage
device:
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
The
USB Provisioning
3
Enter your Management Engine (ME) password and then enter a
Password
NOTE: The AMT password must contain a minimum of eight characters made
up of uppercase, lowercase, numbers, and non-alphanumeric characters
excluding
4
Browse and point to the location of the USB storage device.
5
The application will detect and select the file format of your USB storage
device.
NOTE: For iAMT5 or older select the Format Drive check box and format the
USB storage device to a FAT 16 file format.
6
Select the
if you want to allow the administrator to override the client system's user
consent policy.
7
Depending on the version of AMT you are targeting select the
Ver si on
from the drop-down list.
Home
screen, click
USB Provisioning
.
window is displayed.
for AMT and confirm it.
:, _, and ".
Enable remote configuration of user consent policy
New
check box
Setup File
NOTE: For AMT version 5 or older use setup file version 2 or 2.1, for AMT
version 6 to 7 use setup file version 3 or 4.
8
Select the type of
Hash Algorithm
depending of the type of Setup File
Version you have selected.
NOTE: The Hash Algorithm SHA256 and SHA384 are available for setup file
version 3 or higher only.
9
Select the
immediately)
OOB Provisioning (enabling will start hello packets
check box if you want to send hello packets immediately.
40Intel vPro OOB Management Extensions
10
Browse and select the
systems for iAMT provisioning.
11
Enter a suitable friendly name for the certificate file.
12
Click
Export...
.
Certificate File
you want to apply on your client
Client Configuration
Allows you to control various AMT settings on the target client systems.
Configuring Power Profile
You can control various functions like Wake-up On Lan (WOL), ON, OFF
after power loss, and so on, in the different power states (S0 to S5) of your
client system.
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
3
On the
4
Select the power package for your desktop and/or mobile computers.
Click
The
5
Search for client systems to which you want to apply the power packages.
6
Select the client systems to which you want to install the power packages
on and click
7
Click
The
Client Configuration
Next
Select Clients
Next
Schedule Task
.
.
Home
tab is displayed.
Add
.
tab is displayed.
screen, click
window, click
Client Configuration
Power Profile
.
.
8
You can either choose to apply the package immediately or schedule it to
run at a later time.
9
Provide a brief description of the package you are applying and click
Finish
.
10
Depending on your schedule, select one of the following options:
•
Run now
Running
— the package is immediately applied and displays the
status in the
Tas k Qu eue
Intel vPro OOB Management Extensions41
.
NOTE: If your client systems are not connected to the network, you have to
run the task again.
•Run At —
NOTE: You can launch the Task Queue to view the list of completed and
pending tasks.
the package is queued in the
Tas k Qu eue
.
Configuring the Boot Order
Change or configure the boot order on the targeted client-systems.
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
3
On the
The
4
The table on the left side lists all the possible Boot devices. Change the
Client Configuration
Boot Order
boot order by:
•Moving the boot devices up or down the order by clicking on the
or
Down
•Disabling boot devices by clicking on the on/off toggle switch.
5
Select one of the configuration options:
•
One-time configuration
one reboot cycle.
•
Permanent configuration
6
If you want the Task execution to continue to subsequent clients systems
when an error occurs, select the
Task execution will stop on the first client system where an error is
encountered.
Home
screen, click
Client Configuration
window, click
Boot Order
tab is displayed.
arrows at the bottom of the table.
— the boot-order will be changed for only
— the boot-order is permanently changed.
Continue on error
.
.
check box. Otherwise,
Up
NOTE: The Re-Run task feature will allow you to pick up processing a Task
that is partially complete.
7
If you want to reboot the client systems after applying changes select the
Reboot after applying changes
8
Click
Next
.
Select Clients
The
tab is opened.
check box.
42Intel vPro OOB Management Extensions
9
Search for client systems you want to apply the
10
Select the client systems you want to apply the
click
Add
.
11
Click
Next
.
The
Schedule Task
12
You can either choose to apply the changes immediately or schedule it to
tab is displayed.
Boot Order
Boot Order
changes.
changes and
run at a later time.
13
Provide a brief description of the changes you are applying and click
Finish
.
14
Depending on your schedule, select one of the following options:
•
Run now
displays the
NOTE: If your client systems are not connected to the network, you have to
run the task again.
•Run At —
NOTE: You can launch the Task Queue to view the list of completed and
pending tasks.
— the
Running
the
Boot Order
status in the
Boot Order
changes are immediately applied and
Tas k Q ue u e
changes are queued in the
.
Tas k Qu eue
Configuring BIOS Settings
This feature allows you to configure and change the BIOS settings.
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
3
On the
The
BIOS Settings
Client Configuration
Home
screen click
tab is displayed.
Client Configuration
window, click
BIOS Settings
.
.
.
4
Make the changes you want to the BIOS settings for your client-systems
and select the check box under
5
If you want the Task execution to continue to subsequent clients systems
when an error occurs, select the
Apply
.
Continue on error
check box. Otherwise,
Task execution will stop on the first client system where an error is
encountered.
Intel vPro OOB Management Extensions43
6
Select the
Reboot after applying changes
check box if you want to reboot
after applying changes.
7
You can load predetermined/default BIOS values through the
BIOS
Attribute Config Source:
•BIOSAttributeConfig.xml — load BIOS settings from the
BIOSAttributeConfig.xml file contained in the install folder.
•Defaults — load the factory settings.
8
Click
Next
.
The
Select Clients
9
Search for the client-systems you want to update the BIOS attributes.
10
Select the client-systems you want to update the BIOS attributes and click
Add
.
11
Click
Next
.
The
Schedule Task
12
You can either choose to apply the changes immediately or schedule it to
tab is displayed.
tab is displayed.
run at a later time.
13
Provide a brief description of the BIOS attribute changes you are applying
and click
14
Depending on your schedule, select one of the following options:
•
Finish
.
Run now
— the BIOS setting configuration is immediately applied
and displays the
Running
status in the
Tas k Q ue u e
.
NOTE: If your client systems are not connected to the network, you have to
run the task again.
•Run At —
Queue
NOTE: You can launch the Task Queue to view the list of completed and
pending tasks.
the BIOS setting configuration is queued in the
.
Ta s k
Setting BIOS Passwords
The feature allows you to set passwords, clear passwords, or change the length
requirements for your client system's Administrator and/or System passwords.
44Intel vPro OOB Management Extensions
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
3
On the
The
4
Select one of the following options:
•
•
•
Client Configuration
BIOS Passwords
Clear
NOTE: To clear the Admin password you have to clear the System password
as well.
Set
— enter and confirm the
NOTE: Client systems have to reboot after setting the Admin or System
passwords.
Length
Admin
5
If you want the Task execution to continue to subsequent clients systems
when an error occurs, select the
Home
screen click
Client Configuration
window, click
BIOS Passwords
.
.
tab is displayed.
— clear either the
Admin
Admin
or
System
or
System
password.
password.
— you can specify the minimum and maximum length for the
and
System
password.
Continue on error
check box. Otherwise,
Task execution will stop on the first client system where an error is
encountered
6
If you want to reboot after applying changes select the
applying changes
7
Click
Next
The
Select Clients
check box.
.
tab is displayed.
Reboot after
8
Search for the list of client systems that you want to change the BIOS
passwords.
9
Select the client systems you want to change the BIOS passwords and click
Add
.
10
Click
Next
.
The
Schedule Task
11
You can either choose to apply the password changes immediately or
tab is displayed.
schedule it to run at a later time.
12
Provide a brief description of the changes your are applying and click
Finish
.
Intel vPro OOB Management Extensions45
13
Depending on your schedule, select one of the following options:
•
Run now
and displays the
NOTE: If your client systems are not connected to the network, you have to
run the task again.
•Run At —
Queue
NOTE: You can launch the Task Queue to view the list of completed and
pending tasks.
— the BIOS password configuration is immediately applied
Running
the BIOS password configuration is queued in the
.
status in the
Tas k Q ue u e
.
Ta s k
Operations
This features allows you to cold and warm reboot your client-systems and
setup KVM sessions
Performing Power Management
To Reboot and Shutdown your remote client-systems:
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
3
On the
The
Power Management
Operation
Home
screen click
window, click
Operations
Power Management
tab is displayed.
.
.
4
Select the power control option you want to on the client-systems from the
drop-down list.
5
Click
Next
.
The
Select Clients
6
Search for the client-systems you want apply the Power Management
changes.
7
Select the client-systems you want to apply the Power Management
changes and click
8
Click
Next
.
The
Schedule Task
46Intel vPro OOB Management Extensions
tab is displayed.
Add
.
tab is displayed.
9
You can either choose to apply the task immediately or schedule it to run
at a later time.
10
Provide a brief description of the task you are applying and click
11
Depending on your schedule, select one of the following options:
•
Run now
and displays the
NOTE: If your client systems are not connected to the network, you have to
run the task again.
•Run At —
Queue
NOTE: You can launch the Task Queue to view the list of completed and
pending tasks.
— the power management changes are immediately applied
Running
the power management changes are queued in the
.
status in the
Tas k Qu eue
.
Establishing KVM Sessions
To establish KVM sessions with remote client systems:
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
3
On the
The
KVM Connect
Operation
Home
screen click
window, click
tab is displayed.
Operations
KVM Connect
.
.
Finish
Ta s k
.
4
Search for the list of client systems on which you want establish KVM
sessions.
5
Select the client system on which you want to start the KVM session and
click
Start
.
Generating Reports
This feature allows you to generate and view OOB Manageability,
Provisioning, Battery Health of notebook client-systems, and Hardware
Inventory reports.
1
On the Dell Client Integration Pack’s
2
On the
Welco me
screen you can generate the following reports:
Intel vPro OOB Management Extensions47
Home
screen click
Reports
.
•
OOB Manageability
configuration for client systems.
•
Provisioning
in the network.
•
Battery Health
client systems on the network.
•
Hardware Inventory
client systems on the network.
3
After selecting the type of report you want, you can perform one of the
following actions:
•
Schedule
•
Retrieve
— view the provisioning status of all the client systems
— for more information, see Scheduling Reports.
— for more information, see Retrieving Reports.
— you can see the AMT Management Engine
— view the battery health of all the AMT enabled
— collect the inventory information of all the
Scheduling Reports
Generate reports from all the active client systems on the network.
To schedule a report:
1
Click
Schedule
The
Select Clients
2
Search for the list of client systems you want to view the reports on.
3
Select the client systems you want to view the reports and click
4
Click
Next
5
The
Schedule Report
6
You can either choose to apply the Task immediately or schedule it to run
at a later time.
7
Provide a brief description of the Task you are applying and click
.
tab is displayed.
.
tab is displayed.
Add
Finish
.
.
NOTE: Schedule reports creates a task that populates data about client systems.
Retrieving Reports
View existing reports. To retrieve a report:
1
Click
Retrieve
The
Select Clients
48Intel vPro OOB Management Extensions
.
tab is displayed.
2
Search for the list of client systems you want to view the reports on.
3
Select the client systems you want to view the reports. Click
4
Click
Next
.
5
The
Retrieve Report
6
Print, Copy
NOTE: The report is exported as a .xlsx file.
NOTE: Retrieving reports requests a report for whatever data has been collected
by the scheduled reports.
, or
tab is displayed.
Export
the report.
Add
.
Application Preferences
On this screen you can configure and set your preferences for different
components of the application like:
•Data Base(DB) and Passwords
•KVM Setup
•Logging
•Task Queue
DB and Passwords
You can configure where the task requests, and configuration data are stored.
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
3
On the
The
DB & Passwords
Welco me
Home
screen, click
screen, click
tab is displayed.
Preferences
DB & Passwords.
.
4
You can configure the following settings:
•Retrieve and select the available
drop-down list.
•Select the type of SQL Server Security (Integrated or Username /
Password) you want to set.
•Configure your
•Configure your
Windows Account
AMT ME Account
Intel vPro OOB Management Extensions49
SCCM SQL Server
settings.
settings.
option from
5
Click
Save
and
Finish.
KVM Setup
This feature allows you to configure and setup your Keyboard, Video, and
Monitor (KVM) sessions.
NOTE: Before a remote KVM session can be established, KVM must be enabled
through the Intel Management Engine BIOS Extension (MEBx) interface.
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
3
On the
The
4
Select the
the start of the KVM session.
5
If you want the user to provide consent, select the
box.
6
Set the time-out through the
7
Set the time frame for the KVM session to time-out after a period of
inactivity using the
8
Click
Client Configuration
KVM Setup
Finish
Home
screen, click
window, click
tab is displayed.
Default Video Screen,
User Consent Timeout
Session Timeout.
.
Client Configuration
KVM Setup
that is the screen you want to connect at
.
.
User Consent
.
check
Logging
Set your preferences for the type of logs you want to be captured by DCIP.
1
Launch the AMT plug-in by clicking
Client Integration Pack for Microsoft ConfigMgr
2
On the DCIP’s
3
On the
The
4
Select one of the following type of Logs:
•
•
50Intel vPro OOB Management Extensions
Welco me
Logging
None
Normal
is the recommended setting.
Home
screen, click
screen, click
screen is displayed.
— no logs are captured.
— typical logging for client systems operating normally. This
Preferences
Logging
Start
.
All ProgramsDell
Dell AMT Plugin.
.
•
Debug
— detailed logging for troubleshooting unexpected issues.
5
Click
Browse
to choose the location where your log files are created.
6
To view existing logs click
7
Click
Save
and
Finish
Open Containing Folder
.
Task Queue
This feature allows you to limit the number of task requests saved and
displayed in the Task Queue window.
NOTE:
1
Launch the AMT plug-in. For more information, see Launching the AMT
Plug-in.
2
On the DCIP’s
3
On the
The
4
Set the
database (1-500).
5
To have your
Refresh the task list automatically
Welco me
Tas k Qu eue
Tas k H is to ry L im it
NOTE: The older completed tasks will be automatically deleted from the
database as new tasks are created.
Home
screen, click
screen, click
tab is displayed.
Tas k Q ue u e
Preferences
Tas k Qu eue
to the number of tasks you wish to retain in the
automatically refresh every 15 seconds, select the
check box.
.
.
NOTE: To reduce database activity, deselect the Refresh the task list
automatically box and click Refresh on the Task Queue to update the Task list.
Task Queue
The Task Qu eu e window allows you to review scheduled and completed tasks.
You can also click:
•
View
— to get detailed information on an individual task in the task
queue. Click
•
Refresh
Export
to export the information to an excel file.
— to refresh the task queue.
Intel vPro OOB Management Extensions51
•
Re-Run
— to re-run an existing task which has failed on client systems
while skipping those client systems on which the task has run successfully.
If a Task was completed without any errors, then
Re-Run
will restart all
client systems in the Task.
•
Retrieve
— executes the Retrieve (instead of the Schedule) path of a
report task.
•
Edit
— edit tasks that are pending (waiting to be run). Tasks will be placed
on
Hold
while editing is underway.
•
Clone
— clone pending, completed, and canceled tasks.
•
Cancel
— cancel tasks that are not yet
Completed
.
Configuring WinRM
NOTE: The client systems firewall have to be configured to accept WinRM
commands.
On client system, if WinRm has not been configured type the following
command on an administrative command prompt.
1
Enter
winrm quickconfig
2
Press y to continue if prompted
3winrm set winrm/config/client @{AllowUnencrypted=
"true"}
4winrm set winrm/config/client/auth @{Digest=
"true"}
5winrm set winrm/config/client @{TrustedHosts=
"MANAGEMENT_SERVER_IP_ADDRESS"}
The WinRM is configured.
.
Do you want to configure winrm?
52Intel vPro OOB Management Extensions
Intel vPro OOB Management Extensions53
54Intel vPro OOB Management Extensions
5
Troubleshooting
This section contains troubleshooting information for the Dell Client
Integration Pack for Microsoft System Center Configuration Manager (DCIP
for ConfigMgr).
Authenticode Signature
If authenticode signature takes longer than usual to start because .Net is
searching for the signature, follow the steps mentioned in
support.microsoft.com/kb/936707/.
Windows XP Installation Fails
Installation of Windows XP operating system will fail if the mass storage
driver to be installed is not selected in the task Sequence. To do this in the
Apply Driver Packages step ensure that you select the Mass Storage Driver
that is required for the operating system installation.
KVM Over Wireless
Anytime the user selects To ol s Link Preference OS owns Wireless,
control of the wireless link is transferred from the Intel Management Engine
to the operating system. (ME gains control of the wireless link anytime a
shutdown or reboot command is selected from Tools Power Control.)
Whenever ME is given control of the wireless link (Link Preference), a
timeout value is supplied that indicates how long ME is to maintain control
of the wireless link, after which, control is given back to the OS. For example,
a user selects Reboot To OS to reboot the client operating system.
In order to maintain the KVM link, ME is first given control of the wireless
link. The timeout is set by default to 10 miniutes to provide ample time for
the system to complete the reboot process. ME will maintain control even
after the OS has rebooted if the reboot completes in under 10 minutes. To
give control back to the OS immediately, the user must select ToolsLink PreferenceOS owns Wireless. In that case, the KVM connection will be
Troubleshooting55
lost during the transfer process. To re-establish the connection, the user must
select ConnectionStart. Also note that when control of the wireless link is
automatically reverted back as a result of the Link Preference Timeout
expiring, there is no loss of connectivity. There are individual timeout values
for the each shutdown/reboot operation (defined in KVMView app.config
settings) that can be configured externally:
Hardware Inventory Report Memory Speed is
reported as Zero
This is a DMTF issue where memory speed is defined in seconds. SCCM
Resource Explorer today reports this as 0.
Max Password Length Change
Some systems BIOS do not support reducing the Maximum password length
down from 32. This is known issue being worked on at the time of release of
the product.
KVM Power Control - Boot to OS in S3
If after a KVM connection is established, the AMT client enters power state
S3 or S4, the KVM connection is lost within 30 seconds of entering the sleep
state. (This occurs in both wired and wireless environments.) In such a case,
the administrator will need to restart the connection (ConnectionStart),
before issuing a reboot command (OS, BIOS, Diagnostics, IDE-R).
56Troubleshooting
Troubleshooting57
58Troubleshooting
6
Related Reference
In addition to this guide, there are other product guides you should have
for reference. You can find the following guides on the Dell Support website
at support.dell.com/manuals.
•The
•The
•The
For more information on Microsoft System Center Configuration Manager
(ConfigMgr), its installation, or features and functionalities. See the
Microsoft TechNet site at technet.microsoft.com for details on ConfigMgr.
Obtaining Technical Assistance
If at any time you do not understand a procedure in this guide, or if your
product does not perform as expected, there are different types of help
available. For more information, see “Getting Help” in your system’s
Hardware Owner’s Manual.
Dell Client Configuration Toolkit User's Guide
installation and use of the client configuration toolkit (CCTK) to
configure various BIOS features for Dell business client platforms.