ENGL Imaging Toolkit™ 11.0.6 for |
In order to automate the restoration of images two lookup files are required. These files are normally created by the Build Console based on the projects selected when running the Integration Wizard and the project and drivers selected when running the Deployment Wizard.
These files may need some modification in your environment and so their layout and function are described here.
The images.ini controls which driver image a machine restores, what type of machine it is, and which operating systems it supports. At minimum it must specify the driver image to restore, but may be extended to include other machine-specific information if required.
The following describes the entries in a typical images.ini originally created by the Build Console Deployment Wizard following a successful driver deployment.
; Program that generated this file
; Copyright
; Date and time this file was created
; This is a sample images.ini file that can be used by ENGL Zim to automate the selection and
; restoration of hardware specific driver images. Driver images can be created using Build Console
; which also generates additional information for the images.ini lookup file.
[Manufacturer*]
Model* = "Name of machine-specific driver image | Machine type | Comma separated list of project operating systems supported by this machine"
* The Manufacturer and Model details must match the information passed by ENGL Zim when querying the images.ini.
Manufacturer entries may include a wildcard to reduce the number of sections required. For example Dell* will match Dell Inc. and Dell Computer Corporation.
The following is a sample images.ini file showing some of the changes that might be made to deliver driver images for several machines and to limit which machines are able to deploy a certain operating system when used in conjunction with the standard ENGL Zim.cfg as generated by the Build Console Integration Wizard.
; This is a sample images.ini file that can be used by ENGL Zim to automate the selection and
; restoration of hardware specific driver images. Driver images can be created using Build Console
; which also generates additional information for the images.ini lookup file.
[Dell*]
Latitude E6530="drivers-dell-latitude-E6530|laptop|win7-x86"
OptiPlex 755="drivers-dell-optiplex-755|desktop|win7-x86"
OptiPlex 7010="drivers-dell-optiplex-7010|desktop|win8-x64"
[Hewlett*]
HP Compaq dc5800 Small Form Factor="drivers-hp-hp-compaq-dc5800-small-form-factor|desktop|win7-x86"
The projects.ini is used by the standard ENGL Zim script as generated by the Build Console Integration Wizard to display a list of projects that have been created using the Build Console and contains details of the path to the images and the image names themselves in order that a single script can be used to deploy multiple combinations of Operating System and build process configuration.
The following describes the entries in a typical projects.ini originally created by the Build Console Deployment Wizard.
; ; ENGL Zim projects.ini lookup file ; [Projects] projectId = "Project Description" ; Project details [Project Description] Description = Project Description project_image_path = Path to image files project_os = Project operating system, this is the long version of the operating system name including edition and service pack e.g. win7-pro-sp1-x86 driver_os = Driver operating system, this is the short version of the operating system name e.g. win7-x86 base_image = Name of base image file
ztoolkit = Name of ztoolkit image file
partition_count = The number of partitions set in the project and created in the base image by the Windows Unattended installation process
partition1_size = The size of the first partition set in the project and created in the base image by the Windows Unattended installation process
partition2_size = The size of the second partition set in the project and created in the base image by the Windows Unattended installation process
The following is a sample projects.ini file showing some of the changes that might be made when several projects have been created and then selected, when running the Build Console Integration Wizard.
; ; ENGL Zim projects.ini lookup file ; [projects] project1 = Windows 10 Enterprise (x64) project2 = Windows 7 Professional (x64) project3 = Windows 7 Professional (Paris Office) (x86) - French project4 = Windows 7 Professional (Lab Machine) (x86) ; Project details [Windows 10 Enterprise (x64)] Description = Windows 10 Enterprise (x64) project_image_path = win10-standard-build project_os = win10-ent-x64 driver_os = win10-ent-x64 base_image = win10-ent-x64-16299-postsp partition_count = 2 partition1_size = 100 partition2_size = 60000 ztoolkit = ztoolkit
[Windows 7 Professional (x64)] Description = Windows 7 Professional (x64) project_image_path = win7-standard-build project_os = win7-pro-x64 driver_os = win7-x64 base_image = win7-pro-x64-postsp efi_boot_image = win8-pro-x64-uefi-boot partition_count = 2 partition1_size = 100 partition2_size = 60000 ztoolkit = ztoolkit [Windows 7 Professional (Paris Office) (x86) - French] Description = Windows 7 Professional (Paris Office) (x86) - French project_image_path = win732 project_os = win7-sp1-pro-x86 partition_count = 1 partition1_size = 60000 driver_os = win7-x86-french base_image = win7-sp1-pro-x86-postsp-french ztoolkit = ztoolkit [Windows 7 Professional (Lab Machine) (x86)] Description = Windows 7 Professional (Lab Machine) (x86) project_image_path = win7-sp1-pro-x86-lab project_os = win7-sp1-pro-x86 driver_os = win7-x86 base_image = win7-sp1-pro-x86-postsp
partition_count = 2 partition1_size = 100 partition2_size = 60000 ztoolkit = ztoolkit