Jamie Glendinning [email protected] ENGL Imaging Toolkit 6 Managing your drivers using...

Jamie [email protected]

ENGL Imaging Toolkit™ 6Managing your drivers using Build Console

Copyright © Expert Networking Group Limited2

Agenda

Introduction

Zdrivers

Build Console

Import driver scans

Download drivers

Creating driver images

Files and folders

Troubleshooting driver issues

Known issues


Introduction


Introduction

Level Intermediate

Duration 30 minutes

Assumptions An understanding of ENGL build process


Zdrivers


Zdrivers Imaging Toolkit 6

Zdrivers is a standalone utility that performs a hardware inventory scan on the local machine and outputs the results to an XML file that can be imported into Build Console.

Advantages:

Hardware information is valid for all supported OS’s

Drivers are downloaded via build console from the manufacturer's website

Drivers are based on original vendor packages and are digitally signed

One location to store all driver information (Build Console)

Driver information can be extracted from hardware without an OS image (using WinPE)


Zdrivers Imaging Toolkit 6

To use Zdrivers

Copy zdrivers.exe to a USB pen drive, an accessible network share or other removable media from

C:\Program Files\ENGL\ImagingToolkit\6.0\Ztoolkit\x86 (or x64 as appropriate)

Launch Zdrivers from the removable media

Step through the Zdrivers wizard and save the xml file to an appropriate location


ZdriversDemonstration


Build Console


Build Console

The Build Console is the primary tool used to create and configure the automated Windows build process.

In this session we are going to be concentrating on the driver management side to Build Console


Build ConsoleImport driver scan

1. Using Build Console, select Add Drivers from the File Library

2. Select Zdrivers hardware scan and specify a path to the XML file created by Zdrivers.

To query the ENGL driver service ensure Download drivers is checked

3. When prompted click Yes to import the machine into the File Library

4. Select the Windows operating system to be deployed, then click Next twice to query the ENGL driver service

5. Select the drivers to download and click Next

6. Once the driver download process has completed click Finish



The drivers are now imported and downloaded for the hardware and OS selected

Hardware Manufacturer

Hardware Model

Devices with available Drivers

Driver status

Devices without drivers

Driver Pack(based on OS)


Build ConsoleProperties view – No Drivers

There may be devices listed under the No Drivers section in the Driver Pack properties.

This does not necessarily mean that a required driver is missing because the device may be handled natively by Windows.

If there are no Unknown Devices listed in Device Manager on a built machine then no further drivers are required.

If there are unknown devices then right-click the appropriate “No Drivers” device and select Report Issue to notify ENGL that a driver is required.


Build ConsoleDownload additional driver pack



The driver scan has now been imported into Build Console and the drivers for the selected OS have now been downloaded successfully.

To download drivers for an additional OS

1. Right click on the Machine entry in the file library.

2. Select “Search for drivers”

3. Select appropriate “Windows Operating System”

4. The driver info will be sent back to ENGL and a list of available drivers is returned

5. Download appropriate drivers


Build ConsoleDownload additional drivers



The drivers have now been downloaded and are stored in the file library

The hardware scan only needs to be performed once per hardware model.

Build Console can then download drivers for all supported OS’s



If there are variations on the hardware – different scans can be taken.

The steps to import the hardware are the same.

Build Console will detect that the hardware is for the same model and will attempt to merge the driver scan information.

Duplicate information will be ignored while additional hardware will be listed and an option to download drivers will be added


Build ConsoleCreating Driver images


Build ConsoleCreating driver images

In order to create a driver image an appropriate project needs to be open. This project must be configured for the OS that you wish to create a driver image.

Run the Deployment Wizard

Select Build Process creation and click Next

Select Driver add-on images and click Next

Select the required machine models and click Next twice

Once the Deployment Wizard has completed select Open project folder and click Finish

Copy the project folder\images\project name folder to the ZENworks imaging server

Update the images.ini in the TFTP server's zimfiles folder to include the new entries in the integration folder\ZENworks\tftp\zimfiles\images.ini file



A Windows Explorer window will now open with the files that have been created

Folder containing image files.This needs to be copied to the ZENworks Imaging server

Source files used to create drivers image

Note: These folders are volatile. Files should not be manually added to

or edited in this folders structure



The images.ini file also needs to be updated on the server.

A sample is configured for you at

integration folder\ZENworks\tftp\zimfiles\images.ini

i.e. ; ENGL Imaging Toolkit 6.0 Build Console; Copyright (C) 1999-2011 Expert Networking Group Limited; May 16, 2011 17:18:25

; This images.ini file can be used by ENGL Zim to automate the selection; and restoration of hardware dependent images based on the driver images; created by the Build Console Deployment Wizard.

[Dell Inc.]Precision WorkStation T3400="drivers-dell-precision-workstation-t3400.zmg|desktop|win7-ent-x86"

Name of machine-specific driver add-on image

Model

Manufacturer

Comma separated list of project operating systems supported by this machine

Machine type


http://www.engl.co.uk/documentation/imagingtoolkit/6.0/proc-imagerestore-auto-inifiles.html


More information on the format of the images.ini file can be found in the product documentation:


Build ConsoleFiles and folders


Build ConsoleFiles and Folders

There are several files and folders that are used by or created when the deployment wizard creates the drivers image.

These can be split between 3 main areas:

File library files

Project files

Build Console files

Note: These files are created and managed by Build Console and should not be edited in any way


Build ConsoleFiles and Folders – File Library

Path <FILE LIBRARY>\Drivers\Machines\<MANUFACTURER>\<MODEL>\

File Deploy.log

RoleRecord of all driver processing for the manufacturer/model of hardware




File hardware.xml

Role Hardware scan information




Filedrivers-<OS>-<ARCH>.xml (Drivers-Win7-x64.xml)

RoleDriver scan information as returned from ENGL. This file contains the hardware id info and corresponding driver download links.



Path <FILE LIBRARY>\Drivers\Machines\<MANUFACTUROR>\<MODEL>\

Filedrivers-<OS>-<ARCH>-manual.xml (Drivers-Win7-x64-manual.xml)

RoleInformation about manually modified drivers i.e. manually added, replaced or custom properties applied




Folder \<OS>\<ARCH>\

RoleContains the driver install files (downloaded, manually added or replaced)


Build ConsoleFiles and Folders – Project files

Path <project>\imagesource\drivers\<DRIVER IMAGE FILE NAME>\

Folder \drivers

RoleContains the expanded driver files that will be processed and installed by sysprep mini-setup


Build ConsoleFiles and Folders – Project files

Path <project>\imagesource\drivers\<DRIVER IMAGE FILE NAME>\

Folder \ztoolkit

RoleContains the driver install file sets that will be processed and installed by the build process using the install.cmd file


Build ConsoleFiles and Folders – Build Console files

Path%AppData%\ENGL\ImagingToolkit\ (Windows XP)

%ProgramData%\ENGL\ImagingToolkit\ (Windows Vista or newer)

File Buildconsole.log

RoleLog file reporting all actions taken by Build Console when creating driver images (and all other Build Console actions)


TroubleshootingDriver issues


TroubleshootingDriver Issues – Driver download

If Build Console reports an error downloading a driver file:

Enable Build Console debug logging (if not already configured)

(Tools Options Log File)

Review BuildConsole.log file for error message

Open up appropriate Drivers-<OS>-<ARCH>.xml file in notepad

Identify driver download link


TroubleshootingDriver Issues – Driver download

Does this download successfully in a browser?

The file can be saved to the <os>\<arch>\<driver class>\<description> folder structure, where <driver class> & <description> are defined in the xml file. It will now appear in Build Console as “Downloaded”

or

Right click on failed driver entry within Build Console, select replace driver – select the downloaded driver file – driver will then be imported into Build Console

If the driver fails to download, Right click on the problem download and select “Report Issue”. This will log a driver incident with ENGL


TroubleshootingDriver Issues – Driver image creation

If Build Console reports an error creating a driver image:

Enable Build Console debug logging (if not already configured)

(Tools Options Log File)

Review BuildConsole.log file for error message

Resolve error and retry

If the issue is not obvious - Right click on the problem driver and select “Report Issue”. This will log a driver incident with ENGL. We will assist you in resolving the issue


TroubleshootingDriver Issues – Driver installation issue

Driver image has restored successfully but built machine has unknown device.

There are several approaches to debugging the problem.

First we need to identify what the issue is:

Driver is not available

Sysprep mini-setup failed to install driver

Build process failed to install driver



When a device shows up as “unknown” post build it implies that the driver either failed to install or that no driver was available.

Identify what the unknown device is:

Launch devmgmt.msc

Right click on unknown device – select properties

Select details tab

Select Hardware id’s from Property drop down list

Record hardware id’s listed.



Review file library - drivers-<OS>-<ARCH>.xml & drivers-<OS>-<ARCH>-manual.xml files – is the hardware id matched anywhere? If so we’ve found our problem driver

Review hardware.xml file – is the hardware id matched anywhere? If so we’ve found our problem device

Note: & may need to be replaced with & when searching through files.

If no downloaded driver is appropriate

Review manufacturer's website for appropriate driver

Download driver

Import into buildconsole using either replace (an existing driver) or manually add (a new driver)

Re-deploy drivers image and test



If downloaded driver is appropriate but has failed to install

Review driver folder structure – is the driver being installed by sysprep or by the install.cmd file

If the driver is in c:\drivers structure sysprep

If the driver is in c:\ztoolkit\drivers structure install.cmd file



Sysprep install failure: .Inf file not found

Check location of inf file in c:\drivers structure

Review c:\ztoolkit\ztoolkit.log file

Was the driver inf file identified by the build process or was it “skipped”?

If the driver was skipped – update the <project>.xml file and change driver search depth option to a larger value.



Sysprep install failure: .Inf failed to install

Open driver image in Image Explorer

Mark any (OS) folders that do not match the deploying OS as deleted

Save updated driver image

Redeploy driver image and test

If this resolves the issue then:

Create a zip file containing appropriate files and replace existing driver with subset of original files.




If this fails to resolves the issue then:

Review driver folder structure – is there an exe that can be launched to do a silent/unattended install of the driver.

Identify appropriate silent/unattended install command

Right click on driver in Build Console

Select “Properties”

Enable “Install using script instead of hardware detection”

Populate command line if one is known or leave field blank to allow Build Console to attempt to identify the appropriate commandline


If there are still issues deploying driver - Right click on the problem driver and select – Report Issue.



Install.cmd – Driver fails to install silently

Review commandline set up in

<project>\imagesource\drivers\<DRIVER IMAGE FILE NAME>\ztoolkit\install.cmd

Identify correct commandline

•Review *.cva, swi.xml or readme.txt – there may be information on how to do a silent or unattended install

•Run command with /? Switch – is there any setup switches given

•Google search for appropriate silent/unattended command line



Right click on driver in Build Console

Select “Properties”

Enable “Install using script instead of hardware detection”

Populate command line


If there are still issues deploying driver right click on the problem driver and select “Report Issue”.


Known issues


Know Issues

ENGL TID-2010002

Contains a list of machines and drivers with known issues and workarounds to deliver a valid drivers add-on image.

https://englnet.engl.co.uk/kb/tid-2010002.htm

If you do have issues with...

• Build console creating a drivers add-on image

• Drivers not installing during the build

• Incorrect command line switches being added to images.ini file


Know Issues

Let us know!

• Right click on problem driver in Build Console and select “Report issue”

• Log an incident on englnet

https://englnet.engl.co.uk/nps

• Email [email protected]

• Report an issue via support forum - engl.support.imagingtoolkit6.drivers


More information


More Information

Useful links Product information and Downloads

www.engl.co.uk/products/imagingtoolkit

Success Stories

www.engl.co.uk/company/success

Partners

www.engl.co.uk/partners


More Information

Future Events Tech Bite sessions

Brainshare

www.engl.co.uk/events

www.engl.co.uk

Jamie Glendinning [email protected] ENGL Imaging Toolkit 6 Managing your drivers using...

Documents

Transcript of Jamie Glendinning [email protected] ENGL Imaging Toolkit 6 Managing your drivers using...