Migration from version 4.x to version 5.0

Intel® Integrators Toolkit (ITK)

Migration from version 4.0 to version 5.0

Version 1.2

This document details the most notable and impactful changes in migrating from ITK 4.0 to ITK 5.0. This

list is not comprehensive and minor changes such as user interface layout are not covered.

BIOS File Consolidation

• ITK 4.0 used .ITK files, which could be read by the tool to create new .BIO and .EXE files for use

by the BIOS or operating system, respectively, to change BIOS settings.

• ITK 4.0 allowed text-based .INI configuration files to be created. These files could be directly

manipulated with a standard text editor such as Notepad* or Vi*.

• ITK 5.0 no longer uses ITK or .INI files. All the information ITK 5.0 needs is now included in the

.BIO files.

• Only .BIO files are used with ITK 5.0.

Legacy ITK 4.0 Support

• ITK 5.0 supports legacy ITK 4.0 BIOS and configuration files. If a legacy .ITK file is chosen, a full

instance of ITK 4.0 launches.

• Sustaining support of ITK 4.0 will stop with the release of 5.0, but ITK 4.0 will continue to function

for legacy products.

• Legacy .BIO files will not have the necessary data to be loaded with either ITK 5.0 or ITK 4.0. You

must use the associated .ITK file for legacy BIOS files.

• Legacy support of ITK 4.0 includes DOS and WinPE command line arguments. All of the

following command line tools are included with ITK 5.0:

o ITK 4.0

 DOS: itoolkit.exe

 Windows: itoolkitw.exe

o ITK 5.0

 DOS: vcust.exe

 Windows 32-bit: vcustw.exe

 Windows 64-bit: vcustw64.exe

•

Microsoft* OEM Activation 3.0

• ITK 4.0 does not include support for Microsoft’s OEM Activation*.

• ITK 5.0 supports Microsoft OEM Activation 3.0 (OA3) for volume licensing of Microsoft Windows

8*.

o The individual payload files which include activation information must be obtained from

Microsoft.

o ITK 5.0 applies this provided activation information to the board, enabling scriptable,

command-line activation for Microsoft Windows 8.

• OA3 is supported through command line interactions only.

A simple OEM Activation can be accomplished by navigating to the “Intel(R) Integrator

Toolkit\Installation Tool – Windows\” file-path and entering the following command:

vcustw -oa3 -oemid=Name -tableid=Name -oadata=file (32 Bit)

PAGE 1
Intel® Integrators Toolkit (ITK) Migration from version 4.0 to version 5.0 Version 1.2 This document details the most notable and impactful changes in migrating from ITK 4.0 to ITK 5.0. This list is not comprehensive and minor changes such as user interface layout are not covered. BIOS File Consolidation • • • • ITK 4.0 used .ITK files, which could be read by the tool to create new .BIO and .EXE files for use by the BIOS or operating system, respectively, to change BIOS settings. ITK 4.
PAGE 2
vcustw64 -oa3 -oemid=Name -tableid=Name -oadata=file (64 Bit) OEMID and TableID are both OEM specific. OAData is the payload file received from Microsoft. Entering the full directory path to the payload file is necessary. Full syntax options are available by entering “vcustw help” or “vcustw64 help” from the same file-path. Note that the command line syntax changed from ITK 4.0, so any automated scripts will need to be adjusted accordingly. BIOS Splash Intel Logo • • ITK 4.
PAGE 3
Temporarily Skip Prompt: A boot counter is started. The system can be rebooted a specified number of times up to 50, allowing any changes to be made by ITK during these reboots. The default boot counter is 5. After the boot counter has expired, Unattended BIOS Configuration will be reset to Always Prompt. Never Prompt: All changes made via ITK are allowed.