Release Notes

April 30, 2019

Includes UIUPrep version 5.8.3.0

Issue: Classic Mode Loop

Symptoms:
UIU Classic Mode continuously runs in an infinite loop upon deployment to target machine(s).

Resolution:
Corrected the issue in the UIU that was preventing Classic Mode from registering properly, resulting in an infinite "Classic Mode" loop.

Issue: Sysprep Entry Duplication

Symptoms:
When a Sysprep answer file is imported, the UIU Classic Mode is not recognizing several variables and is duplicating Sysprep answer file entries.

Resolution:
Corrected the issue causing the the UIU Classic Mode to duplicate the InputLocale, SystemLocale, UILanguage and UserLanguage fields.

Issue: Sysprep Password Field

Symptoms:
The UIU Classic Mode prevents the user from clearing the "Local Administrator Password" field.

Resolution:
Corrected the issue that prevented the user from clearing the "Local Administrator Password" field. The UIU Classic Mode will now allow for an empty "Computer Name" field, as is permitted by mini-setup.

---

Feature Addition: Computer Name

Details:
A "Prompt for Computer Name" checkbox has been added to the "Advanced" tab. When selected, this feature will prompt for Computer Name during the UIU process, prior to mini-setup.

Feature Addition: Remove UIU Repository After Deployment

Details:
UIU Classic Mode will automatically clean up the UIU Driver Database files located in the UIU Replository, local to the deployed machine(s).

---

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.

Requirements - .Net Framework Version

The UIU Classic Mode (as of UIU 5.8.0.x) requires the .NET 4.6 Framework.

For assistance or questions, please contact us:

UIU Support