Release Notes

August 25, 2022 - RELEASE

Includes UIUPrep version 5.12.0.0

This is an update of the UIUPREP application ONLY. Changes in this version of the UIUPREP application do not affect the UIU Classic Mode product.

NEW FEATURE: Enhanced UIU Logging

Details:
UIUPrep now logs to \ProgramData\UIU\UIU.cmtl.log in addition to the standard UIUPrep log file, in Configuration Manager Trace Log (CMTL) format.This log is a duplication of the standard UIU log while migration to CMTL format is in progress.

Reminder: NEW FEATURE: Classic Mode Command Line Interface (CLI) Auto Import

Details:
Added a "-cmautoimportrepository" switch for UIU Classic Mode: This switch enables Classic Mode CLI to automatically discover a UIU Repository Import (IMP) file in the same directory as the Classic Mode executable. In the event that multiple IMP files exist, the first (alphanumerical) entry is selected, based on file name. This switch is overridden by the -cmrepositoryimportpath switch, so if a user provides both, the value provided by -cmrepositoryimportpath is selected. If the -cmautorepositoryimport switch is provided and Classic Mode is unable to locate any IMP files, Classic Mode writes an error dialogue ("Classic Mode does not continue automatically if the -cmautorepositoryimport switch is provided and cannot locate a UIU Repository Import (IMP) file.") and exits.

For more information, please review the UIU Classic Mode User Guide

---

What is the UIU Classic Mode?

The original UIU 4.x — known in recent years as the UIU Classic — accommodated all OS deployment solutions, including those that do not utilize Microsoft's Windows PE, by storing the entire UIU Driver Database within the OS image. The UIU Classic Mode is an updated version of that methodology for those users that do not use a WinPE-based deployment solution.

How is it different from the UIU 4.x "Classic" product?

The UIU Classic method has been integrated into a optimized modern GUI, (though the basic process was preserved as much as possible for ease of adoption).

How is it different from the UIU 5?

• The entire UIU Driver Database is stored in the UIU-prepared image as opposed to network-based delivery of target machine specific drivers only.


• The Master Image must be manipulated by the UIU Classic Mode process. The UIU 5 does not require any preparation within the image itself.


• Using the UIU Classic Mode, if unsigned drivers are opted-in, the Administrator will be prompted for each one during execution. The UIU 5, wherein its method includes staging the appropriate drivers from WinPE, allows the Windows operating system to address unsigned drivers without interaction.

Who should use the UIU Classic Mode?

Users employing OS deployment solutions that are not based on Windows PE (e.g. Linux-based solutions like CloneZilla and FOG)

Who should NOT use the UIU Classic Mode?

• It is highly recommended that users employing OS deployment solutions that utilize Windows PE use the UIU 5


• UIU customers that are utilizing the Microsoft's SCCM solution should use the UIU Plug-ins 2.0 - SCCM


• UIU customers that are utilizing the Microsoft's MDT solution should use the UIU Plug-ins 2.0 - MDT

Please refer to the UIU Classic Mode - User Guide for detailed implementation and usage instructions.

For assistance or questions, please contact us:

UIU Support