Release Notes

September 16, 2024 - RELEASE

Includes UIUPrep version 5.13.1.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.

 

 

 

 

Announcement: NEW FEATURE: HTTP/s Support

 

 

Details:
UIUPrep now supports HTTP/s source locations, (including 1E Nomad discovered cache locations).

Requirements: IP protocol access to desired source locations; Internet or Intranet.

1E Nomad Application ONLY:
UIUPrep will automatically determine which mode to use (HTTP, HTTPS, or SMB) based on the 1E Nomad settings discovered in the WinPE registry. Please contact UIU Support for additional detail specific to this environment.

GENERAL FEATURES:

If the HTTP/s features are enabled you MUST have specified a database version using the requisite advanced switch. That switch is -driverudbname %filename%.udb. for example: “-driverudbname DB-24-09-10.udb” for the September 10th, 2024 release. This version must be available in any repository that a machine might chose from %UIURepository%\repository\*.udb

The UIU Log location remains the same, however the logging format has changed. UIUPrep’s processes will now output in the standard CMTrace readable format, viewing with Notepad or other text editor is no longer recommended. Because of this, when viewing in CMTrace, there may now be additional information in the information section located at the bottom of the CMTrace window for any given logged item/line that is selected.

Support has been included for WinPE version 10.1.26100.1 in order to support modern WADK versions.
 

 

 

 

 

 

---

 

 

 

 

 

 

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