Release Notes

May 20, 2019 - RELEASE

Includes UIU plug-in for SCCM version 2.2.1.0

Includes UIUPrep version 5.8.3.0

This is an update of the UIU Plug-in Manager ONLY. The UIU plug-in for MDT and the UIUPrep application have not changed.

Issue: WinPE Boot+ Failure

Symptoms:
The UIU Boot+ feature does not complete successfully.

Resolution:
Corrected an issue with file cleanup.

Supported MDT builds

• MDT 2012 Update 1 - 6.1.2373.0
• MDT 2013 - 6.2.5019.0
• MDT 2013 Update 1 - 6.3.8290.1000
• MDT 2013 Update 1 (re-released on Sept 15, 2015) - 6.3.8298.1000
• MDT 2013 Update 2 - 6.3.8330.1000
• Microsoft Deployment Toolkit (MDT), build 8443 - 6.3.8443.1000
• 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.




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

May 20, 2019 - RELEASE

Includes UIU plug-in for SCCM version 2.2.1.0

Includes UIUPrep version 5.8.3.0

This is an update of the UIU Plug-in Manager ONLY. The UIU plug-in for SCCM and the UIUPrep application have not changed.

Issue: UIU Plug-in Manager Updating Issue

Symptoms:
If UIUPM.exe resides on a drive other than the machine's system drive, the UIUPM will be unable to update itself, hanging after download (at 100%).

Resolution:
Issue corrected.

Issue: UIU Plug-in(s) Not Updating After UIU License Key Update

Symptoms:
When the UIU License Key is updated in the UIUPM.exe, the option to update the UIU Plug-in for SCCM with the newly updated key is unavailable ("Install" button is greyed-out).

Resolution:
Issue corrected.

Issue: WinPE Boot+ Failure

Symptoms:
The UIU Boot+ feature does not complete successfully.

Resolution:
Corrected an issue with file cleanup.

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.

New Feature: SCCM Provider Installation Option

In UIUPM, upon selecting the "Install Plug-in", an Administrator may now elect to install the Console Element and/or the WMI class (MOF).

• If installing on an SCCM Primary Site Server, select both components.
• If installing on an SCCM Provider (stand-alone), select only the MOF component.
• If installing on a "remote" Configuration Management Console, (e.g. Administrator PC), select only the "UIU Plug-in Library" component.

---

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.



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

May 9, 2019

Driver DB Amendments:

Customer-requested drivers since April 24 2019 release.

Drivers Affected:

See Attached: UIU DB-19-05-09 Drivers.pdf

Make and Models Affected:

See Attached: Make-Model DB-19-05-09.pdf

Issue: nVidia 3d Video Controller Issue on Dell hardware

Symptoms:
On various Dell machines, if using Windows 1709, the latest version of the 3D Video Controller offered (OEM or PC Manufacturer) will not install correctly and produces a driver bang in the Device Manager.

Resolution:
We have modified the staging of this driver to the latest appropriately constructed driver.

Issue: IDT Driver Issue on HP hardware

Symptoms:
On HP hardware that contains the IDT HD Audio component, the associated IDT driver (STWRT*.inf) newer than 19AUG12 will not function correctly or install in a silent or unattended fashion.

Resolution:
We have modified the staging of this driver to the latest appropriately constructed driver. Please contact UIU Support for additional, manual installation methods for the affected versions.

Reminder:

The full driver database exceeds 28Gb in size (28.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!

April 30, 2019 - RELEASE

Includes UIUPrep version 5.8.3.0

Issue: DNS Lookup Difficulty

Symptoms:
UIULog indicates that a DNS Lookup Failed potentially resulting in insufficient driver support on target machine(s).

Resolution:
UIU's behavior for addressing management points has been updated to account for additional variety in network configurations.

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.

New Feature: SCCM Provider Installation Option

In UIUPM, upon selecting the "Install Plug-in", an Administrator may now elect to install the Console Element and/or the WMI class (MOF).

• If installing on an SCCM Primary Site Server, select both components.
• If installing on an SCCM Provider (stand-alone), select only the MOF component.
• If installing on a "remote" Configuration Management Console, (e.g. Administrator PC), select only the "UIU Plug-in Library" component.

---

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.



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

April 30, 2019 - RELEASE

Includes UIUPrep version 5.8.3.0

Feature Update: MDT Version

Support has been added for MDT build 8456.

Supported MDT builds

• MDT 2012 Update 1 - 6.1.2373.0
• MDT 2013 - 6.2.5019.0
• MDT 2013 Update 1 - 6.3.8290.1000
• MDT 2013 Update 1 (re-released on Sept 15, 2015) - 6.3.8298.1000
• MDT 2013 Update 2 - 6.3.8330.1000
• Microsoft Deployment Toolkit (MDT), build 8443 - 6.3.8443.1000
• 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.




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

April 30, 2019 - RELEASE

Includes UIUPrep version 5.8.3.0

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

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

April 24, 2019

Driver DB Amendments:

Customer-requested drivers since April 18 2019 release.

Drivers Affected:

See Attached: UIU DB-19-04-26 Drivers.pdf

Make and Models Affected:

See Attached: Make-Model DB-19-04-26.pdf

Reminder:

The full driver database exceeds 28Gb in size (28.3 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!

April 18, 2019

Driver DB Amendments:

Customer-requested drivers since April 4 2019 release.

Drivers Affected:

See Attached: UIU DB-19-04-18 Drivers.pdf

Make and Models Affected:

See Attached: Make-Model DB-19-04-18.pdf

Reminder:

The full driver database exceeds 27Gb in size (27.9 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!

April 4, 2019

Driver DB Amendments:

Customer-requested drivers since March 7, 2019 release.

Drivers Affected:

See Attached: UIU DB-19-04-04 Drivers.pdf

Make and Models Affected:

See Attached: Make-Model DB-19-04-04.pdf

Reminder:

The full driver database exceeds 27Gb in size (27.4 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!