866-754-3592

Release Notes

rss

DB-20-01-18 Driver Database Update Bookmark

January 18, 2020
 

Driver DB Amendments:

Customer-requested drivers since January 13, 2020 Release.

This release includes the DB-20-01-16 Release.
 

 

Drivers Affected:

See Attached: UIU DB-20-01-18 Drivers.pdf

 

 

 

Make and Models Affected:

See Attached: Make-Model DB-20-01-18.pdf

 

 

 

 

Issue: Intel NIC (I219-V) & Intel Smart Sound Technology

 

 

Symptoms:
Older versions of the Intel NIC (I219-V) and Intel Smart Sound Technology drivers not installing properly.

Resolution:
Added latest driver to rectify the installation issue.

 

 

 

 

Reminder:

 

 

 

 

The full driver database exceeds 30Gb in size (30.0 Gb IMP). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).

 

 

Note: As of January 16, 2020, the full UIU driver database available for download from the web site will contain only drivers for supported 64-bit Windows operating systems, (Win7, Win8.1, & Win10). Requests for 32-bit support should be directed to UIU Support.

 

 

 

 

USB Flash drives need to be formatted with the NTFS file system before the driver database will successfully transfer. Network share access is recommended.

 

 

 

Support Reminder:

 

The Big Bang Support Team would like to remind our customers to please clear out any drivers represented in the Custom folder(s) prior to testing with a new version of the UIU Driver Database as neglecting to do so may result in false negative installations.  Please contact a Support Representative with questions or concerns. Thank you!

 

 

 

DB-20-01-13 Driver Database Update Bookmark

January 13, 2020
 

Driver DB Amendments:

Customer-requested drivers since December 12, 2019 Release.
 

 

Drivers Affected:

See Attached: UIU DB-20-01-13 Drivers.pdf

 

 

 

Make and Models Affected:

See Attached: Make-Model DB-20-01-13.pdf

 

 

 

 

 

 

Reminder:

 

 

 

 

The full driver database exceeds 34Gb in size (34.1 Gb IMP). Please follow the guidelines below for optimal performance. This database release still covers Windows 7 through Windows 10 (32/64bit).

 

 

USB Flash drives need to be formatted with the NTFS file system before the driver database will successfully transfer. Network share access is recommended.

 

 

 

Support Reminder:

 

The Big Bang Support Team would like to remind our customers to please clear out any drivers represented in the Custom folder(s) prior to testing with a new version of the UIU Driver Database as neglecting to do so may result in false negative installations.  Please contact a Support Representative with questions or concerns. Thank you!

 

5.9.2.0 - UIU Classic Mode - Executables Update Only Bookmark

January 3, 2020 - RELEASE

Includes UIUPrep version 5.9.0.0

 

 


This is an update of the UIU Classic Mode application ONLY.

 

 

 

 

The UIU Classic Mode is a direct, compulsory upgrade for the UIU Classic (4.x) product. Support for UIU Classic (4.x) will be deprecated with the introduction of UIU License Keys with expiration dates ≥ Jan 1, 2020.

 

 

 

 

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

 

 

Reminder: KNOWN ISSUE - WinPE 3.0 & 4.0 (x86 only)

 

 

Symptoms:
Servicing older Windows PE media (3.x & 4.x) requires 32-bit specific binaries (DISM) which do not load under a 64-bit process, resulting in error conditions. Big Bang recommends that Winodw PE version 10 be employed. Contact UIU Support for additional information.

 

 

 


 

 

 

 

 

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.

 

 

 

 

 

Due to security upgrades, UIU License Keys with expiration dates ≥ Jan 1, 2020 will only be valid with the following product versions of the UIU (or newer):

UIU 5: 5.8.0.0
UIU Plug-in for SCCM: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Plug-in for MDT: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Classic Mode: 5.8.0.0


Note: Each of these products employ the UIUPREP executable and as such the version of UIUPREP.EXE must be ≥ 5.8.0.0


WARNING: The UIU Classic (4.x) Product will not function using UIU License Keys with expiration dates ≥ Jan 1, 2020

 

 

 

 

 

 

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

 

 

 

 

 

 

2.3.2.0 - UIU Plug-ins 2.0 with SCCM - Executables Update Only Bookmark

December 31, 2019 - RELEASE
Includes UIU plug-in for SCCM version 2.3.2.0
Includes UIUPrep version 5.9.0.0


This is an update of the UIUPM application ONLY.

Issue: UIUPM Updating Errors (SCCM)

Symptoms:
Customers trying to update Task Sequences with the UIUPM would crash.

Resolution:
Fixed an issue relating to how UIUPM interacts with the Configuration Manager.



Issue: Clean Mountpoints

Symptoms:
In situations when the media build process fails to complete the DISM mountpoints would not be cleaned up under certain conditions.

Resolution:
Code was modified to ensure proper and complete mountpoint cleanup.



Issue: Boot+ Crash

Symptoms:
If no UIU databases (UDB's) are found in the current UIU Repository, the Boot+ operation crashes.

Resolution:
This now results in a descriptive error presented in the lower left dialog.



Issue: Custom Driver crash

Symptoms:
Clicking "Custom Drivers" in the Repository Manager control could crash. (This occurred if the Repository was not internally initialized, (e.g. updating the Repository would cause it to be initialized internally, therefore clicking "Custom Drivers" after an update operation would work properly, but clicking it before could cause a crash.)

Resolution:
Code was modified to correct this condition.



Issue: Proxy Support

Details:
UIU proxy support has been overhauled. This new development should facilitate proxy support (address/port), and optionally, a username/password.



Issue: KNOWN ISSUE - WinPE 3.0 & 4.0 (x86 only)

Symptoms:
Servicing older Windows PE media (3.x & 4.x) requires 32-bit specific binaries (DISM) which do not load under a 64-bit process, resulting in error conditions. Big Bang recommends that Winodw PE version 10 be employed. Contact UIU Support for additional information.



Due to security upgrades, UIU License Keys with expiration dates ≥ Jan 1, 2020 will only be valid with the following product versions of the UIU (or newer):

UIU 5: 5.8.0.0
UIU Plug-in for SCCM: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Plug-in for MDT: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Classic Mode: 5.8.0.0


Note: Each of these products employ the UIUPREP executable and as such the version of UIUPREP.EXE must be ≥ 5.8.1.0


WARNING: The UIU Classic (4.x) Product will not function using UIU License Keys with expiration dates ≥ Jan 1, 2020


REMINDER: Requirements Change - .Net Framework Version Upgrade

The UIU Plug-ins 2.0 with SCCM (as of UIU 2.2.2.x) now requires the .NET 4.6 Framework.





REMINDER

The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT (v1.x). Support and UIU DAT files for UIU plug-in for MDT (v1.x) will be deprecated on Feb 1, 2018.

All OS deployment task sequences should be thoroughly assessed for remnants of the UIU Machine Configuration element, (associated with the UIU v1.x product), prior to uninstalling the UIU v1.x product. Failure to remove UIU v1.x task sequence elements prior to uninstallation will result in unrecoverable MMC errors when requesting properties on those task sequences, rendering those task sequences unusable!


Please refer to the UIU Plug-ins 2.0 - SCCM User Guides for detailed implementation and usage instructions.

The UIU Plug-ins 2.0 for SCCM version 2.1.0.0 also includes support for 1E Nomad/Active Efficiency. Please contact UIU Support for details.



The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard SCCM Console interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.

System Center Configuration Manager (SCCM)
In SCCM, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin" directory as well as the addition of necessary WMI classes (MOF) to support the UIU Plug-ins 2.0. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result. Furthermore, if an Administrator is not able to control the configuration of various SCCM Remote Console implementations (distribution of a single UIU dll file), the integration of the UIU Plug-ins 2.0 may prove to be problematic and utilizing the Run Command Line task element will alleviate those issues.

For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.

IMP Files

This version of the UIU requires the use of UIU IMP files to establish a UIU Repository from locally existing files. If bandwidth allows, Big Bang recommends that the UIU Repository be established (and regularly updated) from Big Bang's Online Updates resources. UIU DAT files are not supported.

UIU Import files (*.IMP) contain required driver files, driver database(s) and UIU components which are used to populate a UIU Repository from which deployed target machines will draw necessary files during OS deployment Task Sequence executions. These files are used in conjunction with the UIUPM.

For assistance or questions, please contact us:


UIU Support



2.3.2.0 - UIU Plug-ins 2.0 with MDT - Executables Update Only Bookmark

December 31, 2019 - RELEASE
Includes UIU plug-in for MDT version 2.3.2.0
Includes UIUPrep version 5.9.0.0


This is an update of the UIUPM application ONLY.

Issue: UIU Plugins Load Failure (MDT 8450)

Symptoms:
UIU Plug-ins 2.0 for MDT will no load on MDT 8450.

Resolution:
Code modified to accounbt for supported versions of MDT.



Issue: Clean Mountpoints

Symptoms:
In situations when the media build process fails to complete the DISM mountpoints would not be cleaned up under certain conditions.

Resolution:
Code was modified to ensure proper and complete mountpoint cleanup.



Issue: Boot+ Crash

Symptoms:
If no UIU databases (UDB's) are found in the current UIU Repository, the Boot+ operation crashes.

Resolution:
This now results in a descriptive error presented in the lower left dialog.



Issue: Custom Driver crash

Symptoms:
Clicking "Custom Drivers" in the Repository Manager control could crash. (This occurred if the Repository was not internally initialized, (e.g. updating the Repository would cause it to be initialized internally, therefore clicking "Custom Drivers" after an update operation would work properly, but clicking it before could cause a crash.)

Resolution:
Code was modified to correct this condition.



Issue: Proxy Support

Details:
UIU proxy support has been overhauled. This new development should facilitate proxy support (address/port), and optionally, a username/password.



Issue: KNOWN ISSUE - WinPE 3.0 & 4.0 (x86 only)

Symptoms:
Servicing older Windows PE media (3.x & 4.x) requires 32-bit specific binaries (DISM) which do not load under a 64-bit process, resulting in error conditions. Big Bang recommends that Winodw PE version 10 be employed. Contact UIU Support for additional information.



Due to security upgrades, UIU License Keys with expiration dates ≥ Jan 1, 2020 will only be valid with the following product versions of the UIU (or newer):

UIU 5: 5.8.0.0
UIU Plug-in for SCCM: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Plug-in for MDT: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Classic Mode: 5.8.0.0


Note: Each of these products employ the UIUPREP executable and as such the version of UIUPREP.EXE must be ≥ 5.8.1.0


WARNING: The UIU Classic (4.x) Product will not function using UIU License Keys with expiration dates ≥ Jan 1, 2020

REMINDER: New Feature - Task Sequence UIU License Key Updating

The UIU plug-in updating feature has been upgraded to not only update the MDT plug-in within the framework of MDT (ts.xml), the service will also update the UIU license key within every MDT task sequence that contains the UIU Deployment Configuration element, requiring no Administrator interaction with MDT task sequences post-UIU updates.

Note: In previous versions of the UIU plug-in for MDT, after the plug-in had been updated using the UIU Plug-in Manager, each MDT task sequence that integrated the UIU Deployment Configuration element required an "Apply" event in order to use the UIUPM-updated UIU license key.

Supported MDT builds

  • Microsoft Deployment Toolkit (MDT), build 8450 - 6.3.8450.1000
  • Microsoft Deployment Toolkit (MDT), build 8456 - 6.3.8456.1000


To download Microsoft Deployment Toolkit (MDT), build 8456, click the following link:
Microsoft Deployment Toolkit (MDT) v6.3.8456.1000


REMINDER: Requirements Change - .Net Framework Version Upgrade

The UIU Plug-ins 2.0 with MDT (as of UIU 2.2.2.x) now requires the .NET 4.6 Framework.





REMINDER

The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT (v1.x). Support and UIU DAT files for UIU plug-in for MDT (v1.x) will be deprecated on Feb 1, 2018.


All OS deployment task sequences should be thoroughly assessed for remnants of the UIU Machine Configuration element, (associated with the UIU v1.x product), prior to uninstalling the UIU v1.x product. Failure to remove UIU v1.x task sequence elements prior to uninstallation will result in unrecoverable MMC errors when requesting properties on those task sequences, rendering those task sequences unusable!


Please refer to the UIU Plug-ins 2.0 - MDT User Guides for detailed implementation and usage instructions.




The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard MDT Deployment Workbench interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.

Microsoft Deployment Toolkit (MDT)
In MDT, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Deployment Toolkit\bin" directory as well as a modification (additional section appended) to the Actions.xml file in the same directory. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result.

For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.

IMP Files

This version of the UIU requires the use of UIU IMP files to establish a UIU Repository from locally existing files. If bandwidth allows, Big Bang recommends that the UIU Repository be established (and regularly updated) from Big Bang's Online Updates resources. UIU DAT files are not supported.

UIU Import files (*.IMP) contain required driver files, driver database(s) and UIU components which are used to populate a UIU Repository from which deployed target machines will draw necessary files during OS deployment Task Sequence executions. These files are used in conjunction with the UIUPM.

For assistance or questions, please contact us:


UIU Support



5.9.1.0 - Executables Update Only Bookmark

December 31, 2019 - RELEASE

Includes UIUPrep version 5.9.0.0

 


This is an update of the UIU5 application ONLY.

 

 

 

NEW FEATURE: Proxy Support

 

 

Details:
UIU proxy support has been included, including new support for CLI. This new development should facilitate proxy support (address/port), and optionally, a username/password.

 

 

Issue: Importing IMP files

 

 

Symptoms:
Unhandled Error exception when attemptin to import an IMP file.

Resolution:
Code modified to corrctly import IMP files.

 

 

Due to security upgrades, UIU License Keys with expiration dates ≥ Jan 1, 2020 will only be valid with the following product versions of the UIU (or newer):

UIU 5: 5.8.0.0
UIU Plug-in for SCCM: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Plug-in for MDT: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Classic Mode: 5.8.0.0


Note: Each of these products employ the UIUPREP executable and as such the version of UIUPREP.EXE must be ≥ 5.8.1.0


WARNING: The UIU Classic (4.x) Product will not function using UIU License Keys with expiration dates ≥ Jan 1, 2020

 

 

 

 

Issue: Microsoft ADK 1803

 

 

Symptoms:
When employing ADK options in UIU 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).

Resolution:
With ADK 1803 installed on the UIU 5 Console machine, a pop-up window stating "Using Windows 10 or later" will be presented. Selecting the "OK" button will allow the ADK process to proceed. Alternatively for unattended operations, an earlier version of ADK should be employed, (e.g. ADK 1709).

 

 

REMINDER - Requirements Change - .Net Framework Version Upgrade

 

 

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

 

 

REMINDER - 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..

 

 

REMINDER - 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.


 

 

 

5.9.0.0 - Core Functionality Update - Classic Mode Bookmark

December 27, 2019 - RELEASE

Includes UIUPrep version 5.9.0.0

 

 


This is an update of the UIUPREP application ONLY.

 

 

 

 

The UIU Classic Mode is a direct, compulsory upgrade for the UIU Classic (4.x) product. Support for UIU Classic (4.x) will be deprecated with the introduction of UIU License Keys with expiration dates ≥ Jan 1, 2020.

 

 

 

 

Issue: KNOWN ISSUE - WinPE 3.0 & 4.0 (x86 only)

 

 

Symptoms:
Servicing older Windows PE media (3.x & 4.x) requires 32-bit specific binaries (DISM) which do not load under a 64-bit process, resulting in error conditions. Big Bang recommends that Winodw PE version 10 be employed. Contact UIU Support for additional information.

 

 

NEW FEATURE: Classic Mode Command Line Interface (CLI)

 

 

Details:
Classic Mode is fully-supported and invocable with switches to control it's behavior. A new switch, "-cmcli", is required to invoke Classic Mode behavior from the CLI. This switch is what instructs Classic Mode to "start" when passed by the CLI, and is intended to be passed along with other, optional arguments that begin with "-cm", which can be used to modify the behavior of Classic Mode. This switch acts a safeguard to prevent accidental invocation. Additionally, users can safely pass "-classicmode" to UIU5 without worry of accidentally invoking Classic Mode CLI, as Classic Mode CLI now requires "-cmcli" to begin.

In addition, support has been added for "Maintain Default Administrator Profile" via CLI.

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

 

 

NEW FEATURE: Classic Mode Integrity Check

 

 

Details:
A refactored version of MIMIC has been introduced as "Classic Mode Integrity Check" and is accessible by the CLI only with the "-cmic" switch. The CMIC currently checks for various Windows settings denoting that Windows is awaiting a restart, and indicates as such to the user. The CMIC temporarily displays a message box when it locates one or more of the various Registry settings than can indicate that a reboot is pending in order to allow for pre-emptive investigation regarding the legitimacy of that flag's veracity. Multiple flags may be presented.

 

 

NEW FEATURE: Proxy Support

 

 

Details:
The global system proxy as configured on the local system is now referenced for external access instead of allowing a user to configure a proxy manually, which should more easily account for the different configuration possibilities related to a system's proxies. As a result, the "Internet" tab as part of the "Settings" control which previously facilitated setting and testing a proxy has been removed. UIU proxy support has been overhauled, including new support for CLI. This new development should facilitate proxy support (address/port), and optionally, a username/password.

 

 

NEW FEATURE: Classic Mode Invocation

 

 

Details:
Classic Mode may be invoked from the UIU5 executable by running with the "-classic" switch. A separate Classic Mode "build" may also be used to launch the product. Note that while the UIU5 product can still run in "Classic Mode", the "Classic Mode"-specific build of UIU5 cannot be run in "Normal" mode.

 

 

NEW FEATURE: Classic Mode Online Updates

 

 

Details:
Support has been added for Repository Manager in Classic Mode. A checkbox has been added to the "UIU Driver Database" tab of the Classic Mode wizard and is labeled "Check for UIU Driver Database updates online". When checked, the "Run UIU" functionality will extract an IMP (if provided), and then will leverage Repository Manager technology to update the UIU Repository, including Components (UIUPrep), UDBs (databases), and driver files. This means that an IMP is no longer required, and an entire Repository can be downloaded "on-the-fly" for the machine executing Classic Mode. NOTE: Providing an IMP file will reduce the required update size to only a delta between the provided IMP and the latest UIU Driver Database available online.

 

 

NEW FEATURE: IMP Import Estimated Time

 

 

Details:
Importing an IMP file now displays the estimated time remaining on the operation in addition to the extraction percentage complete.

 

 

NEW FEATURE: Repository Extraction Optimization

 

 

Details:
Repository Import (IMP) has been further optimized, providing a performance increase and reduction in time required to extract an archive, (reducing the time required by more than half).

 

 

NEW FEATURE: Success Screen

 

 

Details:
Classic Mode now includes a "Success" screen to be displayed at the conclusion of Classic Mode. This screen is always displayed (by default), and will only not display if the user has selected either "Shutdown" or "Reboot" as part of the Sysprep Shutdown Options.

 

 

NEW FEATURE: Post-deployment UIU Repository Cleanup

 

 

Details:
UIUPrep for Classic Mode should now clean up the UIU Repository directory (ProgramData\UIU\Repository\Repository) as well as UIU Repository extracted driver INF directory used for installing drivers in Classic Mode (ProgramData\UIU\INF).

 

 

 

 

UIU Classic Mode v5.8.1.0 (or newer) contains several critical fixes and both the UIU Executables Files (UIU Classic Live) and UIU Driver Database Files (UIU Classic Live DB Files) should be downloaded and used in conjunction.

 

 

 

 

 

 

 

 


 

 

 

 

 

 

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.

 

 

 

 

 

 

Due to security upgrades, UIU License Keys with expiration dates ≥ Jan 1, 2020 will only be valid with the following product versions of the UIU (or newer):

UIU 5: 5.8.0.0
UIU Plug-in for SCCM: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Plug-in for MDT: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Classic Mode: 5.8.0.0


Note: Each of these products employ the UIUPREP executable and as such the version of UIUPREP.EXE must be ≥ 5.8.0.0


WARNING: The UIU Classic (4.x) Product will not function using UIU License Keys with expiration dates ≥ Jan 1, 2020

 

 

 

 

 

 

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

 

 

 

 

 

 

5.9.0.0 - Core Functionality Update Bookmark

December 27, 2019 - RELEASE
Includes UIUPrep version 5.9.0.0


This is an update of the UIUPREP application ONLY.

New Feature:  Fixed Disks Media Build

Details:
Wizards now consider fixed disks (excluding the System drive) in addition to removable disks as eligible for media creation paths in order to better accomodate larger media builds.



Issue:  KNOWN ISSUE - WinPE 3.0 & 4.0 (x86 only)

Symptoms:
Servicing older Windows PE media (3.x & 4.x) requires 32-bit specific binaries (DISM) which do not load under a 64-bit process, resulting in error conditions. Big Bang recommends that Winodw PE version 10 be employed. Contact UIU Support for additional information.



Issue:  Media Creation Popup

Symptoms:
When deploying media built using WinPE version 10, a pop-up dialog interrupts the process, disrupting the automated portion of the UIU5's constructed media.

Resolution:
Code was modified to prevent "Running on Windows 10 or later" dialog pop-up.



Issue:  UNC Path vs local mapped drives

Symptoms:
When selecting the ellipsis to browse for a UIU path in any UIU 5 wizard, if the location is chosen from a locally mapped drive, target machines would not have access to the location, resulting in errors.

Resolution:
The path selection with now convert the selected location to a UNC path for proper access by target machines.



Issue:  Clean Mountpoints

Symptoms:
In situations when the media build process fails to complete the DISM mountpoints would not be cleaned up under certain conditions.

Resolution:
Code was modified to ensure proper and complete mountpoint cleanup.



Issue:  Deplyment Settings control

Symptoms:
Selecting "Use Latest Driver Database (Recommended)" was causing that literal string to be written to the registry as the SelectedUDBPath (instead of being empty).

Resolution:
Code was modified to correct this condition; note that users will need to refresh/make a new selection in UIU5 to see the changes take affect in their Registry.



Issue:  Boot+ Crash

Symptoms:
If no UIU databases (UDB's) are found in the current UIU Repository, the Boot+ operation crashes.

Resolution:
This now results in a descriptive error presented in the lower left dialog.



Issue:  Custom Driver crash

Symptoms:
Clicking "Custom Drivers" in the Repository Manager control could crash. (This occurred if the Repository was not internally initialized, (e.g. updating the Repository would cause it to be initialized internally, therefore clicking "Custom Drivers" after an update operation would work properly, but clicking it before could cause a crash.)

Resolution:
Code was modified to correct this condition.



Issue:  ADK Capture Timeout

Symptoms:
A short pause was found to be necessary under certain conditions (on certain machines) in order to execute a DISM capture. Pinging localhost did ont always provide a sufficient delay.

Resolution:
ADK Basic Capture now performs a TIMEOUT for five seconds instead of pinging localhost to ensure proper execution of the DISM capture command.



Due to security upgrades, UIU License Keys with expiration dates ≥ Jan 1, 2020 will only be valid with the following product versions of the UIU (or newer):

UIU 5:  5.8.0.0
UIU Plug-in for SCCM:  2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Plug-in for MDT:  2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Classic Mode:  5.8.0.0


Note:  Each of these products employ the UIUPREP executable and as such the version of UIUPREP.EXE must be ≥ 5.8.1.0


WARNING:  The UIU Classic (4.x) Product will not function using UIU License Keys with expiration dates ≥ Jan 1, 2020


Issue:  Microsoft ADK 1803

Symptoms:
When employing ADK options in UIU 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).

Resolution:
With ADK 1803 installed on the UIU 5 Console machine, a pop-up window stating "Using Windows 10 or later" will be presented. Selecting the "OK" button will allow the ADK process to proceed. Alternatively for unattended operations, an earlier version of ADK should be employed, (e.g. ADK 1709).



REMINDER - Requirements Change - .Net Framework Version Upgrade

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



REMINDER - 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..



REMINDER - 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.



2.3.1.0 - UIU Plug-ins 2.0 with SCCM - Core Functionality Update Bookmark

December 27, 2019 - RELEASE
Includes UIU plug-in for SCCM version 2.3.1.0
Includes UIUPrep version 5.9.0.0


This is an update of the UIUPREP application ONLY.

Issue: UIU Repository DP selection process

Symptoms:
If no DP locations respond to ping (within 200ms), UIUPrep fails to service drivers to the target machine.

Resolution:
UIUPrep pings each accessible Distribution Point (Package path) when attempting to discern from which to source the UIU Repository. This change continues to ping each path (and will use it for sorting purposes if provided multiple valid options if otherwise unable to determine the 'best', 'nearest' path), but no longer invalidates a path if it does not respond (or fails to respond within 200ms.)



New Feature: Continue on Error Control Compliance

Details:
In accordance with the SCCM(MDT) Task Sequence engine, the UIUPREP application will now return an error code (1) in the event that a condition required for the UIU to function efficiently or completely has not been satisfied. SCCM and MDT users should be able to control whether or not Task Sequences continue under the "Options" panel of their UIU Deployment Configuration step via the "Continue on error" control.



UIU Driver Database Review

Details:
Our Support team has completed a comprehensive review of the UIU Driver Database, particularly with respect to its inclusion of unsigned drivers. In previous versions, when the "Signed Drivers Only" option had been selected, unsigned drivers may have been delivered to target machines but not employed. As of UIUPREP version 5.8.4.0, handling of unsigned drivers has been optimized to ensure that they are not even delivered to target machines when the "Signed Drivers Only" option has been selected.



Due to security upgrades, UIU License Keys with expiration dates ≥ Jan 1, 2020 will only be valid with the following product versions of the UIU (or newer):

UIU 5: 5.8.0.0
UIU Plug-in for SCCM: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Plug-in for MDT: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Classic Mode: 5.8.0.0


Note: Each of these products employ the UIUPREP executable and as such the version of UIUPREP.EXE must be ≥ 5.8.1.0


WARNING: The UIU Classic (4.x) Product will not function using UIU License Keys with expiration dates ≥ Jan 1, 2020


REMINDER: Requirements Change - .Net Framework Version Upgrade

The UIU Plug-ins 2.0 with SCCM (as of UIU 2.2.2.x) now requires the .NET 4.6 Framework.





REMINDER

The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT (v1.x). Support and UIU DAT files for UIU plug-in for MDT (v1.x) will be deprecated on Feb 1, 2018.

All OS deployment task sequences should be thoroughly assessed for remnants of the UIU Machine Configuration element, (associated with the UIU v1.x product), prior to uninstalling the UIU v1.x product. Failure to remove UIU v1.x task sequence elements prior to uninstallation will result in unrecoverable MMC errors when requesting properties on those task sequences, rendering those task sequences unusable!


Please refer to the UIU Plug-ins 2.0 - SCCM User Guides for detailed implementation and usage instructions.

The UIU Plug-ins 2.0 for SCCM version 2.1.0.0 also includes support for 1E Nomad/Active Efficiency. Please contact UIU Support for details.



The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard SCCM Console interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.

System Center Configuration Manager (SCCM)
In SCCM, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin" directory as well as the addition of necessary WMI classes (MOF) to support the UIU Plug-ins 2.0. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result. Furthermore, if an Administrator is not able to control the configuration of various SCCM Remote Console implementations (distribution of a single UIU dll file), the integration of the UIU Plug-ins 2.0 may prove to be problematic and utilizing the Run Command Line task element will alleviate those issues.

For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.

IMP Files

This version of the UIU requires the use of UIU IMP files to establish a UIU Repository from locally existing files. If bandwidth allows, Big Bang recommends that the UIU Repository be established (and regularly updated) from Big Bang's Online Updates resources. UIU DAT files are not supported.

UIU Import files (*.IMP) contain required driver files, driver database(s) and UIU components which are used to populate a UIU Repository from which deployed target machines will draw necessary files during OS deployment Task Sequence executions. These files are used in conjunction with the UIUPM.

For assistance or questions, please contact us:


UIU Support



2.3.1.0 - UIU Plug-ins 2.0 with MDT - Core Functionality Update Bookmark

December 27, 2019 - RELEASE

Includes UIU plug-in for MDT version 2.3.1.0
Includes UIUPrep version 5.9.0.0

 


This is an update of the UIUPREP application ONLY.

 

 

 

Due to security upgrades, UIU License Keys with expiration dates ≥ Jan 1, 2020 will only be valid with the following product versions of the UIU (or newer):

UIU 5: 5.8.0.0
UIU Plug-in for SCCM: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Plug-in for MDT: 2.2.2.0 (incl. UIUSMS.DLL v2.2.1.0)
UIU Classic Mode: 5.8.0.0


Note: Each of these products employ the UIUPREP executable and as such the version of UIUPREP.EXE must be ≥ 5.8.1.0


WARNING: The UIU Classic (4.x) Product will not function using UIU License Keys with expiration dates ≥ Jan 1, 2020

 

 

REMINDER: New Feature - Task Sequence UIU License Key Updating

The UIU plug-in updating feature has been upgraded to not only update the MDT plug-in within the framework of MDT (ts.xml), the service will also update the UIU license key within every MDT task sequence that contains the UIU Deployment Configuration element, requiring no Administrator interaction with MDT task sequences post-UIU updates.

Note: In previous versions of the UIU plug-in for MDT, after the plug-in had been updated using the UIU Plug-in Manager, each MDT task sequence that integrated the UIU Deployment Configuration element required an "Apply" event in order to use the UIUPM-updated UIU license key.
 

Supported MDT builds

  • Microsoft Deployment Toolkit (MDT), build 8450 - 6.3.8450.1000
  • Microsoft Deployment Toolkit (MDT), build 8456 - 6.3.8456.1000

 


To download Microsoft Deployment Toolkit (MDT), build 8456, click the following link:
Microsoft Deployment Toolkit (MDT) v6.3.8456.1000

 

 

 

 

REMINDER: Requirements Change - .Net Framework Version Upgrade

 

 

 

The UIU Plug-ins 2.0 with MDT (as of UIU 2.2.2.x) now requires the .NET 4.6 Framework.

 

 


 

 

 

REMINDER

The UIU Plug-ins 2.0 is a direct, compulsory upgrade for the UIU plug-in for MDT (v1.x). Support and UIU DAT files for UIU plug-in for MDT (v1.x) will be deprecated on Feb 1, 2018.

 

 

 

 

All OS deployment task sequences should be thoroughly assessed for remnants of the UIU Machine Configuration element, (associated with the UIU v1.x product), prior to uninstalling the UIU v1.x product. Failure to remove UIU v1.x task sequence elements prior to uninstallation will result in unrecoverable MMC errors when requesting properties on those task sequences, rendering those task sequences unusable!

 


Please refer to the UIU Plug-ins 2.0 - MDT User Guides for detailed implementation and usage instructions.

 

 

 

 

 


 


The UIU Plug-ins 2.0 is a versatile solution that may be invoked though the standard MDT Deployment Workbench interface via a task element (UIU Deployment Configuration) or directly through a Run Command Line task element. Furthermore, The UIU may be invoked manually from within a Windows PE session under the direction of UIU Support. Multiple modes of operation have been provided to accommodate environmental differences as well as policy/change control restrictions.

 

 

 

 

Microsoft Deployment Toolkit (MDT)

In MDT, integration consists of the inclusion of a uiusms.dll in the "C:\Program Files (x86)\Microsoft Deployment Toolkit\bin" directory as well as a modification (additional section appended) to the Actions.xml file in the same directory. If integration is not desired or permitted, an Administrator may launch the UIU Plug-ins 2.0 from a Run Command Line task element (with the correct arguments) to achieve a successful result.

For more information on alternative methods of invoking the UIU Plug-ins 2.0, Please contact UIU Support.

 

 

 

 

IMP Files

This version of the UIU requires the use of UIU IMP files to establish a UIU Repository from locally existing files. If bandwidth allows, Big Bang recommends that the UIU Repository be established (and regularly updated) from Big Bang's Online Updates resources. UIU DAT files are not supported.

UIU Import files (*.IMP) contain required driver files, driver database(s) and UIU components which are used to populate a UIU Repository from which deployed target machines will draw necessary files during OS deployment Task Sequence executions. These files are used in conjunction with the UIUPM.

 

 

 

 

For assistance or questions, please contact us:


UIU Support