Release Notes

5.7.0.0 - Executables Update Only Bookmark

June 11, 2018 - ISSUE UNDER INVESTIGATION

Issue: Microsoft ADK 1803

Symptoms:
When employing ADK options in UIU 5.7.0.0, with ADK 1803 installed on the UIU 5 Console machine, DISM commands fail to execute properly. This issue is under investigation.

Work-Around:
When employing ADK options, please use an earlier version of Microsoft ADK on the console machine, (e.g. ADK 1709).




June 8, 2018 - RELEASE
Includes UIUprep version 5.6.0.0


Updating from pre-5.5.0.0 versions of the UIU 5 product requires two steps. First, use the UIU 5 Updater to obtain the 5.5.0.0 version and then re-execute online updates from that version to obtain UIU 5 (v5.7.0.0)


Requirements Change - .Net Framework Version Upgrade

The UIU 5 (as of UIU 5.7.x.x) now requires the .NET 4.6 Framework.



Feature Addition - UEFI Boot Media

The UIU 5's boot media creation features now all support UEFI (GPT) in addition to MBR (BIOS).



Notes on creating UEFI media:

  • Create Offline UEFI (GPT) Media, (Bootable WinPE Media), will evaluate the provided removable drive and it's total size. If it's total size is greater than 32 GB, it will be partitioned to 32 GB, (FAT32 maximum). If it is less than 32 GB, it will be partitioned accordingly to fit it's maximum capacity.


  • When building Offline UEFI media, the user may select a removable drive for Bootable WinPE Media and/or a removable drive for UIU Repository. If only one is selected, media will be built only for the selected option. For example, if a removable drive is selected for Bootable WinPE Media, (but not for the UIU Repository), the wizard will create the Bootable WinPE Media and will not attempt to create UIU Repository media. The inverse is also true.

  • When booting a target PC with media created via UIU 5, (Create Offline UEFI (GPT) Media), the boot process will pause once WinPE has initialized and state:

        "Make sure the removable media containing the UIU Repository and target image to deploy is connected and press ENTER."

    This provides the Administrator a chance to attach or swap removable drives to the target PC. Once ENTER is pressed, the STARTNET.CMD script looks for a UIU Repository directory structure on all drives, and upon finding one, attempts to deploy the provided OS.WIM or OS.GHO image, and then runs UIUPREP.




Issue: Windows 7 DISM Errors

Symptoms:
When running the UIU 5 on Windows 7 or Windows Server 2008, operations that required DISM functions, (e.g. media creation), would produce a non-critical system error.

Resolution:
Fixed an issue where trying to use DISM libraries on Windows 7 / Windows Server 2008 could fail due to DISM library-related issues.



Issue: UIU 5 Window Resizing

Symptoms:
The UIU 5 window would not resize.

Resolution:
UIU 5 now supports the minimize/maximize window button and is completely resizable.



Support: DISM Log Location

Location Change:
UIU 5 now stores the DISM log for DISM sessions it initializes in ProgramData\UIU\dism.log. Previously, it was stored in the default DISM log location, %windir%\logs\dism\dism.log. DISM sessions not initialized by UIU (e.g. user-driven DISM commands at the CLI, etc.) continue to log in the default location--but UIU 5-driven operations using DISM will log in the UIU directory, which should make it easier to review DISM errors associated with UIU 5.



Feature Enhancements - Repository Management

Improvements have been made to Repository Management in this version (5.7.x.x) and now include the ability to update any combination of UIU Components, Driver Database, and Driver Files. Additional improvements include the ability to perform CRC Validation, Clean up unreferenced drivers, and produce commands that will facilitate the scripting of updates, (e.g. using scheduled tasks).



  • Enhancement: Expanded Removable Disk Support

    The "Repository Management" control has been updated to support removable disks, local disks, and network disks. Any valid path is acceptable, given it is accessible and that UIU 5 has read/write access. The requirement of being a shared network disk has been removed.

    As of version 5.7.x.x, the Repository Management control's "Change Repository" feature has been further modified to better support the new philosophy of allowing a UIU Repository to live "anywhere", including a non-shared path, a removable drive, etc. Because of this change, it no longer attempts to convert local paths to FQDN UNC paths--which means users will need to be specific when entering their Repository path, as it's passed along as-is to built media. This resolves an issue that was preventing users from entering a network path in the new Change Repository control.


  • Addition: Custom Drivers Handling Restored the "Custom Drivers" button (from pre-UIU5v2) which allowed users to navigate their Repository's "Custom Drivers" directory. This functionality exists now both in the Repository Manager control as well as in the Deployment Settings control, under the Drivers tab. Clicking the "Custom Drivers" button opens an Explorer window to the selected Repository's Custom directory, and writes a "README Custom Drivers.txt" with basic instructions (copied from the original UIU5) as to how it can be utilized.


  • Issue: Scripting Online Updates Fails

    Symptoms:
    Provided command line options, placed into a script fail to execute.

    Resolution:
    Added support for the arguments from the Command Line for updating and/or scripting purposes.



  • The UIU 5 (version 5.5.0.0 and newer) no longer employs driver.dat files for installation and manual updates. This (and future) versions will require Driver.imp files (e.g. DB170411-p5460.imp) for those operations. Online UIU 5 Updates will be unaffected.


    UIU Log File Location CHANGE!

    Details:
    On deployed machines only, the Log folder & UIU data folder have been migrated from Program Files to ProgramData.

    UIU log files on deployed machines are now located under the ProgramData\UIU directory. Additionally, resources needed by each application are extracted/placed in the ProgramData\UIU\bin directory (temporarily). Program Files is no longer used for any resources or logs.

    NOTE: The UIU 5 Installation log files are also now located in ProgramData\UIU; other install files remain in Program Files.





Comments are closed.